Unified Advertising API: Sync Campaigns, Ads, and Performance Data Across Platforms

January 5, 2026

Unified now supports a new category: Advertising.

If your product touches paid media, you eventually hit the same wall: every customer asks to connect a different ad platform, and each platform's API behaves differently.

The Unified Advertising API gives you a single, standardized way to read and write campaigns, ads, and performance data across major ad networks, in real time, without maintaining vendor-specific integrations.

This is built for teams shipping advertising data as a real product surface:

• Marketing analytics and reporting SaaS ('Connect your ad accounts')
• Agency and reseller portals (many clients, many ad accounts)
• AI and automation tools that need live performance signals
• Data and BI pipelines pulling paid media into warehouses for attribution and forecasting

Read our docs →

Why a unified Advertising API

Ad platforms provide similar concepts (campaigns, ads, performance), but their APIs rarely line up. Authentication differs, objects are modeled differently, and reporting endpoints and metrics are inconsistent. Supporting 'one more platform' becomes recurring engineering work.

Traditional approach

• Build separate integrations per platform
• Maintain multiple auth systems and permission scopes
• Normalize schemas yourself for reporting and analytics
• Rework integrations when APIs change
• Repeat pagination, rate limits, and error handling patterns per provider

With Unified

• Integrate once through one API surface
• Work with normalized objects across providers
• Query performance metrics by KPI type and time range
• Get real-time data via real-time, pass-through API calls (no caching, no sync jobs)

What you can build with Advertising

Common use cases:

• Multi-platform ad dashboards inside your product
• Agency reporting portals (white-label, client-by-client)
• Cross-channel monitoring and alerts (spend, CTR shifts, performance drops)
• Cross-platform reporting and attribution workflows that need consistent inputs
• Warehousing ad performance into BI (without multiple pipelines)
• AI analytics over ad data (trend detection, anomaly detection, recommendations)
• Campaign creation and lifecycle management
• Budget updates and pacing adjustments
• Creative and targeting updates across platforms

This is especially useful for AI-powered products, where agents or copilots need consistent, real-time access to campaign performance and the ability to take action across platforms.

Read our docs →

Supported providers

Advertising integrations include:

• Amazon Advertising
• Google Ads
• Google Campaign Manager 360
• Google Display & Video 360
• LinkedIn
• Meta Ads
• Microsoft Advertising
• Pinterest Ads
• Reddit Ads
• Snapchat
• The Trade Desk
• TikTok Ads
• X Ads

Looking for another provider? Request an integration.

Standardized objects across advertising platforms

The Advertising API provides normalized objects across providers:

• Organizations (ad accounts): id, name, currency, timezone (where supported)
• Campaigns: id, name, active status, budgets (budget_amount, budget_period), scheduling (where supported)
• Groups (ad groups/ad sets): id, name, active status, campaign relationship, plus provider-specific fields where available
• Ads: id, name, type, active status, group relationship, plus creative fields where available
• Reports: metric results scoped to date range + org, and optionally campaign
• Creatives (ad assets, copy, URLs, metadata)
• Insertion Orders (budget allocation and pacing structures)
• Targets (targeting parameters)
• Promoted Objects (platform-specific promoted entities)

Field-level coverage varies by provider. In addition to core objects, Unified supports deeper structures such as creatives, insertion orders, targeting, and promoted entities, enabling full campaign lifecycle management across platforms.

Reports with explicit KPI types

Reporting is metric-driven. You request the KPI you want, then filter by ad account and campaign.

Endpoint: GET /ads/{connection_id}/report

Filters: org_id, campaign_id

Metric selector: type

Supported type values include:

• Core: CLICKS, IMPRESSIONS, CTR, COST, CPC, CPM, ECPM
• Conversion + value: CONVERSIONS, CONVERSION_VALUE, CPA, ROAS
• Engagement: ENGAGEMENT, ENGAGEMENTS, LIKES, SHARES, COMMENTS, SAVES, FOLLOWS
• Video: VIDEO_VIEWS, VIDEO_COMPLETIONS
• Lead gen: LEADS

Example workflow

Cross-platform dashboard inside your product:

1. Customer connects Google Ads + Meta Ads + TikTok Ads
2. You list organizations (ad accounts) and pull structure (campaigns, groups, ads)
3. You query /report for the KPIs you need (e.g., COST, CLICKS, ROAS) filtered by org_id and campaign_id
4. You render a consistent dashboard across platforms using Unified's normalized objects

Real-time, read/write by design

The Advertising API supports both read and write operations across supported objects.

• Read campaign structure, ads, and performance metrics
• Create, update, and manage campaigns, groups, creatives, and ads
• Modify targeting, budgets, and scheduling where supported

All requests are stateless and routed directly to the source API—no caching, no sync jobs, no stored records.

Unified provides real-time access because every request is stateless and passes through to the ad platforms directly (no caching). Traffic is regionalized (US/EU/AU) to support data residency requirements. Learn more about our data security →

The Advertising API is available on all Unified plans. Start your 30-day trial or book a demo.

What is a unified advertising API?

A unified advertising API provides a single interface to access and manage data across multiple ad platforms. Instead of integrating with each provider separately, developers can use one API to read and write campaigns, ads, and performance data with consistent schemas across systems.

Can you manage ad campaigns across multiple platforms with one API?

Yes, a unified advertising API allows developers to create, update, and manage campaigns, ads, and targeting across multiple ad platforms through a single integration. This removes the need to build and maintain separate integrations for each provider.