Connecting CAPI platforms

Connecting CAPI platforms

TrackLayer fans out every incoming event to the CAPI (Conversions API) destinations you configure. You manage credentials once in the dashboard; we handle per-platform payload shaping, identity stitching, click-ID restoration, and retry.

Supported platforms

Connect a platform

1. Open Platforms in the dashboard sidebar.
2. Pick a destination from the 3×4 grid. Connected platforms show their live status pill (OK / DEGRADED / DROPPED); unconnected show + CONNECT.
3. Click + CONNECT. The inline wizard walks through the 3-step flow:
   • Intro — what the platform expects + a link to the provider's docs for each credential
   • Credentials form — per-platform validation runs on blur (Meta pixel_id must be numeric, Google Ads customer_id must match \d{3}-\d{3}-\d{4}, etc.)
   • Review — confirm + test. A 200 from the provider's test-connection endpoint activates the platform.

Credential-format tips

Meta

• pixel_id — numeric ID from Events Manager → Data Sources → Pixel → Settings
• access_token — generate a system-user token in Business Manager → Users → System Users → Generate New Token. Required permissions: ads_management, business_management.

TikTok

• access_token — Events Manager → Web Events → Set Up Events API → Generate Access Token
• Token must be regenerated if the owning Business Center user loses the Events role.

Google Ads

• Requires both a developer token (Ads API developer access) and an OAuth refresh token with https://www.googleapis.com/auth/adwords scope.
• We use the Enhanced Conversions for Leads API (uploadClickConversions), so conversion_action_id must be an existing conversion action in the target customer account.

GA4

• measurement_id is G-XXXXXXXXXX (not the UA-prefixed legacy ID).
• api_secret is generated at Admin → Data streams → Web → Measurement Protocol API secrets.

LinkedIn

• Requires LinkedIn Conversions API access (separate from Page/Profile API). The conversion_id is from Campaign Manager → Conversions.

Duplicate prevention

TrackLayer does not dedupe events across platforms — every destination sees every matching event. Deduplication happens within a platform using the event_id you provide (or we generate). Meta's pixel-and-CAPI dedup relies on this; same for TikTok, Pinterest, and others.

For routing subsets — "send purchases only to Meta + Google Ads" — use routing rules.

Testing a connection

The TEST button on every platform card fires a synthetic test_event to that provider's sandbox (where available). Response status + latency surface directly in the card.

For platforms without a sandbox (Awin, Criteo), the test hits the real API with a minimally-valid payload — providers log it as a test but don't charge it against your conversion budget.

Status pills — what they mean

• OK — last attempt succeeded within the 24h window.
• DEGRADED — 5–50% of recent deliveries failed. Usually a token about to expire or a field validation issue.
• DROPPED — most recent deliveries failed. Check Quality → Contributing Factors for the specific field triggering reject.
• IDLE — credentials valid, but no events sent yet.

Next steps

• Define routing rules — override the default "fan out to everyone" behavior per event type
• Event quality reference — understand Match Quality Score + per-field completeness