Public API — Candidate Integrations
Working list of third-party platforms where an Adventive Public API connector or end-user guide would meaningfully expand reach into our publisher and agency customer base. Not every entry is committed work — this is a backlog of opportunities to evaluate as task #33 / #34 / #35 / #41 are picked up.
Audience legend
Section titled “Audience legend”- Pub — direct-sold and programmatic publishers running Adventive creative
- Agy — media buying / planning agencies pulling campaign performance for clients
- Both — relevant on both sides
Integration model legend
Section titled “Integration model legend”- Native connector — partner builds (or we build) a first-class connector that calls the Public API on the user’s behalf using
X-Api-Key+X-Integration-Key - Sheets / spreadsheet — pulled via Google Sheets / Excel Power Query against REST endpoints
- ELT / pipeline — partner platform schedules pulls and lands data in a warehouse the client owns
- BI direct — BI tool reads JSON/CSV directly via web data connector
- Automation — no-code workflow (Zapier-style) consumes endpoints
- Doc-only — no integration code, just an end-user guide showing how to authenticate and call the API
Candidates
Section titled “Candidates”| # | Platform | Category | Audience | Why it matters for Adventive | Integration model | Priority |
|---|---|---|---|---|---|---|
| 1 | Looker Studio (Google Data Studio) | BI / Dashboards | Both | Free, ubiquitous in agencies; existing Adventive Apps Script connector is tracked under task #33. Lowest-friction client-reporting surface we can offer. | Native connector (already exists) | High — task #33 |
| 2 | Google Sheets | Spreadsheet | Both | ”Lingua franca” of agency reporting; analysts copy-paste numbers into client decks. A signed Sheets add-on or IMPORTDATA recipe covers most ad-hoc use. | Sheets / spreadsheet | High — task #35 |
| 3 | TapClicks | Agency reporting | Agy | Mid-market agency reporting suite with a marketplace of data sources; native Adventive connector unblocks dozens of client-facing dashboards per agency. | Native connector | High — task #34 |
| 4 | Windsor.ai | Marketing data pipeline | Both | Connector platform with hundreds of marketing destinations (Sheets, BigQuery, Snowflake, Looker, Power BI, etc.). One Adventive source unlocks all of them at once. | ELT / pipeline | Medium — task #41 |
| 5 | Supermetrics | Marketing data pipeline | Both | The Windsor.ai incumbent — Sheets / Looker Studio / BigQuery / Excel destinations. Publisher partnership = they list us; agency use case = batch pulls into client warehouses. | ELT / pipeline | High |
| 6 | Funnel.io | Marketing data pipeline | Agy | Agency-favored ELT with strong normalization layer; relevant when agencies blend Adventive with DSP / search / social spend. | ELT / pipeline | Medium |
| 7 | Improvado | Marketing data pipeline | Agy | Enterprise-tier marketing data aggregator targeting holding-company agencies; competitive lever vs. Datorama. | ELT / pipeline | Low — enterprise long-tail |
| 8 | Adverity | Marketing data pipeline | Both | Strong publisher-side footprint in EU; pre-built data harmonization that agencies and pub-side BI teams both consume. | ELT / pipeline | Medium |
| 9 | Fivetran | Generic ELT | Both | Standard for in-house data teams that want raw Adventive data in Snowflake / BigQuery / Redshift. We supply the connector spec; Fivetran or the customer builds. | ELT / pipeline | Medium |
| 10 | Power BI | BI / Dashboards | Both | Microsoft-shop publishers and agencies often standardize on Power BI; native Web/REST data source plus a documented Power Query M template covers it. | BI direct + doc-only | Medium |
| 11 | Tableau | BI / Dashboards | Both | Enterprise BI tool; needs a Web Data Connector or tableau-api recipe. Same audience as Power BI but skewed toward larger agencies and publisher analytics teams. | BI direct + doc-only | Medium |
| 12 | Domo | BI / Dashboards | Agy | Cloud BI common in mid-market agencies and publisher revenue teams; Workbench or REST connector. | BI direct | Low |
| 13 | AgencyAnalytics | Agency reporting | Agy | White-label client-reporting platform popular with SMB and mid-market agencies; lots of Adventive’s smaller agency customers already use it. | Native connector | Medium |
| 14 | Whatagraph | Agency reporting | Agy | Same niche as AgencyAnalytics; visual client-report builder. Native source request comes up periodically in support. | Native connector | Low |
| 15 | NinjaCat | Agency reporting | Agy | Agency PPC / display reporting suite; relevant where agencies blend Adventive with search/social. | Native connector | Low |
| 16 | Salesforce Marketing Cloud Intelligence (Datorama) | Enterprise marketing intelligence | Agy | Enterprise / holding-company agencies standardize on Datorama for cross-channel reporting; high effort, high value per logo. | Native connector / API stream | Low — enterprise long-tail |
| 17 | Snowflake / BigQuery (direct) | Data warehouse | Both | Larger publishers and in-house agency data teams want raw rows in their own warehouse. Document a sanctioned pull pattern (scheduled Worker → object storage → external table) so customers don’t reinvent it badly. | Doc-only + reference recipe | Medium |
| 18 | Zapier / Make.com | No-code automation | Both | Long-tail use cases — alerts, ticket creation, light data sync. A published REST app on each platform makes Adventive available to non-technical users without us shipping bespoke connectors. | Automation | Medium |
| 19 | Slack / Microsoft Teams | Alerting | Both | Scheduled performance digests and pacing alerts delivered as channel messages. Implementable as a small Worker that calls Public API on cron and posts to webhooks; ships as a recipe, not a product. | Doc-only + reference Worker | Low |
| 20 | Operative.One | Publisher ad ops | Pub | Publisher-side OMS where direct-sold campaign delivery is reconciled. A read-only Adventive feed of measured delivery would close a known gap in publisher month-end reconciliation. | Native connector | Medium — strategic to publisher segment |
How to use this list
Section titled “How to use this list”When a task in §13 of 07-as-built-runbook.md is picked up:
- Confirm the audience and priority above still reflect reality (sales / CS may have more recent signal).
- Decide the integration model — many “guides” are actually doc-only and can be shipped from
developer.adventive.com(task #36) without engineering work. - For native-connector partnerships (TapClicks, AgencyAnalytics, Whatagraph, NinjaCat, Operative.One, Datorama), confirm whether the partner builds against our spec or we build against theirs — this changes who owns the maintenance burden.
- File the integration-specific guide under
integrations/<vendor-slug>.mdin this folder, mirroringwindsor-ai.md.
Out of scope (intentionally)
Section titled “Out of scope (intentionally)”- Google Ads / DV360 / TTD — those are demand-side; Adventive is creative/measurement, not a buying platform.
- FreeWheel / Magnite / Xandr SSP feeds — supply-side ad-server integrations are a separate workstream from the Public API.
- Mediaocean / Prisma — agency media-management; integration is order/IO-level, not measurement-level. Revisit if the product line expands.
Change log
Section titled “Change log”| Date | Change |
|---|---|
| 2026-04-30 | Initial list. 20 candidates spanning BI, ELT, agency reporting, warehouse, automation, and publisher ad-ops. Three already tracked as tasks #33/#34/#35; Windsor.ai newly added as task #41. |