Meta Pixel conversion events: check one test event before you trust the counts

What the Pixel needs from the site

The Pixel reports an action when the page calls fbq with a standard event name. Meta states that Purchase requires a value and that currency gives its currency, and that purchase calls can sit on a confirmation page or be bound to a button click. If either is missing or placed on the wrong step, the counts cannot be trusted whatever the dashboard shows.

The first check is therefore on the site, not in Events Manager: perform one test conversion with Meta's Pixel Helper extension open and read what fires.

• Count the firings for one test action.
• Read the event name, value and currency in Pixel Helper.

Deduplication and testing

Meta documents deduplication for one case only: the same event sent from both the browser Pixel and the Conversions API, matched by event ID and name within 48 hours. It does not remove two identical browser events. Test Events in Events Manager shows what Meta receives, but Meta says events sent with a test code are not dropped, so tests are not isolated from live data. Log the time of each test.

• Fix a double-firing Pixel at the tag, not in settings.
• Remove any test code from production.

Priced routes and boundaries

The bounded route is Verify ad conversion tags at £295, covering one Google Ads action and one Meta event on one site; the wider chain from campaign link to conversion starts from £1,495 as a project. Server-side Conversions API work is outside both. All are untested proposals with payment after sign-off, and none promises ad performance. Send the conversion step; no account IDs or logins.