True Conversionsby Nexopath

Connecting Meta (Facebook)

The Meta Conversions API (CAPI) integration is available. Once connected, True Conversions sends your CRM milestones (qualified lead, proposal, deal won) straight to the Meta dataset, server-side — it works in both Journey mode and Value Optimization mode.

True Conversions sends conversion events. It does not create, edit, or manage campaigns or ads.

What you'll need first

  • A Meta Business account with access to the advertiser's ad account.
  • A Pixel / Dataset configured in Events Manager.
  • An account already created in True Conversions.

Step by step

  1. Open the client account under Dashboard → Contas → [your account].
  2. Click Ad Integrations.
  3. Click Connect Meta.
  4. In Meta's dialog (Facebook Login for Business), authorize the correct business, ad account and dataset/pixel. Double-check the names before approving — this is what decides where conversions land.
  5. Return to True Conversions. The Meta card's status becomes Ativa (active).
  6. Enter (or confirm) the Dataset / Pixel ID. You'll find it in Events Manager; Pixel ID and Dataset ID are the same identifier — Meta unified the two terms.
  7. Only for messaging conversions from click-to-WhatsApp ads: enter the WhatsApp Business Account (WABA) ID. You paste this ID yourself (Business settings → Accounts → WhatsApp accounts). True Conversions never fetches it via API. If you don't run click-to-WhatsApp ads, leave the field empty — all other leads are unaffected.
  8. Click Salvar configuração (Save).
  9. Configure the Meta event for the relevant CRM stages:
    • Journey mode: pick the event per stage on the Jornada de conversão page.
    • Value Optimization mode: use the Evento Meta column on the Value Optimization page.
  10. Verify delivery on both sides: under Eventos recentes in True Conversions (the send shows as enviado) and in Meta's Events Manager, on the connected dataset.

The "Account health" card

Once connected, the Ad Integrations page shows the Saúde da conta — últimos 7 dias (Account health — last 7 days) card: impressions, clicks, reach, spend and conversions for the connected ad account, plus its name and ID.

Its main job is to confirm which account was connected. The figures cover that account's last 7 days: if nothing was delivered in that window, zeros are a valid result — they don't indicate a broken connection or a broken integration.

What gets sent

Once connected, True Conversions sends hashed PII (SHA-256), the fbclid (if mapped — see Field Mapping), and conversion details (event, timestamp and, where applicable, value) via the Conversions API. This improves Event Match Quality (EMQ) in Events Manager.

To get the most out of the integration, make sure the True Conversions GTM tag is installed (see Setup & Tracking) — it captures fbclid in addition to gclid — and include email, phone, name, and fbclid in the account's field mapping.

Click-to-WhatsApp ads

Conversions from conversations started by click-to-WhatsApp ads are sent to Meta through the Conversions API. The flow: your attendance platform forwards the click's ctwa_clid in the first-message webhook → True Conversions stores that identifier and joins it to the CRM lead by phone number → as the deal advances, the conversion goes to Meta carrying the ctwa_clid and the WABA ID.

What your setup needs in place:

  • A chatbot/attendance platform that forwards the ctwa_clid in the first-message webhook. ManyChat has a supported path; Wati, as far as its public documentation shows, does not expose this field. Without ctwa_clid there is nothing to attribute — confirm this on your platform before configuring.
  • The WABA ID filled in on the Meta card.
  • The plain WhatsApp Business app, with no webhooks, is not supported.

To verify, start a conversation from a real click-to-WhatsApp ad and follow the capture in the dashboard and the event in Meta's Events Manager.

Connection problems?

See Troubleshooting.