Meta Purchase event with no value, or counted twice: parameters, deduplication and how to test

What a Purchase event must carry

Meta defines standard events and reports them with a call to fbq. For Purchase, Meta states that value is required and that currency gives its currency, so a Purchase without them cannot support value-based use. If you send contents, each object in the array needs an id and a quantity. Custom events use a different call, and their names must be 50 characters or fewer.

Placement matters too. Meta shows two patterns: a call on the confirmation page load, and a call bound to the button click on the checkout page. A page-load call fires again when the page is reloaded; a click call fires on each click.

• Check the event name, value and currency in Pixel Helper on a test order.
• Decide whether the event belongs to the page load or the click, and use only one.

When deduplication applies and when it does not

Meta documents deduplication for one situation: the same event sent through both the Pixel and the Conversions API. To deduplicate, the Pixel eventID must equal the server event_id and the event names must match, and the window is 48 hours. A second method using fbp or external_id exists but is described as working generally only when the browser event arrives first.

It does not help when the browser event itself is sent twice. Meta states deduplication does not remove duplicates within a single source, such as two identical browser events. A double-firing Pixel is a tag problem to fix at the source, not a deduplication setting.

• If you use only the Pixel, there is nothing to deduplicate across routes.
• If you use both, give every event a shared ID generated per event.

Test one event end to end

Use the Pixel Helper extension in your browser to see which events fire and with which parameters, then check Meta's Test Events tool under Events Manager, Data Sources, your Pixel. Meta says events sent with a test code are not dropped: they still reach Events Manager, so test events are not isolated from live data. Remove any test code from production payloads and note the time of every test.

Meta says events should be verifiable within about 20 minutes. If a click ID goes missing, Meta's support page points to destination pages that reject unexpected parameters or redirects that alter the URL; those are fixed on the site.

• One test conversion should show one Purchase with value and currency.
• An event appearing proves Meta received it, not that any ad attribution is correct.

What does not fit, and how the paid outcome is accepted

This guide does not cover server-side sending, audience building or campaign changes. It makes no claim about ad performance.

The fixed outcome Verify ad conversion tags covers one Google Ads conversion action and one Meta event on one site at £295, an untested proposal, with payment only after sign-off. For Meta, acceptance is one firing in Pixel Helper with the agreed event name, value and currency, listed in Test Events, with no second firing on reload. Send the conversion step; no account IDs or logins.