Skip to content
Mather Media Solutions
Start

03 · Tracking & measurement

Meta Pixel and CAPI without the double counting

Browser events, plus server events when they solve a real problem, sharing one event ID so Meta can tell one purchase arriving twice from two purchases.

Are we counting the same purchase twice in Meta? When the Pixel and the Conversions API both send an action without a shared event ID, Meta can record one purchase as two. Meta tracking can use the Pixel in the browser, the Conversions API from a server or partner integration, or both. The implementation starts with business and dataset ownership, then defines the events, fields, consent path, and delivery method. When browser and server both send one action, a shared event ID tells Meta it happened once.

Start the tracking audit

Start with the tracking audit

Why buyers call

Meta is getting some purchases twice and some not at all, and the dataset sits in a Business account we do not fully control.

What gets done

Inside the scope

  1. 01

    Confirm Business Portfolio, dataset, domain, partner, and account ownership before any migration decision

  2. 02

    Configure standard events with the value, currency, content, location, or lead fields the journey supports

  3. 03

    Choose the Pixel, a partner integration, a gateway, or direct CAPI based on the actual need

  4. 04

    Implement event-ID deduplication and inspect Test Events and diagnostics

How it is proved

Verification standard

The controlled event is inspected in the browser or integration source and in Meta Test Events. When two paths are used, they must share the same event ID so the action can be deduplicated.

What you receive

The handoff

  • Configured Pixel and appropriate server path
  • Event and field map
  • Deduplication evidence
  • Ownership, diagnostics, and handoff notes

Result

Meta events sent through an intentional path, deduplicated, and held in a dataset the business owns.

Questions that come up

  • Do we automatically need Conversions API?

    No. CAPI adds implementation and maintenance. It is used when a server or partner path solves a real reliability or control problem, not because a more complicated diagram looks better.

  • Who should own the Meta dataset?

    The client should control the Business Portfolio and dataset whenever the platform allows it. If an agency currently owns them, the audit documents what can be shared and whether a separate migration decision is needed.

  • What prevents double counting?

    When browser and server send the same action, both carry the same event ID. Meta can then recognize one action arriving by two routes instead of treating it as two conversions.

Start the tracking audit

The first paid step checks the journey and defines the smallest useful build.

Send the domain, the customer journey, and the platforms that should receive it. The tracking audit shows what is working, what is missing or duplicated, and the exact build recommended next.

Start the tracking audit

Paid, fixed scope · Within ten business days after complete access