/schemas/v3/media-buy/sync-event-sources-request.json
Response Schema: /schemas/v3/media-buy/sync-event-sources-response.json
Quick Start
Configure an event source for purchase tracking:Request Parameters
Event Source Object
Response
Success Response:event_sources- Results for each event source, including both synced and seller-managed sources on the account
errors- Array of operation-level errors (auth failure, account not found)
- All request fields
seller_id- Seller-assigned identifier for this event sourceaction- What happened:created,updated,unchanged,deleted,failedaction_source- Type of event source (website pixel, app SDK, etc.)surface- Structured surface this source represents, when the flataction_sourceis too coarsemanaged_by- Who manages this source:buyerorsellersetup- Implementation details (snippet, instructions)health- Event source health assessment (when seller supports health scoring)errors- Per-source errors (only whenaction: "failed")ext- Per-source extension metadata, such as platform-native conversion IDs, attribution-window handles, or raw origin strings
Event Source Health
Sellers that evaluate event source quality include ahealth object on each source in the response. This is analogous to Snap’s Event Quality Score or Meta’s Event Match Quality — it tells the buyer whether their event integration is working well enough for optimization.
test=false
status, not detail.score. The four-tier status is comparable across all sellers — a buyer agent writes one rule (“require good or better for DR products”) that works everywhere. The detail object is for human dashboards or advanced diagnostics.
Buyer agents can use health data to:
- Gate product selection on event quality (e.g., require
goodor better for DR products) - Surface setup issues to the buyer before campaign launch
- Prioritize which event sources to fix first
Common Scenarios
Discovery Only
Discover all event sources on an account (including seller-managed sources) without making changes. Useful for platform-managed conversion tracking where the seller provides always-on attribution:Multiple Event Sources
Configure separate sources for website and app:Discovering Seller-Managed Sources
Sellers may provide always-on event sources (e.g. Amazon sales attribution). These appear in the response withmanaged_by: "seller" alongside your buyer-managed sources:
test=false
conversion_tracking.platform_managed: true indicate the seller provides these sources.
Creator and Owned-Property Sources
Seller-managed creator or owned-property sources use the sameevent_sources array, with a flat action_source for compatibility and surface for structured context:
test=false
follow for free durable opt-ins to a channel, profile, feed, list, or podcast. Use subscribe only for paid subscriptions or paid memberships.
Clean Sync with delete_missing
Replace all buyer-managed event sources on the account:Setup Instructions
The response includes setup details for each event source. Thesetup object tells you how to activate the source:
Error Handling
Best Practices
-
Sync before logging - Always configure event sources before sending events via
log_event. Events sent to unconfigured sources will be rejected. -
Use descriptive IDs - Choose
event_source_idvalues that are meaningful (e.g.web_pixel,app_sdk,crm_import) rather than opaque identifiers. - Specify event_types - Restrict each source to relevant event types for better validation and debugging.
-
Check seller capabilities - Use
get_adcp_capabilitiesto discover supported event types, UID types, and action sources before configuring event sources. -
Install setup snippets - When the response includes
setupinstructions, install the provided snippet before logging events. Server-only sources (snippet_type: "server_only") skip this step. -
Handle seller-managed sources - The response may include sources with
managed_by: "seller"that you didn’t configure. These are always-on and provide additional attribution data.
Next Steps
- Conversion Tracking - Data model, optimization goals, and the end-to-end flow
- log_event - Send marketing events to configured event sources
- create_media_buy - Set optimization goals on packages referencing event sources
- get_media_buy_delivery - Monitor conversion metrics in delivery reports