Facebook conversion API for BigCommerce

In this guide

Route 1: the built-in channel Route 2: Tag Manager and a server container BigCommerce traps What a managed server adds Test Frequently asked questions

Key takeaways

BigCommerce has an official Meta channel that can send server events. A server container adds control and other platforms.
For the container route, use Script Manager to add the container and read order confirmation data.
Use one server route for Meta and a shared event ID.

BigCommerce is a hosted platform with an app ecosystem, and like Shopify it gives you a quick built-in way to send events to Meta, and a more flexible route through Tag Manager. Which to choose depends on how many platforms you use and how much control you want. BigCommerce's features and menus change, so check its documentation for the exact current steps. See also Meta Conversions API vs Pixel and how to set up the Conversions API.

Route 1: the built-in channel

Connect Meta through BigCommerce's Facebook channel (in Channel Manager). It adds the pixel and sends server events, and handles the event IDs for you. Check that the data sharing setting is on the level that includes the Conversions API. This is a good start for a store that only advertises on Meta.

Check your setup

Check your tracking in one pass

This is an example. Run the check on your own site to see where yours stands.

Route 2: Tag Manager and a server container

Add the container with Script Manager

In Storefront, Script Manager, add the Tag Manager snippet to all pages, in the header and the body part as your container requires.

Make a data layer

Push events from the storefront theme or an app: product view, add to cart, checkout steps.

Read the order confirmation

Script Manager can run a script on the order confirmation page. Use it to push the purchase event with the order ID, total, currency, items and, with consent, the customer's e-mail.

Send to your tagging subdomain

Set the server container URL in the Google tag.

Add the Meta tag in the server container

With the dataset ID, token and a shared event ID.

Turn off the other server route

If you used the Meta channel before, switch its server events off.

BigCommerce traps

SymptomThe checkout is on a different domain

Likely causeSome checkouts run on a separate address, which splits cookies and sessions.

FixCheck that the container is installed on the checkout and that cookies are first-party on the same domain, or use cross-domain settings.

SymptomPurchase fires twice

Likely causeThe channel and your container both send it.

FixUse one server route and a shared event ID.

SymptomCustomer data is missing at confirmation

Likely causeThe script does not have the customer fields.

FixRead them from the checkout or order objects the script manager exposes, and hash them.

SymptomConsent is ignored

Likely causeScript Manager loads scripts without a consent check.

FixUse the consent categories in Script Manager and Consent Mode in Tag Manager.

Data in, clean out

Raw events in. Clean events out.

Open Tracked collects each event on your own domain, removes the noise and sends what is left to Meta, BigCommerce, Google Ads.

What a managed server adds

With Open Tracked as the host, the container, subdomain and power-ups run for you. Cookie Keeper restores _fbp for returning visitors, the Data Store and Enricher add stored e-mail and phone to later events, and Visitor Location adds country and city. All are on the free plan. See every power-up.

Test

Place a test order.
Check the data layer on the confirmation page.
Open server Preview and the Meta tag.
Check Test Events for a deduplicated Purchase.
Compare Meta purchases with BigCommerce orders for a week.

0 of 6 done

I chose the channel route or the container route for MetaThe container is installed on every page, including the checkoutThe purchase event fires once with ID, value and currencyEvent IDs are sharedConsent controls scripts and tagsTest Events shows deduplicated purchases

Try it

Works with your stack

Grab a logo and throw it. These are the tools Open Tracked already talks to.

Grab one. Throw it.

Frequently asked questions

Does BigCommerce support the Meta Conversions API?

Yes, through its Meta channel. A server container is an alternative with more control.

How do I add Tag Manager to BigCommerce?

Through Script Manager in the storefront settings.

How do I track purchases on BigCommerce?

Push a purchase event with the order details on the order confirmation page.

How do I avoid double purchases?

Use one server route and a shared event ID.

Does Open Tracked work with BigCommerce?

Yes. Open Tracked hosts the server container that receives events from your store.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start free More in Integrations →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...