Set up Meta CAPI postbacks

This article shows how to send Meta Conversions API (CAPI) events from Datahubb so Meta (and your affiliates) can attribute conversions.

Prefer the Postbacks Meta CAPI preset. It is the flexible path: each traffic source gets its own pixel, triggers, and field mappings. Use the Integrations → Meta CAPI path only when a single shared pixel for the whole workspace or one campaign is enough.

Why the postback preset is encouraged

• Per traffic source — each affiliate can fire their pixel, not a shared company pixel
• Multiple configs — different triggers, min payout, or mappings per network
• Full postback controls — scopes, rules, test panel, Resolution Trace, outgoing logs
• Self-serve — traffic-source users can manage their own Meta CAPI config

Limitation of the Integrations path

The campaign Meta CAPI integration is a single shared setup:

• Global credentials — one Pixel ID and access token under Integrations → Meta CAPI for the workspace
• Per campaign — you enable that same integration on a campaign and optionally override settings for that campaign only
• You cannot attach a different pixel per traffic source on this path
• You cannot run independent Meta configs per affiliate the way Postbacks allows

If affiliates need their own pixels, or you need more than one Meta setup on the same campaign, use the postback preset instead.

Prerequisites

• A Meta Pixel ID and System User access token (Events Manager → Data Sources → your pixel → Settings)
• Postbacks feature (for the recommended path)
• A traffic source recipient for the config
• Optional: Meta Test event code while validating

Recommended: Meta CAPI postback preset

1. Open Postbacks → Create.
2. Choose the Meta CAPI preset.
3. Set the recipient to the traffic source.
4. Paste Pixel ID and access token. Optional: Test event code.
5. Set Event name (default Lead) and Action source (website when you have browser ids; system_generated when you do not).
6. Under User data, enable Meta fields (em, ph, fn, …) and map placeholders such as {{lead.payload.email}} for em. Hashed fields are normalized and SHA-256 hashed at fire time. Leave fbc empty to rebuild from fbclid when present.
7. Under Custom data, keep value source = payout for traffic-source users. Set currency and any extra rows.
8. Choose triggers — typically lead_sold. Add min_payout or match rules if needed.
9. Save → run Test → confirm in Meta Test Events or Overview.

Hardcoded country when the lead has no country: {{||fallback:US||meta_hash:country}}.

Optional: Campaign Meta CAPI integration (shared pixel only)

Use this only when one company-owned pixel should fire for a campaign.

1. Open Integrations → Meta CAPI and enter the shared Pixel ID and access token.
2. Open the campaign → Integrations → toggle Meta CAPI ON.
3. Optional: Override Settings for that campaign (trigger, event name, action source, test code, mappings, value source).
4. Save and verify in Meta Test Events and the integration Usage Log.

Remember: this remains one global credential set and one enabled setup per campaign — not per traffic source.

Expected result

• Meta receives a CAPI event with hashed user data
• On the preset path, each traffic source can use its own pixel and triggers
• Test-coded events stay under Test Events until you remove the code

Troubleshooting

• Need per-affiliate pixels — switch to the Postbacks Meta CAPI preset; the integration path cannot do this
• No events in Meta — wrong pixel/token, trigger mismatch, or you are viewing Overview while a test code is set
• Low match quality — send more user_data (em, ph, fn, ln, fbp/fbc, IP, user agent)
• Missing fbc — ensure the click carried fbclid, or map fbc explicitly