The 3-minute setup (Meta)

Meta setup is two values: your Pixel ID and a Conversions API access token, both pasted into the plugin. There is no OAuth step and no app review. Before you paste a real token, set a Test Event Code — that one step is the difference between testing safely and writing test events into your live reporting permanently.

Step 1 — set a Test Event Code first

In Meta Events Manager, open your dataset, go to the Test Events tab, and copy the test event code shown there. Paste it into PixelCapi before you paste your token.

Why first: test events sent without a test code go into your dataset’s real reporting, and individual events cannot be deleted. They age out of the reporting windows eventually, but a stray test purchase will sit in your numbers until they do. With a test code set, events go to the Test Events tab instead, and the plugin also switches to synchronous sending so you see them immediately rather than waiting for the queue.

Step 2 — get the Pixel ID

Events Manager shows the dataset (pixel) ID next to its name. It is a long number. Copy it.

Step 3 — get a Conversions API token

In Events Manager, go to Settings → Conversions API → Set up manually and generate an access token.

Meta offers two radio options at this point, and the difference matters:

• “Set up with Dataset Quality API” — Meta marks this one Recommended. It adds a read scope (read_ads_dataset_quality) on top of the write permission, which is what a match quality dashboard needs in order to read your scores back.
• “Set up without” — a plain write token. It can send events perfectly well; it just cannot read anything back.

Either one can send conversions. Pick the Dataset Quality option if you want match quality figures read from Meta; pick the plain one if you do not.

If you ever need to see what a token actually carries, Meta’s access token debugger lists its scopes and which pixel it is bound to. That page is the fastest way to settle an argument about permissions.

Step 4 — paste and verify

Paste the Pixel ID and the token, save, then press Verify.

Verify sends a real Test Event. It does not do a read check, and that is deliberate: Conversions API tokens are write-only, so a read against the pixel object fails with error #100 even when the token is completely healthy. A verification built on a read would fail for everyone. See Token error #100 if it does not succeed.

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

Step 5 — purge your cache and look at a real page

Open your site in a private window — logged out — and load a product page. Then check the Test Events tab. You are looking for one event with two sources: browser and server. See Verify your first event for what a healthy result looks like, and Processed vs Deduplicated for what the labels mean.

Next

• Add Google
• Add TikTok