Meta Conversions API

The Meta Conversions API integration sends every recorded click to your Meta dataset server-side, as a LinkClicked event. Because it never depends on the browser pixel, the event still reaches Meta when the visitor blocks trackers or is on an iOS device with tracking restricted. Available on Growth and Ultimate.

What you need

• Your pixel ID (Events Manager → your dataset → Settings).
• A Conversions API access token, generated on the same screen under Conversions API.

Connect it to Letlink

1. Open Integrations → Meta Conversions API. Owners and admins only.
2. Paste the pixel ID and access token, then save.
3. Optionally paste a test event code from the Test Events tab and press Send test event — the event appears there within a few seconds.
4. Clear the test event code once you are happy, so production events are not flagged as test traffic.

What we send

One event per recorded click: event_name LinkClicked, action_source website, the short URL as event_source_url, the visitor IP and user agent in user_data, and the short code, destination, link type, variation and UTM values in custom_data. Each event carries a stable event_id (click-<id>) so Meta can deduplicate it against a browser pixel event if you also fire one.

Why do my numbers not match the pixel?

They should not match exactly. The pixel fires on the destination page after the redirect; this fires on the redirect itself. Clicks that never finish loading the destination appear here and not there. Use the event_id deduplication above if you need a single combined number.