Connect your first destination

Overview

Destinations forward normalized events to ad platforms, ESPs, warehouses, or custom HTTP receivers. Connecting a first destination validates mapping, hashing rules, and consent propagation from your workspace defaults.

Steps

1. Go to Destinations → Add and select the vendor (for example Meta, Klaviyo, or a webhook).
2. Paste credentials from the vendor’s developer console—prefer long-lived server tokens with least privilege.
3. Map event names and parameter paths. Start with a narrow allowlist (Purchase, Lead) before enabling broad catalogs.

{
  "destination": "example_capi",
  "mappings": [
    {
      "from": "Purchase",
      "to": "Purchase",
      "fields": {
        "value": "properties.revenue",
        "currency": "properties.currency"
      }
    }
  ]
}

4. Send a sandbox event with the Test delivery action and compare the vendor’s event debugger to TrackLayer’s receipt log.

Troubleshooting

• 400 from vendor commonly means a missing required field—open the mapping diff in the delivery drawer.
• Dropped for consent is expected when default consent is denied; flip to a region with legal basis or attach a CMP signal.
• Throughput warnings usually clear after you batch high-volume streams server-side instead of per-click browser posts.