TABLE OF CONTENTS
Getting Started with Fueled’s GA4 Connector App
Configuring our Google Analytics 4 Connector for BigCommerce is quick and easy.
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:
Next, visit our BigCommerce Marketplace listing to install our app on your BigCommerce Store: https://www.bigcommerce.com/apps/google-analytics-4-attribution-suite/
Configuring the GA4 Connector App
Tracking Client-Side Events
Fueled’s GA4 Connector app leverages BigCommerce’s Scripts Manager and Scripts Manager API to install client-side javascript that tracks events that take place in the browser.
When you install our app on a Stencil-powered theme, we inject two javascript snippets in Scripts Manager:
Script Name | Description | Placement | Location | Category |
fueled-vars | This script loads the Fueled writekeys and API configurations | All pages (including checkout) | Head | Analytics |
fueled-script_tag | This script loads Fueled’s data layer and handles event tracking. | All pages (including checkout) | Footer | Analytics |
Please do not update either of these two scripts, unless you know exactly what you are doing. In particular, edits to fueled-vars could 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.
Respecting User Tracking Consent
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.
Enabling Server-Side Tracking
Enable/disable server-side tracking to track checkout and purchase events with Fueled. By default, our app tracks server-side events.
attribution property on purchase events. Orders placed by customers through your storefront will have “web” listed in this attribution property.Configuring the Purchase Value Sent to Google Analytics
Google recommends that purchase events use the “subtotal” value of an order as the value parameter. 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!
Entering Your Google Analytics 4 Credentials
You will need to enter your Measurement ID and API Key for GA4 to send Google attribution events. Please review our documentation on configuring a GA4 property here.
Pausing Attribution Events
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.
Getting Help
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.
You can get in touch with us at: support@fueled.io.
You might also considering joining our Community Slack Channel, where consultants, developers, and other merchants are available to lend a hand.
ON THIS PAGE
- Getting Started with Fueled’s GA4 Connector App
- Configuring the GA4 Connector App
- Tracking Client-Side Events
- Respecting User Tracking Consent
- Enabling Server-Side Tracking
- Configuring the Purchase Value Sent to Google Analytics
- Entering Your Google Analytics 4 Credentials
- Pausing Attribution Events
- Getting Help