Meta Conversions API

Meta Conversions API setup for lead generation and eCommerce

Our Meta Conversions API setup sends conversion events from your server and CRM directly to Meta, alongside the browser pixel, so the ad algorithm sees the results that matter: qualified leads, booked calls, signed clients and purchases. In our lead generation accounts it recovered 31% more events than the pixel alone.
Book a strategy call ↗See 275+ client results ↗
Quick answer

What does a Meta Conversions API setup involve?

It connects your website and CRM to Meta's servers: events such as Lead, QualifiedLead, Schedule and Purchase are sent server-side with hashed email and phone, deduplicated against the pixel with a shared event ID, and checked for Event Match Quality. Ads can then optimize for real outcomes instead of form fills.

Why the pixel alone is no longer enough

Browser privacy settings, ad blockers and short cookie lifetimes mean the pixel misses a large share of conversions. In our accounts, adding the Conversions API recovered 31% more events and cut cost per qualified lead 37% after 21 days of offline events. The terms are defined in what is the Meta Conversions API and what is the Meta pixel.

What we set up

  1. The event ladder. For lead generation: Lead, QualifiedLead, Schedule, Attended, Purchase. For eCommerce: ViewContent, AddToCart, InitiateCheckout, Purchase with value.
  2. Server-side sending from your site, tag manager or CRM workflows.
  3. Deduplication with a shared event ID so browser and server events are counted once.
  4. Customer information parameters: hashed email and phone, click ID, IP and user agent, to push Event Match Quality above 8.
  5. Offline CRM events for booked, attended and won deals.
  6. Google Enhanced Conversions mirrored where Google Ads is used.

The full technical walkthrough is in our Conversions API guide for lead generation.

Who needs it most

Any account where the valuable event happens after the form: signed cases, funded loans, signed roofing contracts, and eCommerce purchases where value-based bidding needs accurate revenue. After setup, check whether ads are profitable with the ROAS calculator.

What to expect after setup

Expect a learning period of about 14 days while Meta adjusts to the new signals. Cost per lead can rise slightly at first when the campaign optimizes for qualified leads instead of all leads; cost per signed client or purchase is the number that should fall. Platform choices that affect tracking are discussed in GoHighLevel vs HubSpot.

Proof from client campaigns

See eCommerce results ↗

Meta Conversions API

Frequently asked questions.

Do I still need the Meta pixel with the Conversions API?

Yes. Meta recommends running both: the pixel captures browser events in real time, the Conversions API sends the same events from the server plus events that never happen in a browser, such as a signed contract. A shared event ID deduplicates them so nothing is counted twice.

What is Event Match Quality?

Event Match Quality is Meta's score, from 0 to 10, for how well an event can be matched to a Meta account, based on the customer information sent with it. Hashed email, phone, click ID and IP raise it. We aim for 8 or higher, which improves attribution and optimization.

Can my CRM send events to Meta?

Yes. GoHighLevel workflows can send pipeline stage changes, such as qualified, booked, attended and won, to Meta as server events through a webhook or native integration. HubSpot and other CRMs can do the same through integrations or a server-side tag manager.

How long until results improve?

Allow about 14 days of learning after the new events start flowing, longer at low volume. In our lead generation accounts, cost per qualified lead fell 37% after 21 days of offline events, but the first week can look worse as the campaign re-optimizes.

Is the Conversions API privacy compliant?

Customer data is hashed before it is sent, and only data the customer provided and consented to sharing should be used. You still need a privacy policy covering advertising measurement, and consent rules in your region apply. We set it up to send the minimum data needed.

FTP automation robot

We
build
with
Robots.Let's Talk

Talk with us →

We're a small team of strategists, builders and automation nerds, blending funnels, follow-up and AI calling so your leads turn into booked calls, not cold contacts.