Comment on page
Configuring Fueled’s BigCommerce App
First, please make sure that you’ve created a Google Analytics 4 Property, and that you have your Measurement ID and your API key ready to go. You can learn more about GA4 configuration at:
🔑 Note: Fueled’s client-side tracking only works out of the box for Stencil-powered themes. For legacy sites running on BigCommerce’s Blueprint theme engine, additional steps are required to configure client-side tracking. Please contact [email protected] if you are on a Blueprint theme and would like to leverage our client-side tracking features.
Please do not update either of these two scripts, unless you know exactly what you are doing. In particular, edits to
fueled-varscould break your client-side Fueled integration.
Within Fueled’s GA4 Connector App settings, you can enable/disable client-side tracking:
When client-side tracking is disabled, our application’s scripts still fire, such that you can access our data layer. But our application will not send these events to Google Analytics.
📢 Client-side and server-side tracking configuration is managed separately in our app. Some merchants choose to leverage our client-side tracking features, and not our server-side tracking features, or vice versa. Unless you’re building custom functionality on top of our libraries and APIs, we recommend that merchants enable both client-side and server-side tracking through our app.
By default, our GA4 Connector App respects the customer privacy/tracking consent features provided by BigCommerce’s Scripts Manager. We recommend that you leave these settings activated, to respect your customers’ consent when it comes to client-side event tracking.
Enable/disable server-side tracking to track checkout and purchase events with Fueled. By default, our app tracks server-side events.
🔑 With server-side event tracking enabled, Fueled tracks all purchase events, including purchases made through your BigCommerce Admin UI, point-of-sale, third-party checkout apps, and subscription management apps like ReCharge Payments. We send the BigCommerce order source to Google Analytics 4 via the
attributionproperty on purchase events. Orders placed by customers through your storefront will have “web” listed in this
Google recommends that purchase events use the “subtotal” value of an order as the
valueparameter. However, some merchants have historically used, or would prefer to use, the “total order value” (which includes taxes and shipping). We leave this choice up to you!
For the most part, once a merchant has configured our app, they will never need to adjust their settings or temporarily pause events. That said, if you’re setting up a new development store or are staging the Fueled app for a new store, you can use the settings below to turn off event tracking, while keeping the Fueled app installed and configured for your storefront.
While Fueled has provided this app to Shopify merchants for free, we do our best to support the wonderful merchants who choose to leverage our software.