Native integration

Ads that learn from what actually sold.

When a Click-to-WhatsApp ad starts a conversation, the ad's click id is stored on the conversation. When your system posts a conversion, it is attributed to that ad and reported to Meta's Conversions API, so Meta can optimise the campaign on purchases rather than clicks.

How Meta Conversions API connects

In order. A person on our side does this with you during onboarding if you prefer.

  • Referral capture on every ad-started conversation
  • Conversions attributed to the ad, the campaign and the journey
  • Events reported to Meta's Conversions API with a delivery log
  • Ad spend by hand or CSV, with cost per lead and per conversation
  1. 1

    Add the dataset id

    In Settings, under the WhatsApp account, paste the Conversions API dataset id from Meta Events Manager.

  2. 2

    Run Click-to-WhatsApp ads

    Each conversation that starts from an ad carries Meta's referral data, including the click id, which the product stores on the conversation and the contact.

  3. 3

    Post conversions

    Your store, CRM or a Zap posts a conversion with the customer's number, a value and an optional order id to the conversions endpoint.

  4. 4

    Check the delivery log

    Each event sent to Meta is logged with Meta's response, and the ads analytics show revenue, cost per lead and cost per conversation by ad.

A D2C launch on Instagram ads

Every order from an ad-started chat is reported back to Meta, so the ad set optimises on buyers and the analytics show revenue per ad, not just conversations.

Lead-gen for real estate

A site visit booked is posted as a conversion, so the ads learn which creatives bring people who actually visit.

Questions

Is this the same as the Meta pixel?

It is the server-side counterpart for conversations: the pixel tracks a website, the Conversions API accepts events from a server. Conversations from Click-to-WhatsApp ads carry a click id that lets a conversion be tied back to the ad without a website at all.

Do I need a developer?

Posting a conversion is one HTTPS call. A store or CRM integration, a Zap or a Make scenario can do it; a developer is only needed if the system has no automation tool.

Other integrations

Built on the developer platform. See pricing: integrations are included, not add-ons.

Talk to us.

In a forty-minute call we go through what you send today, what it costs you, and what a flagged number would cost you. Then we set up a workspace on your own Meta app and build the first campaign with you.