BigCommerce conversion tracking setup

The purchase that never fired

Picture this. A BigCommerce store selling kitchen knives pastes its Meta pixel into Script Manager, picks Storefront, and hits save. Product views show up in Events Manager within minutes. Add to cart too. Everyone relaxes.

Two weeks later the ad account says zero purchases. The store did 140 orders.

Nothing was broken. The Storefront scope does exactly what BigCommerce says it does: it skips checkout and the order confirmation page. The one page that matters never loaded the code.

Your tracking was fine. It was just installed everywhere except the till.

The real cost of a cheap tool

Cheap tracking that is handled badly costs far more, because the bill arrives in what your ads learn.

• Bots forwarded as buyers. A forwarder sends what reaches it. Junk conversions teach the platform to find more junk.
• The sale that never gets sent. A booked call, a phone order or a won deal happens outside the store or the page. Most tools never see it.
• The limit you hit on your busiest day. Hosts and apps cap requests, events or orders, and sending can pause or stop over the limit.
• The build and the upkeep. Containers, plugins and automations need someone to build them and fix them when a platform changes.

The tracking is 0.17 percent of your spend. If one in five of the conversions your ads learn from is a bot or a fake lead, a fifth of the learning signal points at the wrong people, across the other 99.83 percent of the budget.

Cheap tracking is the cheapest line on the bill and the most expensive one to get wrong.

Your options for BigCommerce conversion tracking

There are three honest routes. Pick by who will maintain it.

When not to use DataCops

• You need custom tag logic or non-ad destinations. DataCops sends to ad platforms and is not a Google Tag Manager container. A hosted server container gives full control, if someone owns it.
• You want a reporting dashboard. DataCops fixes what goes into your ads. It does not replace the reports you already read.

Ads Warmup: tell the ads who pays

BigCommerce conversion tracking forwards what your site or store produces. A new ad account, pixel or campaign has nothing yet, so it pays to learn from scratch. That is a job a pipe cannot do, because the customers you already have never visit on command.

Ads Warmup, DataCops' flagship feature, sends them to your ad platforms before a campaign spends:

1. Upload a customer list. A CSV of past buyers, old leads or booked calls. DataCops reads your columns; only email is required.
2. See a match score for every person. An estimate from 0 to 10 from email, phone, name, location, click ID and customer ID, before anything is sent.
3. Pick the event. Purchase, Lead, Complete registration, Add to cart or Schedule.
4. Send server-side. Up to 20,000 people per upload to Meta, Google Ads and TikTok, with a sent, skipped or failed result per person. Google Ads credits only people who clicked a Google ad.

Each row is dated when you press send, not with the old sale date, so it gives a new campaign real customers to learn from on day one. Preview is free; sending needs a paid plan.

What else a pipe never does

• Capture at the edge. With DNS on Cloudflare, the free, optional DataCops Cloudflare Worker reads click IDs and UTMs off the first request, before the page or any script runs. It captures; it does not block.
• Keep the click on the server. gclid, wbraid, gbraid, fbclid, ttclid and li_fat_id are stored for up to 90 days, so a deal that closes weeks later still finds its click. A signed server-set cookie lasts up to 400 days where enabled.
• Check the lead's email. Fixed rules, not guesses: disposable providers, domains with no mail server and an email risk score. With LeadCops (Business and up), a lead that fails is held and never billed.
• Install on Shopify. The DataCops Shopify app adds a web pixel and a theme app embed, so every paid order reaches your ads, express checkouts included. See Shopify Conversions API.
• Hand evidence to Google. On the Organization plan, the fraud refund report exports bot-flagged Google Ads clicks in the format Google's Click Quality form asks for. You attach it; Google decides.

Where do BigCommerce scripts actually run?

They run wherever the scope in Script Manager says, and nowhere else. BigCommerce's own docs list four.

Two catches on checkout. Scripts there need Optimized One-Page Checkout, which is the default on new Stencil stores. And BigCommerce requires at least one SRI hash on checkout scripts to meet PCI DSS 4.0 requirement 6.4.3. If a vendor snippet refuses to load on checkout, that is the first thing to check.

How to set up BigCommerce conversion tracking, step by step

This is the plain route with no apps. Do it in this order.

1. Open Script Manager. In the control panel, go to Storefront, then Script Manager, then Create a Script.
2. Add the base code with All Pages. Your Meta pixel base code, Google tag or GTM container. Placement: Header.
3. Add the purchase event as its own script with the Order Confirmation scope. Keep it separate so you can switch it off without touching the base code.
4. Send the order ID, value and currency. Value without the order ID is half a conversion. The ID is what makes deduplication and refunds traceable.
5. Set the event ID to the order ID. For Meta that is eventID on the pixel call. For Google Ads it is the transaction_id. Same value on the server later.
6. Pick the right consent category for each script in Script Manager, so ad tags wait for consent where the law asks for it.
7. Add the server side. Send the same purchase from the server to Meta's Conversions API and Google Ads, with the same ID.
8. Place a real test order and check both platforms before you trust a single number. More on that below.

The order ID is the cheapest line of tracking code you will ever write. It fixes half the bugs.

Why are my BigCommerce purchases counted twice?

Because the pixel and the server both sent the order and nothing told the platform they were one sale.

Meta matches a browser event and a server event when the event name and event ID are the same. If your pixel sends Purchase with ID 10482 and your server sends Purchase with a random ID, Meta sees two sales. Your ROAS looks lovely. Your bank account disagrees.

Headless BigCommerce stores hit this most, because the storefront and the backend are often built by different people who never agreed on the ID.

Once it works: what are your ads learning from?

Here is the part most setup guides skip. A clean purchase event is not the only thing your ads read. They also learn from add to cart, begin checkout and every lead form on the store, and not all of that comes from people.

Bots browse, add to cart and sign up for discount codes. If those events reach Meta, the algorithm goes and finds more traffic like them. Your cost per add to cart looks great. Your cost per real order drifts up and nobody can say why.

DataCops is the tracking solution for ad-funded businesses: it keeps bots out of what your ads learn from and sends the sale that happens after the form to Meta, Google Ads, TikTok, LinkedIn, Microsoft Ads, Reddit, Pinterest and X.

Pixel and server events are deduplicated by event ID and counted once. Each platform connects in one click. Every row gets a delivery log entry: sent, held, skipped or failed, with the reason. The consent manager is first-party, IAB TCF v2.2, served from your own domain. If the store runs lead forms, LeadCops adds verification in two lines of code.

A tracking setup is not done when events arrive. It is done when only the right ones do.

How do I check BigCommerce tracking works?

Place a real order, then check each platform. Do not trust a green tick in a plugin.

1. Meta: Events Manager, Test Events. You want one Purchase, marked as received from browser and server, with the order ID.
2. Google Ads: Goals, Conversions, then the status of your purchase action. Allow a few hours for it to show as recording.
3. Compare with orders: after a week, put platform purchases next to BigCommerce orders. Far fewer means missing events. More means dedup is broken.
4. Refund your test order so it does not sit in your reports.

FAQ

Can I warm up a new campaign with my existing customers?

Yes, with DataCops Ads Warmup. Upload a CSV of customers (only email is required, up to 20,000 rows), see a 0 to 10 match score for each person, and send them to Meta, Google Ads and TikTok, dated when you send. Google Ads credits only people who clicked a Google ad.

Why is my Meta pixel not tracking BigCommerce purchases?

Most often the script was added with the Storefront scope, which BigCommerce excludes from checkout and order confirmation. Move the purchase code to the Order Confirmation scope, place a test order, and check Test Events in Events Manager.

Which Script Manager scope should my purchase event use?

Order Confirmation. It runs only on the thank-you page, so the purchase fires once per order and never on a product page by mistake.

Do I need server-side tracking on BigCommerce?

If you spend real money on ads, yes. Browser events get lost to blockers and closed tabs. A server event with the same event ID fills the gap without double counting.

Why does Meta show more purchases than BigCommerce?

Usually the pixel and the server both send the purchase with different event IDs, or no event ID at all. Meta cannot tell they are the same order and counts both. Use the order ID as the event ID on both sides.

Can I track BigCommerce with Google Tag Manager?

Yes. Add the GTM container through Script Manager with the All Pages scope and build tags per platform. It works, but you own every tag, trigger and fix after that.

Why do my checkout scripts need an SRI hash?

BigCommerce requires at least one SRI hash on checkout page scripts to meet PCI DSS 4.0 requirement 6.4.3. It lets the browser check the script has not been changed.

Does DataCops have a BigCommerce app?

No dedicated app today. DataCops handles the part after the tag: counting each purchase once, keeping flagged visits out of what Meta, Google Ads, TikTok, LinkedIn, Microsoft Ads, Reddit, Pinterest and X learn from, and logging every send. Talk to us about connecting your store.

Sources

• Meta for Developers: Conversions API
• Meta for Developers: handling duplicate pixel and Conversions API events
• Google Ads Help: how Google Ads tracks website conversions
• Google Ads Help: guidelines for importing offline conversions
• Google Ads Help: updates to your enhanced conversions settings
• Stape: pricing