Meta Conversions API
| Status | Kind | How you connect |
|---|---|---|
| Coming soon | Ad platform (conversions) | One click: approve bubbl3 on Meta Conversions API's own page |
Meta Conversions API isn't offered yet. This page says what it will do and what you can use meanwhile: a Lead URL, or Zapier, Make or n8n.
What it does
When a lead from your Meta ads qualifies, books or buys, bubbl3 can tell Meta, so Meta can find more people like them. Connecting the Meta Conversions API lets you choose conversion events (such as "Lead qualified") and send each to a Meta dataset as a CRM conversion, with:
- the event name you map, its time and value;
- the Meta lead id, when the contact came from a Meta lead ad;
- the contact's email and phone, hashed with SHA-256 before they leave bubbl3.
Setup
You need full access to integrations in bubbl3, and admin access to the Meta business that owns the dataset.
- In bubbl3, open Settings, Integrations, choose Meta Conversions API, then Connect, and approve bubbl3 for your business on Meta's page.
- In Settings, Events, open an event and add a destination: this connection, the dataset id from Events Manager, and Meta's event name.
- Fire a test with Events Manager's test event code and check it shows under Test events.
Disconnect
Disconnect from the connection page in Settings, Integrations.
- Stops at once: conversion deliveries to Meta. Deliveries still waiting are not sent.
- Deleted at once: bubbl3's Meta access token.
- Kept: your conversion events and their delivery log in bubbl3. Events already sent stay in Meta.
Data shared
From bubbl3 to Meta: for each conversion: the event name, time, value and currency, an event id Meta uses to drop duplicates, the Meta lead id where there is one, and SHA-256 hashes of the contact's email and phone. Never the raw email or phone, and never anyone who opted out or has no consent record.
From Meta to bubbl3: your business's id and name, and Meta's answer to each delivery.
Scopes and permissions
| Permission | Why bubbl3 needs it |
|---|---|
ads_management | Send conversion events to your dataset |
ads_read | Read the dataset bubbl3 sends to |
pages_read_engagement | Match conversions to leads from your Pages |
Events
What bubbl3 receives
Nothing: Meta Conversions API only receives events from bubbl3.
What bubbl3 writes back
| What | Where it shows in Meta |
|---|---|
| Conversions | A CRM event in your dataset, in Events Manager |
Sending rules that still apply
Meta Conversions API never causes a text. bubbl3 sends it conversion events only for contacts who haven't opted out and have a consent record, and stops for a contact who opts out later. Emails and phone numbers are hashed with SHA-256 before they leave bubbl3.
Limits and known gaps
- Meta takes events up to seven days old; bubbl3 doesn't send older ones.
- Contacts who opted out, have no consent record, or opt out later never reach Meta.
Troubleshooting
- A delivery failed. The delivery log on the conversion event shows Meta's answer. A wrong dataset id or missing permission is refused and not retried.
- Events don't match leads. Matching works best for contacts who came from Meta lead ads (they carry Meta's lead id).