Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Meta Ads

Pixel, Conversions API and Measurement

Meta can only optimise towards and report on the events you send it, matched to the people it showed ads to, within the attribution window you set. The pixel and the Conversions API are the two routes those events take, Events Manager is where they are checked, and the attribution setting decides what counts. This hub explains the stack, points to the core guides and to further guides on reconciling with orders and moving a website, and covers why Meta's figures differ from analytics and where incrementality measurement fits.
SectionintermediateUpdated

Learn this as a path

Prefer a guided order? These learning paths read pages from this section in sequence, with exercises and checkpoints.

In this section

What Meta counts and how it learns from it

A result on Meta is an event: a page view, a view of content, an add to cart, a lead, a purchase, an app install, or a custom action you define. Meta documents a set of standard events with recognised names and optional parameters such as value and currency, alongside custom events and custom conversions built from URL or event rules. The event you choose as the ad set's optimisation event is what delivery works towards; the events you report on are what the columns in Ads Manager show. The two should usually be the same, and the campaign objectives guide explains how the objective narrows which events an ad set can optimise for.

Delivery learns from events in a direct way. Each matched event tells the system something about the kind of person who converts, and it uses that to find more of them. An event that fires unreliably, fires on the wrong action or cannot be matched to a person therefore does more than spoil a report; it teaches the system the wrong lesson. Cost per acquisition (CPA) and conversion rate (CVR) are only as meaningful as the event behind them, which is why the CPA calculator and the conversion rate calculator are useful only once the event definitions have been checked.

The stack: pixel, Conversions API, Events Manager, attribution

LayerWhat it doesWhere it fails
Meta PixelA browser script that sends events from the site, with the browser's identifiers and whatever customer information is passedBlocked by browsers and consent choices; fires on the wrong trigger; missing parameters
Conversions API (Conversions API)Sends the same events from your server or a connector, carrying hashed customer information for matchingDuplicates the pixel unless deduplicated; poor match quality when few identifiers are sent
Events ManagerThe console where events arrive, are tested, diagnosed, scored for match quality and prioritisedIgnored after setup; warnings left unread
Attribution setting (Attribution)The window after a click or view within which a matched event counts, set per ad setChosen by default; compared across ad sets with different settings
Aggregated and modelled reportingMeta's statistical fill-in where identifiers are missing, documented alongside its privacy changesTreated as exact; broken down where Meta withholds breakdowns

Meta's recommendation is to run the pixel and the Conversions API together, sending the same events through both with a shared event identifier so the platform can deduplicate them. The pixel captures what the browser allows; the server route recovers events the browser loses to blocking, consent or connection failures, and can carry identifiers the browser never had. Events Manager's match quality score indicates how well the identifiers you send let Meta match events to people, and raising it is most of the practical work in the Conversions API guide.

The core guides

  1. Meta Pixel setup — a tutorial from creating the pixel through installing it, defining standard events and parameters, testing in Events Manager, consent and domain verification, and the checks that confirm the right event fires on the right action.
  2. Conversions API — what the server route adds, the integration options from partner connectors to direct implementation, deduplication with the pixel, match quality and how to raise it, and how to tell whether it is recovering anything.
  3. Attribution settings — what the window controls in optimisation and in reporting, click and view windows, comparing settings in reports, modelled conversions, and choosing a setting by objective.

Measurement on Google's platform solves the same problems with different tools; the Google Ads measurement hub is the parallel section, and the two are worth reading together when an account runs on both. The wider analytics hub covers measurement that spans channels: dashboards, cross-channel attribution models and the privacy changes shaping all of it. The author's paid media analytics expertise page describes how platform reporting is reconciled with the rest in practice.

Further guides

Further guides check Meta's figures against the business's own records and keep the stack working when the website changes:

Why Meta and analytics disagree

They disagree because they are counting different things under different rules, not because one is broken. Meta credits a conversion to an ad if a matched person clicked or viewed it within the attribution window, and reports the conversion against the date of that interaction. A web analytics tool typically credits the last source the browser can see, usually from a click, on the date the conversion happened, with no knowledge of views at all. Add consent and blocking that affect each tool differently, Meta's modelled fill-in where it loses identifiers, and the fact that a person can be one individual to Meta and three browsers to analytics, and the gap is expected. The attribution settings guide covers how to narrow it to the causes you can act on; the general question of how credit should be divided among touchpoints is the subject of the attribution models framework and the analytics hub.

Measurement beyond the platform: incrementality

Platform attribution answers "which of our ads did this person interact with before converting". It cannot answer "would they have converted anyway". For retargeting, for brand audiences and for any campaign reaching people already close to buying, the difference between the two is large. The method that answers the second question is an Incrementality test: a randomly held-out group that does not see the ads, compared with the group that does. Meta offers conversion lift studies through its experiments tooling, documented in the Help Centre, and geographic holdouts can be run without the platform's help. Neither is cheap in budget or patience, which is why they are run for decisions large enough to deserve them — whether a channel is worth its budget, not whether an ad is worth its place — and why the day-to-day account runs on platform attribution with the lift results as a correction factor.

Illustrative example — not a real result

A furniture retailer finds its real cost per order

A furniture retailer reports 640 purchases a month from Meta at £31 each in Ads Manager, while its analytics tool shows 290 last-click purchases from paid social. Events Manager shows the purchase event arriving through the pixel only, with a match quality score of 4.2 out of 10, and the ad sets use the default seven-day click, one-day view window. After adding the Conversions API with hashed email and phone, match quality rises to 7.8 and reported purchases rise to 710, mostly on the one-day view side. A conversion lift study over six weeks, with a 10% holdout, then estimates that about 55% of attributed purchases were incremental. The retailer keeps optimising on the platform number, sets its true cost per incremental order at roughly £56, and uses that figure, not the Ads Manager one, when deciding the following quarter's budget.

Common measurement problems

SymptomLikely causeWhere to look
Purchases in Ads Manager far above sales in the back officePixel and Conversions API both sending without deduplication, or the event firing on the wrong pageConversions API guide, deduplication; pixel setup, triggers
Reported results fell after a consent banner or browser changeBrowser events lost; no server routeConversions API guide
Browser events arrive in Events Manager but server events are missing or stoppedA test event code left live, the wrong dataset, a stopped integration or server container, rejected payloads or a consent checkDiagnosing Conversions API events that are not showing
Low match quality warning in Events ManagerFew or badly formatted customer identifiers sentConversions API guide, match quality
Two ad sets with the same ads report very different cost per resultDifferent attribution settingsAttribution settings, comparing windows
Recent days look poor, then improve over the following weekReporting by interaction date with an open window, plus delayed and modelled dataAttribution settings, modelled conversions
Delivery optimises towards an event that is not the business outcomeWrong optimisation event or a micro-conversion chosen for volumeCampaign objectives guide
Meta and analytics disagree by a wide marginDifferent attribution, dates and identity rulesThis page; attribution settings, reconciling
Events Manager shows no activity, or Test Events stays emptyBase code missing, wrong dataset, an unpublished container or a consent holdDiagnosing pixel events that are not showing
Purchases counted twice after the Conversions API went liveBrowser and server copies without a shared event ID, or two sendersFixing duplicate Conversions API events
Match quality rating stays low on the optimised eventThin, badly formatted or consent-limited customer parametersDiagnosing low event match quality
Nobody can say how far Meta's results should differ from the business's own orders or leadsNo reconciliation over a closed period, and no ratio tracked over timeReconciling with orders
Events stopped, doubled or changed after a new site or platform went liveDataset, events, Conversions API route or URL rules not carried over in the moveMoving a website without breaking Meta Ads

When a number looks wrong, check in order: is the event firing on the right action, is it arriving once, is it matching, and only then which window and which other system it is being compared with.

Terms used on this page

Tools to try

Frameworks

Sources

  1. Meta Business Help Centre — Meta Business Help Centre

Related