Integrations & Data Sources
This section contains all documentation for connecting data sources to Watching That and querying your data through external platforms.
How data flows into Watching That
Watching That ingests data through four primary methods, which can be used independently or in combination depending on the data source:
Method | What It Does | Examples |
|---|---|---|
Log Files | Batch ingestion of event-level data from ad servers and SSPs. The primary feed for most deployments. | FreeWheel v4 logs, GAM Data Transfer files, SpringServe log level data |
API Connections | Three purposes: pulling reporting data where log access isn't available, enriching log data with metadata (resolving IDs to friendly names), and powering Validation Monitors (configuration checks). | FreeWheel MRM API, GAM API, SpringServe API, all 12 SSP and exchange reporting APIs |
Email / CSV Import | Automated ingestion of scheduled reports delivered as email attachments, or manual CSV file uploads. Used for SSP and exchange rollup data. | SSP daily revenue reports, exchange performance summaries |
Collector | Real-time event tracking via pixels deployed in ad responses, browser plugins on video players, or custom code pushing data to the Collector endpoint. | Ad server pixels, Brightcove/JW Player plugins, server-side proxy implementations |
Each data source in Watching That may use one or more of these methods. The sections below are organised by technology type — find your vendor and everything you need is in one place.
Coverage at a glance
Quick reference for what's supported, how it connects, and which modules it feeds.
Platform | Category | Ingestion | Report | Analysis | Inspect | Monitoring |
|---|---|---|---|---|---|---|
Ad Server | Logs + API + Pixel | ✓ | ✓ | ✓ | ✓ | |
Ad Server | Logs + API + Pixel | ✓ | ✓ | ✓ | ✓ | |
Ad Server | Logs + API + Pixel | ✓ | ✓ | ✓ | ✓ | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
SSP/Exchange | Reporting API | ✓ | — | — | — | |
Akamai AMP, Bitmovin, Brightcove, JW Player, VideoJS | Video Players | Collector Pixel | ✓ | ✓ | ✓ | ✓ |
Don't see your platform? Custom integrations are available via the Collector API or Email / CSV Import — contact your account manager.
Data sources by technology type
Ad Servers
Primary event data via log files. API connections serve three purposes: pulling reporting data where log access isn't available, enriching log data with metadata (resolving IDs to friendly names), and powering Validation Monitors (configuration checks). Optional pixel deployment captures real-time tracking.
SSPs & Exchanges
Performance data from SSP and exchange platforms via Reporting API integrations or Email / CSV import. Currently supported via Reporting API: Beachfront, Google Ad Manager Ad Exchange (AdX), Index Exchange, Magnite, Microsoft Advertising, Nexxen, OpenX, PubMatic, ShareThrough, SpringServe Marketplace, TripleLift, and Yahoo Ad Manager Plus. More connections being added via both methods.
Video Players
Real-time event tracking via pre-built browser plugins that wrap the Collector API.
AI & LLM Platforms
Query your Watching That data in plain English from AI assistants such as Claude and ChatGPT, via the MCP Server.
Platform Tools & References
Shared infrastructure documentation: Collector API spec, Email / CSV Data Import reference, plugin configuration, MCP Server reference, and custom integration guides.