Skip to main content
Configure event sources on a seller account for conversion tracking. Supports upsert semantics, seller-managed sources, and setup instructions. Response Time: ~1s (synchronous configuration) Request Schema: /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
Error Response:
  • errors - Array of operation-level errors (auth failure, account not found)
Note: Responses use discriminated unions - you get either success fields OR errors, never both. Each event source in success response includes:
  • All request fields
  • seller_id - Seller-assigned identifier for this event source
  • action - What happened: created, updated, unchanged, deleted, failed
  • action_source - Type of event source (website pixel, app SDK, etc.)
  • managed_by - Who manages this source: buyer or seller
  • setup - Implementation details (snippet, instructions)
  • errors - Per-source errors (only when action: "failed")
See schema for complete field list: sync-event-sources-response.json

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 with managed_by: "seller" alongside your buyer-managed sources:
test=false
Products with conversion_tracking.platform_managed: true indicate the seller provides these sources.

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. The setup object tells you how to activate the source:

Error Handling

Best Practices

  1. Sync before logging - Always configure event sources before sending events via log_event. Events sent to unconfigured sources will be rejected.
  2. Use descriptive IDs - Choose event_source_id values that are meaningful (e.g. web_pixel, app_sdk, crm_import) rather than opaque identifiers.
  3. Specify event_types - Restrict each source to relevant event types for better validation and debugging.
  4. Check seller capabilities - Use get_adcp_capabilities to discover supported event types, UID types, and action sources before configuring event sources.
  5. Install setup snippets - When the response includes setup instructions, install the provided snippet before logging events. Server-only sources (snippet_type: "server_only") skip this step.
  6. 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