Why doesn't my BigCommerce Purchase event fire?

Check Script Manager scope first — scripts scoped to store pages don't run on order confirmation. Then check consent managers and ad blockers, which kill the browser Pixel regardless of scope.

Does BigCommerce support Conversions API natively?

The native Meta app sends some server events tied to the browser session. Independent server-side delivery with retries and dedup requires an external sender.

Can Caply deduplicate against my existing Pixel?

Yes — Caply shares an event_id with the browser hit, so Meta counts one Purchase even when both sides deliver.

BigCommerce

Check your BigCommerce store's Meta tracking

Paste your storefront URL to see the Pixel and helpers in your HTML. BigCommerce's Script Manager can inject scripts on the order confirmation page — but only when the script is scoped to 'Order confirmation', and headless or checkout-customized stores lose that guarantee.

Deep scan (SPA / JS-rendered)

Real browser. Pro and Team from a workspace. Static scan stays free, no login.

Static scan

Script Manager scope is the silent killer

A Pixel added with 'Store pages' scope never sees checkout. Purchase requires the 'All pages' or 'Order confirmation' scope — a one-dropdown mistake that costs every conversion.

Native Meta integration is browser-tied

The BigCommerce Meta app fires standard events from the shopper's browser. Blocked browser, lost sale — there is no independent server retry.

Headless BigCommerce needs explicit wiring

On Stencil-less storefronts nothing is injected for you. Caply's snippet plus server-side Purchase from order data covers both rendered and headless setups.

BigCommerce tracking questions

Why doesn't my BigCommerce Purchase event fire?: Check Script Manager scope first — scripts scoped to store pages don't run on order confirmation. Then check consent managers and ad blockers, which kill the browser Pixel regardless of scope.
Does BigCommerce support Conversions API natively?: The native Meta app sends some server events tied to the browser session. Independent server-side delivery with retries and dedup requires an external sender.
Can Caply deduplicate against my existing Pixel?: Yes — Caply shares an event_id with the browser hit, so Meta counts one Purchase even when both sides deliver.

After the scan

Send BigCommerce sales from the server. Count each one once.

Caply sends Purchase and Lead from managed servers with hashed customer data, deduplicated against your Pixel by event_id. Pro $29 or Team $99, 14-day trial (card required).

Start 14-day trial How Caply works

Other platforms: Shopify · WooCommerce · Wix · Squarespace · Webflow · Framer · Full scanner