What is Teads CAPI?

Teads is a global advertising platform specializing in outstream video and display ads that appear within premium publisher content. They work with major media outlets to deliver high-quality, brand-safe inventory across desktop, mobile web, and in-app environments. Teads offers both direct and programmatic buying options, with advanced targeting, viewability optimization, and measurement tools. Advertisers can run campaigns focused on awareness, engagement, or conversions, and track performance through Teads’ analytics and reporting suite. Their technology is designed to provide a non-intrusive ad experience while maximizing reach and engagement.

Product Type: Advertising

Integration Type: Starter-Kit & ID Sync

Capabilities

• Captures the auctid (Teads click ID) from the landing-page URL and stores it in first-party storage.
• Attributes server-side conversion events back to the originating Teads ad click.
• Refreshes the stored value on every page load whenever the auctid URL parameter is present.
• Enriches all server-side events with the resolved Teads identifier for attribution.

Sync Details

• IDs:

  • auctid – The Teads click ID appended to landing-page URLs, used to track and attribute conversions back to a specific Teads ad click.

• Description:

  • The sync captures the auctid URL parameter from the landing-page URL.
  • The value is stored in first-party storage for the duration set by the Cookie Lifetime setting in the UI (defaults to 30 days).
  • The stored value is refreshed and its lifetime reset to the full duration whenever the auctid URL parameter is detected again on page load.
  • The identifier is added to server-side event payloads for attribution.

• Server-side Event Payload: Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload:

  JSON

  {
    "teadsCAPI": {
      "auctid": "string"
    }
  }

• Cookie Name:

  • Cookie: _meta_teadsCAPI_auctid
  • IndexedDB: [your storage prefix]_teadsCAPI_auctid
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

Add a Teads CAPI Sync in MetaRouter

To gather the auctid, you must add a Teads CAPI sync.

1. From the Pipelines page, find the pipeline associated with the web property you'd like to add a sync to. Hover over the three dot dropdown and select "Build AJS File."
2. In the Identity Syncs section, select the Teads CAPI sync.
3. Fill out the following fields:
   • Cookie Lifetime (days) (Optional) – How long the synced identifier remains in first-party storage. When expired or no longer detected, the sync will re-trigger. Enter a whole number of days, for example 30. Defaults to 30 days.
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.