The Conversions API is available on the Pro and Enterprise plans. See
Plans & pricing.
How it works
Each client gets their own Meta pixel configuration and a universal snippet. When a visitor completes an action on the client’s site, the snippet reports the conversion to Meta’s servers with high-quality match data — improving attribution and optimization.Set up a client
Enter the pixel details
Paste the client’s Pixel / Dataset ID and a Meta access token.
Optionally add a test event code to verify before going live. In-app
links walk you through where to find each in Meta Events Manager.
Choose what to match on
Pick which customer details the client’s form collects — email, phone, name,
ZIP, city, state, country, and more. Signals like IP, user agent, and Meta
click/browser IDs (
fbc / fbp) are captured automatically.Define the conversion event
Choose a standard Meta event (e.g. Lead, CompleteRegistration,
Purchase) or a custom one, and how it fires — on form submit or when
a thank-you URL loads. You can add extra URL-based events and a
conversion value.
Where to paste the snippet
The snippet goes in the site<head> on every page with the form (and the
thank-you page for URL events). Common builders:
| Builder | Where |
|---|---|
| GoHighLevel | Sites → your funnel/website → Settings → Head Tracking Code |
| WordPress / Elementor | A header-scripts plugin (e.g. WPCode), or Elementor → Site Settings → Custom Code → <head> |
| Webflow | Project Settings → Custom Code → Head Code, then Publish |
| Unbounce | Page → Settings → Javascripts → placement Head |
| Custom HTML | Just before </head> on every page with the form |
Connection status
Each client shows a status on the Conversions API page:| Status | Meaning |
|---|---|
| Pending setup | Configured, no events received yet |
| Receiving (test) | Test events arriving, not yet counted as real conversions |
| Live | Real conversions flowing to Meta |