Meta Conversions API
Server-side event delivery to Meta's Conversions API for enhanced tracking accuracy and privacy compliance.
Meta CAPI is a server destination in the walkerOS flow:
Sends events server-side to Meta's Conversions API, bypassing browser limitations for improved data quality and privacy-compliant tracking.
Installation
- Integrated
- Bundled
Configuration
This destination uses the standard destination config wrapper (consent, data, env, id, ...). For the shared fields see destination configuration. Package-specific fields live under config.settings and are listed below.
Settings
| Property | Type | Description | More |
|---|---|---|---|
accessToken | string | Meta access token for Conversions API authentication | |
pixelId | string | Meta Pixel ID from your Facebook Business account | |
action_source | Source of the event (website, app, phone_call, etc.) | ||
doNotHash | Array<string> | Array of user_data fields that should not be hashed | |
test_event_code | string | Test event code for debugging Meta Conversions API events | |
url | string | Custom URL for Meta Conversions API endpoint | |
user_data | Record<string, string> | Mapping configuration for user data fields |
Mapping
This package does not define custom rule-level settings. For the standard rule fields (consent, condition, data, batch, name, policy) see mapping.
Examples
Form submit
A form submission is forwarded to Meta CAPI as a custom event with the event source URL.
Purchase
A completed order is sent to the Meta Conversions API as a Purchase event with value, currency, and contents.
Purchase with fbclid
A purchase is sent to Meta CAPI with an external_id and a formatted fbc click id for ads attribution.