Skip to content

Browse the documentation

Meta

Pixel plus Conversions API, tokens and scopes, Test Events, multi-pixel and match quality — the full Meta reference.

updated

Outline — facts still to be confirmed

This article is a structured outline. Its headings and scope are settled; the specific values, screens and steps are marked TODO(owner: verify) until they have been checked against the plugin itself. Blueprint §7 is explicit that no article may state plugin behaviour that has not been verified.

Pixel and Conversions API together

Both halves of every dual-flow event carry one shared event ID, which is what lets Meta merge them into a single conversion. The mechanics are covered in Verify your first event.

The plugin talks to Meta’s Graph API at version v25.0.

Tokens and scopes

Covered in full in Token error #100, including the two Events Manager radio options and why Verify posts a Test Event instead of performing a read.

Test Events

  • Setting a Test Event Code switches server sending to synchronous, so results appear immediately instead of waiting for the queue.
  • The tab shows browser events only from the session that has it open — see step 3 of Events don’t show.

Multi-pixel

Settings hold a list of pixel configurations, each with its own ID, token, test code and enabled flag. Events fan out to every enabled pixel carrying the same event ID, and each one has its own verify control.

TODO(owner: verify) — screen layout and field labels; what happens to per-pixel test codes; whether fan-out is per-event-type configurable; migration behaviour for installs that predate multi-pixel.

Match quality (EMQ)

Reading your match quality scores back from Meta requires the Dataset Quality read scope, which is what the “Set up with Dataset Quality API” token option grants. Scores are cached rather than fetched on every page load.

TODO(owner: verify) — cache duration, exactly which scores are displayed, and what the plain-language recommendations say. Do not document a dashboard that has not been confirmed in the shipped build.

Outline still to fill

  • Advanced matching: which parameters the browser half carries.
  • Behaviour when a token is rotated mid-queue.
  • What appears in the log for a rejected event, and how to read a fbtrace_id.

Was this page helpful?