Get Free Tracking Audit
● Meta / Facebook Tracking

Meta Conversions API Setup for Advertisers

We connect your site or store to the Meta Conversions API so key conversions reach Meta from your server as well as the browser. Events are sent with a shared event ID for deduplication and the customer parameters Meta uses for matching. For advertisers who want Events Manager to reflect real orders and leads.

Get Free Tracking Audit Talk to GrowthUper
Meta Conversions APIIllustrative
  1. Conversion
  2. Event ID Created
  3. Pixel Event
  4. Server Event
  5. Meta Deduplication
  6. Ads Optimization
What this covers
  • Server events for key conversions
  • Event ID deduplication with the pixel
  • Customer parameters for match quality
  • Events Manager coverage review
Platforms
Meta Conversions APIMeta PixelMeta Events ManagerServer-side GTMShopify or WooCommerce
Best for

Meta advertisers who see missing conversions or low event match quality in Events Manager

01 The problem

Why Meta Is Not Seeing All of Your Conversions

A pixel-only setup depends on the browser. A rushed Conversions API setup often creates new problems, such as double counting or server events that carry almost no customer data.

  1. 01

    Blocked Browser Events

    Ad blockers and browser privacy features stop some pixel requests, so conversions happen but Meta never hears about them.

  2. 02

    Double Counted Purchases

    Server and browser events sent without a matching event_id and event_name are counted as two separate conversions.

  3. 03

    Server Events With Little Data

    CAPI events without hashed email, phone, fbp or fbc get low match quality and help Meta far less than they should.

02 What we implement

What We Build Into Your Conversions API Setup

The focus is on what Meta needs from each event: the right event name, a shared ID with the pixel, and enough customer information to match the conversion to an ad viewer.

  • 01

    Conversion Event Selection

    We decide which events go through CAPI, usually Purchase, Lead and other events you optimize for.

  • 02

    Event ID Deduplication

    A shared event_id generated once and sent with both the pixel and the server event.

  • 03

    Customer Information Parameters

    Hashed em, ph, fn, ln and external_id, plus client IP address and user agent, sent where available.

  • 04

    fbp and fbc Forwarding

    The browser ID cookie and click ID captured on site and passed with each server event.

  • 05

    Integration Method

    Native partner integration, CAPI Gateway or server-side GTM chosen to suit your platform.

  • 06

    Event Match Quality Review

    Match quality and deduplication checked per event in Events Manager after launch.

03 Live data flow

How a Conversion Reaches Meta Twice and Is Deduplicated

The same conversion is sent from the browser and the server with one shared event ID. Meta keeps one and uses the richer customer data for matching.

Meta Conversions API data flowIllustrative
  1. 01ConversionOrder placed or lead submitted
  2. 02Event ID CreatedOne ID shared by browser and server
  3. 03Pixel EventBrowser sends event with fbp and fbc
  4. 04Server EventCAPI sends event with hashed customer data
  5. 05Meta DeduplicationMatching event_name and event_id merged
  6. 06Ads OptimizationOne conversion attributed to the ad
04 How it works

From audit to validated data.

How Meta Conversions API projects run. Nothing goes live until it has been tested.

  1. 01

    Audit

    Audit pixel events, existing CAPI events and current match quality scores.

  2. 02

    Strategy

    Choose the CAPI method, the events to send and the customer data to include.

  3. 03

    Implementation

    Implement server events with event IDs and hashed customer parameters.

  4. 04

    Testing

    Test server and browser pairs in Test Events and confirm deduplication.

  5. 05

    Validation

    Validate event counts and match quality in Events Manager after launch.

05 Deliverables

What's Included in Meta Conversions API

Everything is documented and handed over, so your team knows exactly what was built and why.

  • 01

    Current Event Coverage Audit

    We compare your pixel and any existing server events against real orders or leads to find where coverage falls short.

  • 02

    Conversions API Integration

    Server events configured through the method that suits your platform, with access tokens stored securely.

  • 03

    Deduplication Setup

    Event IDs wired through the data layer so browser and server events pair correctly.

  • 04

    Match Quality Parameters

    Customer information fields normalized and hashed with SHA-256 before they are sent.

  • 05

    Test Events Verification

    Every server event checked in Test Events, with deduplication confirmed in the event overview.

  • 06

    CAPI Documentation

    A reference of events, parameters, event ID logic and the integration method, handed to your team.

Platforms

The tools involved in a typical Meta Conversions API implementation.

  • Meta Conversions APIServer events
  • Meta PixelPaired browser events
  • Meta Events ManagerMatch quality and dedup
  • Server-side GTMOptional event routing
  • Shopify or WooCommerceOrder and customer data
06 QA and testing

Tested before anything goes live.

Test server and browser pairs in Test Events and confirm deduplication.. Validate event counts and match quality in Events Manager after launch..

QA checklistMeta Conversions API
  • Meta Pixel HelperBrowser events fire with the right parameterschecked
  • Test EventsServer events received and matched in Events Managerchecked
  • DeduplicationBrowser and server events share event_id and count oncechecked
  • Match qualityEvent Match Quality reviewed for each eventchecked

Each check is repeated after launch on live traffic.

07 FAQ

Meta Conversions API FAQ

Something else? Talk to GrowthUper

How does Meta deduplicate pixel and CAPI events?

Meta compares the event_name and event_id of browser and server events. When both match within the deduplication window, it keeps one event. The key is generating the event ID once, on the page, and passing that same value to both the pixel and the server request.

Which integration method will you use?

It depends on your platform and your other tracking. Shopify and some other platforms have native partner integrations. CAPI Gateway suits advertisers who want a managed option. Server-side GTM suits businesses that also send server data to GA4 or Google Ads. We recommend one and explain why.

How is this different from your server-side Meta CAPI service?

This service is about what Meta receives: which events, how they deduplicate and how well they match. Our server-side tracking category covers the infrastructure behind it, such as hosting and running a server-side GTM container. Many clients need only this service, others need both.

Can the Conversions API send offline or CRM conversions?

Yes. CAPI accepts events that happen outside the website, such as a lead marked qualified in your CRM or a sale closed by phone. We can send those with the customer data you hold so Meta can link them back to ad interactions.

Is customer data sent to Meta safely?

Customer information such as email and phone is normalized and hashed with SHA-256 before it is sent, as Meta requires. We only send fields you collect with a lawful basis and connect sending to your consent setup where needed.

Will event match quality reach a specific score?

We cannot promise a score. Match quality depends on what data your visitors provide and what you are permitted to send. We make sure every available parameter is sent correctly and show you which remaining fields could be added.

→ Next step

Get Meta Conversions API right the first time.

Build a tracking and measurement system you can trust.

Get Free Tracking Audit Talk to GrowthUper Free 30-minute review · No obligation
Scroll to Top