FAQ

Why use CAPI?

Better post-click conversion volume and quality for Teads optimization, without relying on third-party cookies. See Why CAPI for the full explanation.

Can CAPI run without the Teads Pixel?

Yes. It is standalone and can also run next to the pixel for better coverage. Together they still deduplicate on Click ID within the same 5-minute window.

Post-click only?

Yes. Open-web post-click only. Post-view measurement still requires the pixel, and CAPI does not support in-app events — see Event types.

CAPI is a selective call: you choose when to send conversion events, so Teads only sees the conversions you attribute and forward.

Matching without PII?

CAPI does not send hashed emails or phone numbers. It matches on the Teads Click ID stored in a first-party cookie and sent back on the event.

Rate limits and HTTP status codes

See Direct integration → Endpoints for the per-environment rate limits, and Direct integration → Status codes for the full list of response codes (including 429 for rate-limit violations).

Other server-side tag managers?

Official support today: sGTM (see Server-side GTM) and Tealium. Other partners (Adobe, and so on) are demand-based — ask your Teads representative.

Still useful if Google keeps third-party cookies?

Yes. Ad blockers, browser restrictions, and cookie expiry still drop client-side data. CAPI is a privacy-first, server-side path that does not depend on third-party cookies.

Privacy / GDPR?

Send the privacy object on every direct-integration event — see the privacy field reference for all supported consent signals (TCF, US Privacy, GPP). sGTM enforces consent through Google Consent Mode (ad_storage) — see Server-side GTM. Teads processes first-party data only post-consent and rejects conversion events without confirmable consent.