Google Analytics 4 Add to Wishlist Event Tracking for BigCommerce
Quick answer: Select Google Analytics 4 and the Add to Wishlist 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 Add to Wishlist event so Google Analytics 4 fires correctly on your BigCommerce store, then generate an importable Google Tag Manager container - no manual tag, trigger, or variable setup required.
Generate my Google Analytics 4 Add to Wishlist container →
How it works
- Open the container builder with Google Analytics 4 and the Add to Wishlist 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 Add to Wishlist with other platforms
- Track Add to Wishlist with Google Ads
- Track Add to Wishlist with Meta Pixel
- Track Add to Wishlist with TikTok Pixel
- Track Add to Wishlist with Pinterest Tag
- Track Add to Wishlist with LinkedIn Insight Tag
- Track Add to Wishlist with Microsoft Advertising (UET)
- Track Add to Wishlist with X (Twitter) Pixel
How this event is built in your container
Add to Wishlist uses a Custom Event trigger that fires when your site pushes dataLayer.push({ event: 'add_to_wishlist' }) - the trigger is pre-configured to match this exact event name, so nothing needs adjusting after import.
Requirement: Your site needs to actually push that dataLayer event for the trigger to fire - the container listens for it, it doesn't generate it. Most WooCommerce sites get this from a data layer / enhanced ecommerce tracking plugin; check that dataLayer.push({event: 'add_to_wishlist', ...}) fires at the right moment using GTM's Preview mode before publishing.
This event also uses shared ecommerce Data Layer Variables so the same values work across every ecommerce event and tracking platform:
ecommerce.currency- transaction currency codeecommerce.value- monetary value of the eventecommerce.items- array of product objects, following GA4's standard ecommerce item schema
The Google Analytics 4 tag itself is added automatically and wired to this trigger - you won't need to create or configure it by hand in GTM.
Troubleshooting
Add to Wishlist doesn't fire at all in GTM Preview mode.
Confirm your site is actually pushing dataLayer.push({event: 'add_to_wishlist'}) - 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.
Add to Wishlist fires twice for the same action.
You likely have both this container's tag and a manually-added Google Analytics 4 snippet both listening for the same action. Remove the manual one, or disable it, before publishing.
Frequently asked questions
What triggers the Add to Wishlist 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 Add to Wishlist, so there's nothing to configure manually beyond making sure your site actually pushes that event.
Why should I track Add to Wishlist with Google Analytics 4 specifically?
It's a core revenue signal - Google Analytics 4 uses Add to Wishlist 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 Google Analytics 4 code I already added manually?
It can, if the same event fires twice from two separate sources. Remove any manually-added Google Analytics 4 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 Google Analytics 4 and the Add to Wishlist 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 Add to Wishlist?
For a revenue event like Add to Wishlist, it's worth considering. This container handles the browser-side Google Analytics 4 tag; a GTM server-side container or Google Analytics 4 Conversions API alongside it can recover conversions lost to ad blockers and iOS/Safari tracking restrictions, improving match quality without duplicating this setup.