Customizing Client-Side BigCommerce Events

When to Customize Client-Side Tracking for Fueled’s GA4 Connector App

By default, Fueled’s GA4 Connector App for BigCommerce tracks ten different types of customer events. An out-of-the-box installation of our app on a standard BigCommerce theme, one that uses BigCommerce’s core theme components and Script Manager, should cover the vast majority of your attribution use cases.

That said, if any of the following are true for your storefront, it might make sense to extend your attribution tracking with Fueled to cover your specific use cases:

  • You are leveraging a third-party shopping cart app, or you have “upsells” and “product recommendation” widgets on your cart and checkout pages.

  • You have highly-customized product collections pages that allow shoppers to interact with product variants without first going to the product description pages.

  • You offer product bundles or other custom “add to cart” experiences on your product pages.

You might also consider adding additional client-side event tracking, following Google Analytics 4’s event specification, describe here:

Turning Off Fueled’s Default Client-Side Events

Generally speaking, you are likely to add additional custom events to your client-side attribution setup, rather than turning off Fueled’s events. That said, if you want to fully customize your client-side tracking with Fueled, you can turn off our events, and simply use our data layer and client-side library:

Respecting Customer’s Privacy Preferences

Fueled’s GA4 Connector App for BigCommerce includes a setting for respecting shopper’s privacy preferences. This setting applies to all of the client-side events that we track.

If you’re setting up your own custom events with Fueled’s client-side library, you will need to follow these best practices on your own, leveraging BigCommerce’s privacy settings, including BigCommerce’s privacy cookie and Scripts Manager privacy features.

Last updated