BigCommerce + Google Ads: an integration that reports the truth
BigCommerce ships with a native Google channel and a clean data model, which makes the baseline connection straightforward. The value iClick adds is beyond the baseline: Enhanced Conversions, server-side tracking, custom labels, and reconciling reported ROAS against the store's real revenue. This guide covers the full setup for a BigCommerce store.
A 47-point written audit of your Google, Meta or Shopping account, back in five business days.
Get your auditBook a callWhat this integration unlocks
- Automatic product feed sync to Merchant Center for Shopping and PMax
- Baseline purchase conversion tracking for ROAS reporting
- Dynamic remarketing audiences from catalogue browsing
- Enhanced Conversions for recovering privacy-limited conversions
- Server-side event pipeline for durable measurement
Setup steps
- 1
Connect the native Google channel
BigCommerce's built-in Google channel syncs your catalogue to Merchant Center. Approve the connection and let the initial sync complete, then confirm GTINs, pricing, and availability populate correctly.
Enable automatic feed updates so inventory and price changes propagate. Watch for SKU disapprovals in Merchant Center, since a silently disapproved product is a live sale being lost.
- 2
Route conversion tracking through Tag Manager
Install Google Tag Manager and fire the purchase conversion from BigCommerce's order-confirmation page with a proper data layer carrying order value and transaction ID.
The transaction ID is what enables deduplication once server-side and Enhanced Conversions are added, so capture it from the start.
- 3
Enable Enhanced Conversions
Map BigCommerce checkout fields, email and phone, into the data layer so Enhanced Conversions can hash and match them. This recovers conversions lost to iOS and cookie limits.
Verify the Recording state in the Enhanced Conversions diagnostics, and confirm the email field is present at the moment the purchase event fires.
- 4
Deploy server-side tracking
Stand up a server-side GTM container to capture the purchase server-side and forward a clean, deduplicated conversion to Google Ads. This protects the signal from ad-blockers and privacy browsers.
On BigCommerce Enterprise, deeper checkout access makes this cleaner, but it is achievable on standard plans through the data layer.
- 5
Configure custom labels
Add custom labels for margin tier, hero-SKU flag, seasonality, and discount state to the feed, so Shopping and Performance Max can bid your high-margin products differently from your loss leaders.
Common issues
Fix. Usually the email field is missing from the data layer at purchase, or hashing is misconfigured. Confirm the field is captured before the event and inspect the hashed value in the tag debugger.
Fix. PMax is likely counting branded search and view-through conversions. Apply brand exclusions, wait for redistribution, and reconcile against the store's revenue report.
Fix. Typically missing GTINs, image quality issues, or title length. Fix at the product level in BigCommerce so corrections persist through feed refreshes.
Fix. Use the transaction ID for deduplication so a customer refreshing the confirmation page does not register a second conversion.
Common questions
Want this checked on your own account?
A 47-point written audit of your Google, Meta, or Shopping account. Five business days, no sales call.
