Meta Conversions API sends conversion events from your CRM server to Meta for ad attribution and optimisation. Connect it under Settings → Integrations → Ad Platforms → Meta.
Setup: In Meta Events Manager, copy your Pixel / Dataset ID and generate a Conversions API access token. Paste both into Henkan, optionally add a Test Event Code, choose Standard (Purchase) or CRM Conversion Leads format, then Save and Test Connection.
Meta Lead ID: For stronger matching, send Meta’s lead ID into Henkan via Zapier (or another form tool) → inbound webhook and map Meta Lead ID. Optional fbclid/fbc/fbp fields improve click matching further. Native Lead Ads inbound (direct from Meta) appears on the Meta card only when the Henkan Meta App is configured on the server.
Strongest matching: Events include hashed email, phone, first/last name, CRM external_id (lead UUID), Meta lead ID, and fbc/fbp/fbclid when stored. Leads that have a Meta Lead ID automatically use CRM Conversion Leads-style matching on deal won. A lightweight Lead event can also fire when a Meta lead is created.
Values: Currency and line-item deal types include monetary value. Non-currency metrics (litres, units, tonnes, etc.) send the conversion with no monetary value.
TikTok Events API, LinkedIn Conversions API, and Google Ads Enhanced Conversions are also available on the same tab.
