Meta Conversions API integration
Tell Meta which ad chats became customers
When a Click-to-WhatsApp ad lead becomes an enquiry, a quotation or a sale, Fliok reports that outcome to your Meta dataset.
Basic and upClick-to-WhatsApp ad leads onlyChecked before it is saved
- Ad
- Festive offer · 2 BHK
- Meta’s tag
- Kept on the lead
- Need
- 2 BHK, Rajarhat
- Budget
- Shared in chat
- Event
- InitiateCheckout
- From
- WhatsApp · business messaging
- Customer’s number
- Hashed before it is sent
What it does
What you get with the Conversions API
Drawn with the dashboard’s own pieces, with sample data.
Three outcomes, reported
A lead who gave their requirements, a quotation and a sale each go to Meta as an event of its own.
What is reported- Gave requirementsLeadSubmitted
- QuotedInitiateCheckout
- WonPurchase
One event of each kind for a conversation, however often its status movesChecked before it is saved
A website pixel cannot receive conversions from chats. Fliok tests your dataset first and says so.
Dataset ID1234567890123456In Events Manager, pick the dataset connected to your WhatsApp account — not the pixel named after your website. A website pixel cannot receive conversions from chats, and we check before saving.
See what was sent
Reported and waiting counts, when the last one went, and Meta’s own words if it refuses one.
Tell Meta which ads actually workedConnectedReported412Waiting3- Dataset ID
- 1234567890123456
- Access token
- ••••••••••••
- Test event code (optional)
- —
The token is stored encrypted and never shown again
Setup
Connect the Conversions API in 4 steps
- 1In Events Manager
Find your dataset
Pick the dataset connected to your WhatsApp account, not the pixel named after your website.
- 2In Events Manager
Generate an access token
Under Settings → Conversions API. Fliok stores it encrypted and never shows it again.
- 3In Fliok
Paste both in Fliok
An admin opens Settings → Integrations → Meta Conversions API and saves the dataset ID and the token.
- 4In Fliok
Test, then go live
With a test event code set, events show under Test Events and stay out of ad optimisation. Clear it when ready.
Good to know
- Only chats that started from a Click-to-WhatsApp ad are reported: any other chat has no ad to credit.
- One event of each kind for a conversation, however often its status moves.
- The customer’s number is sent as a hash. An amount is sent only when one is known; no message text is sent.
- Meta accepts an event up to 7 days after it happened. An older outcome is set aside, not sent.
- Fliok reports what happened. What Meta’s ad delivery does with it is decided by Meta.
A way to tell Meta what happened after someone tapped your Click-to-WhatsApp ad. Meta tags each ad chat, and Fliok keeps that tag on the lead. When the chat becomes an enquiry, a quotation or a sale, Fliok sends that outcome to your dataset with the tag, so the ad is credited with more than the tap.
Three. When a lead has given their requirements, Meta receives LeadSubmitted; when the conversation is quoted, InitiateCheckout; when it is won, Purchase. A sale is taken from whichever comes first: Fliok AI marking the chat as won, a payment recorded on the lead, or someone moving the lead to a Won stage.
For the first two outcomes, yes: they come from the status Fliok AI gives a conversation as it answers. A sale is also reported when a payment is recorded on the lead or a person moves the lead to a Won stage.
A website pixel cannot receive conversions from chats. Use the dataset connected to your WhatsApp account in Events Manager. Fliok sends a test event when you save, and tells you if the dataset cannot take them.
Only as a hash, alongside the ad’s own tag and your WhatsApp account’s id. No name and no message text is sent.
Basic or above: ad attribution and reporting are part of Automation & CRM. An admin or the owner sets it up.
Credit your ads with what they really brought
Start on the Free plan, then connect the Conversions API on Basic or higher.
Free forever plan · Keep your WhatsApp app