Shopify and Meta one click CAPI: check duplicate events

Before adding Meta’s one click Conversions API to a Shopify store, check which integration already sends your purchase events. A second connection is not automatically an improvement, and a setup prompt alone does not establish that your existing tracking is missing.

Tracking vendor Brett Fish renewed his warning about overlapping CAPI setups on 23 October. The practical issue is whether Meta can recognise repeated reports of the same purchase. It would be wrong to conclude that every combination of integrations necessarily double counts.

What Meta’s one click option actually does

Meta’s setup comparison, checked on 24 October, describes Meta enabled Conversions API as a free, web only option that requires a Meta Pixel. It sends the Pixel’s events and parameters through a server connection and automatically deduplicates those events against the Pixel.

That is useful context when evaluating the warning. Automatic handling of this browser and server pair does not, by itself, demonstrate that an additional tracking provider uses compatible identifiers for the same purchase.

Shopify may already send purchase events

According to Shopify’s data sharing documentation, Standard uses the Meta Pixel. Enhanced and Maximum also use Conversions API to send purchase events between Shopify and Meta servers.

Check Sales channels → Facebook & Instagram → Settings → Data sharing settings. Then list any separate tracking apps, tag manager connections or custom integrations. Keep the chosen data sharing level consistent with your store’s customer disclosures; this is not a recommendation to select the broadest setting simply to clear a prompt.

Check whether copies describe the same event

Meta’s deduplication guidance says matching event names and event IDs let it identify duplicate reports. It explicitly includes redundant server events with identical event_name and event_id. Shopify partner integrations can handle these parameters automatically.

The implication for a store using several providers is to check how those providers identify each purchase. Different identifiers for the same transaction warrant investigation. Seeing server events arrive establishes activity, not that every overlapping connection is correctly deduplicated.

Ask the person responsible for tracking to inspect event sources, deduplication status and diagnostics in Events Manager, and use Test Events to verify the setup. Record the expected purchase event and its identifier before changing anything. A connection label or setup banner is a starting point for that review, not its result.

A practical check before BFCM

1. Record the integrations currently sending purchase events and the dataset they use.
2. Confirm which connection is meant to provide each event. Ask your provider how it coordinates identifiers with other active connections.
3. Test the intended flow and examine received events and deduplication diagnostics.
4. If an unnecessary connection is identified, have its owner plan the change and retest afterwards. Avoid switching sources off at random and creating a tracking gap.

A sudden reporting jump is a reason to investigate, not proof of duplication on its own. Keep a dated record of tracking changes so your team can distinguish measurement changes from changes in sales.

The original practitioner warning

Fish’s 23 October post raises the issue again ahead of BFCM. His earlier 11 August post reports advertisers adding Meta’s option alongside an existing setup. These are a tracking vendor’s observations, not evidence that every Shopify account is affected.

Brett Fish’s CAPI warning, 23 October 2026

Read the October post and the 11 August post with an Events Manager screenshot. The older screenshot provides context rather than a guarantee of today’s interface.