Meta Pixel Page View Event Tracking for BigCommerce

Quick answer: Select Meta Pixel and the Page View event in the free container builder wizard, enter your tracking ID, then import the generated file into Google Tag Manager - the trigger is wired up automatically, no manual setup required.

Configure the Page View event so Meta Pixel fires correctly on your BigCommerce store, then generate an importable Google Tag Manager container - no manual tag, trigger, or variable setup required.

Generate my Meta Pixel Page View container →

How it works

Open the container builder with Meta Pixel and the Page View event already selected.
Enter your tracking ID/pixel credentials for this platform.
Generate and download the GTM container JSON file.
In Google Tag Manager: Admin > Import Container > choose the file > Merge into a new workspace, then verify in Preview mode before publishing.

Track Page View with other platforms

How this event is built in your container

Page View uses Google Tag Manager's native Page View trigger, which fires on every page load automatically. No data layer changes are needed on your site for this one.

The Meta Pixel tag itself is added automatically and wired to this trigger - you won't need to create or configure it by hand in GTM.

Troubleshooting

Page View doesn't fire at all in GTM Preview mode.
Confirm your site is actually pushing dataLayer.push({event: 'page_view'}) - open the browser console and check the dataLayer array at the moment the action happens. If it's not there, the container has nothing to listen for.

The event fires, but values show up blank or undefined.
Check that the pushed object's key names match exactly (case-sensitive) - a mismatched key like "Value" instead of "value" will show as undefined in GTM's variable preview.

Page View fires twice for the same action.
You likely have both this container's tag and a manually-added Meta Pixel snippet both listening for the same action. Remove the manual one, or disable it, before publishing.

Frequently asked questions

What triggers the Page View event?

It fires automatically at the matching point in the BigCommerce visitor journey - the container builder wires up the correct trigger for you based on the standard dataLayer event for Page View, so there's nothing to configure manually beyond making sure your site actually pushes that event.

Why should I track Page View with Meta Pixel specifically?

It's a core revenue signal - Meta Pixel uses Page View data to measure return on ad spend, build retargeting audiences, and optimize bidding toward customers likely to complete this action. Accurate first-party data here also matters more as browsers restrict third-party cookies.

Is this free to set up?

Yes - the free tier covers 1 tracking platform at a time. If you need this event across several platforms in one container, unlocking full access covers all of them together.

Will this conflict with Meta Pixel code I already added manually?

It can, if the same event fires twice from two separate sources. Remove any manually-added Meta Pixel tag for this event before importing the generated container, or use GTM's Preview mode to confirm it only fires once.

How long does setup take?

A few minutes - select Meta Pixel and the Page View event in the wizard, enter your tracking ID, download the container, and import it into GTM.

Should I pair this with server-side tracking for Page View?

For a revenue event like Page View, it's worth considering. This container handles the browser-side Meta Pixel tag; a GTM server-side container or Meta Pixel Conversions API alongside it can recover conversions lost to ad blockers and iOS/Safari tracking restrictions, improving match quality without duplicating this setup.

← See all Meta Pixel events