Skip to content

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.

Start freeSetup steps

Basic and upClick-to-WhatsApp ad leads onlyChecked before it is saved

Illustration: a woman at a café table, smiling at her phone

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.

  • Checked before it is saved

    A website pixel cannot receive conversions from chats. Fliok tests your dataset first and says so.

  • See what was sent

    Reported and waiting counts, when the last one went, and Meta’s own words if it refuses one.

Setup

Connect the Conversions API in 3 steps

  1. 1In Fliok

    Use my WhatsApp connection

    Settings → Integrations → Send results back to Meta: Fliok uses the dataset of your WhatsApp account, nothing to paste. Pending Meta’s review.

  2. 2In Events Manager

    Or paste a dataset and token

    Pick the dataset of your WhatsApp account (not your website pixel), make a token under Settings → Conversions API, save both in Fliok.

  3. 3In Fliok

    Test, then go live

    With a test event code set, events show under Test Events so you can check them. Meta still uses them, so test with a few, then clear it.

PlanBasic and above
How it connects
One switch with your WhatsApp connection, or your dataset ID and an access token
Compare plans

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.

Got questions?

Questions about the Conversions API

Anything else, ask us.

What is the Conversions API for WhatsApp ads?

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.

Which outcomes are reported?

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.

Do I need the AI agent for it?

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.

Why a dataset and not my website pixel?

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.

Is my customer’s number sent to Meta?

Only as a hash, alongside the ad’s own tag and your WhatsApp account’s id. No name and no message text is sent.

Which plan do I need?

Basic or above: ad attribution and reporting are part of Automation & CRM. An admin or the owner sets it up.

Keep exploring

Related

All integrations

Credit your ads with what they really brought

Start on the Free plan, then connect the Conversions API on Basic or higher.

Start freeRequest a walkthrough

Free forever plan · Keep your WhatsApp app