# Configuring Fueled’s BigCommerce App

## Getting Started with Fueled’s GA4 Connector App <a href="#block-69b9931706dc4d16b3ede600a1816d86" id="block-69b9931706dc4d16b3ede600a1816d86"></a>

Configuring our [Google Analytics 4 Connector for BigCommerce](https://www.bigcommerce.com/apps/google-analytics-4-attribution-suite/) 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:

[Configuring Google Analytics 4 for BigCommerce](/apps/bigcommerce-marketplace-app/google-analytics-4-connector/configuring-google-analytics-4-for-bigcommerce.md)

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 <a href="#block-fa97a04f39e843d68096304da1c65573" id="block-fa97a04f39e843d68096304da1c65573"></a>

### Tracking Client-Side Events <a href="#block-63da997451224774a39659d4feec2745" id="block-63da997451224774a39659d4feec2745"></a>

[Fueled’s GA4 Connector app](https://www.bigcommerce.com/apps/google-analytics-4-attribution-suite/) leverages BigCommerce’s [Scripts Manager](https://support.bigcommerce.com/s/article/Using-Script-Manager) and Scripts Manager API to install client-side javascript that tracks events that take place in the browser.

> 🔑 **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 <support@fueled.io> if you are on a Blueprint theme and would like to leverage our client-side tracking features.

When you install our app on a Stencil-powered theme, we inject two javascript snippets in Scripts Manager:

<table data-header-hidden data-full-width="true"><thead><tr><th></th><th width="255"></th><th width="154"></th><th width="107"></th><th></th></tr></thead><tbody><tr><td><strong>Script Name</strong></td><td><strong>Description</strong></td><td><strong>Placement</strong></td><td><strong>Location</strong></td><td><strong>Category</strong></td></tr><tr><td><mark style="color:red;"><code>fueled-vars</code></mark></td><td>This script loads the Fueled writekeys and API configurations</td><td>All pages (including checkout)</td><td>Head</td><td>Analytics</td></tr><tr><td><mark style="color:red;"><code>fueled-script_tag</code></mark></td><td>This script loads Fueled’s data layer and handles event tracking.</td><td>All pages (including checkout)</td><td>Footer</td><td>Analytics</td></tr></tbody></table>

***Please do not update either of these two scripts, unless you know exactly what you are doing. In particular, edits to&#x20;**<mark style="color:red;">**`fueled-vars`**</mark>* ***could break your client-side Fueled integration.***

Within Fueled’s GA4 Connector App settings, you can enable/disable client-side tracking:

<figure><img src="https://images.spr.so/cdn-cgi/imagedelivery/j42No7y-dcokJuNgXeA0ig/17e4d533-e9d2-479e-9936-3a5ced41e1f3/client-side_tracking_config/w=1920,quality=80" alt=""><figcaption></figcaption></figure>

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.

### Respecting User Tracking Consent <a href="#block-7f16c1a113994aad9ce490db9838afc3" id="block-7f16c1a113994aad9ce490db9838afc3"></a>

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.

<figure><img src="https://images.spr.so/cdn-cgi/imagedelivery/j42No7y-dcokJuNgXeA0ig/6e13a479-eac2-4134-b829-ef97e14219ff/Image_2022-10-17_at_6.14.34_PM/w=3840,quality=80" alt=""><figcaption></figcaption></figure>

### Enabling Server-Side Tracking <a href="#block-d91a5531b9ca4421b78d91db37cf8e05" id="block-d91a5531b9ca4421b78d91db37cf8e05"></a>

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 <mark style="color:red;">`attribution`</mark> property on purchase events. Orders placed by customers through your storefront will have “web” listed in this <mark style="color:red;">`attribution`</mark> property.

<figure><img src="https://images.spr.so/cdn-cgi/imagedelivery/j42No7y-dcokJuNgXeA0ig/edf1c353-6875-4fdd-89f7-fa6fceed73ab/Image_2022-10-17_at_6.16.55_PM/w=1920,quality=80" alt=""><figcaption></figcaption></figure>

### Configuring the Purchase Value Sent to Google Analytics <a href="#block-932d4ced19194be5a89e70388e351421" id="block-932d4ced19194be5a89e70388e351421"></a>

Google recommends that purchase events use the “subtotal” value of an order as the <mark style="color:red;">`value`</mark> 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!

<figure><img src="https://images.spr.so/cdn-cgi/imagedelivery/j42No7y-dcokJuNgXeA0ig/b1f10a7d-7cda-4daa-b1e6-75fcd91bb634/Image_2022-10-17_at_6.22.37_PM/w=3840,quality=80" alt=""><figcaption></figcaption></figure>

### Entering Your Google Analytics 4 Credentials <a href="#block-deea07059eac4ba28dab6f19f9f9d9fb" id="block-deea07059eac4ba28dab6f19f9f9d9fb"></a>

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](/apps/bigcommerce-marketplace-app/google-analytics-4-connector/ga4-bigcommerce-app-event-definitions.md).

<figure><img src="https://images.spr.so/cdn-cgi/imagedelivery/j42No7y-dcokJuNgXeA0ig/d4673346-59e4-4352-9794-509982e58885/Image_2022-10-17_at_6.18.12_PM/w=3840,quality=80" alt=""><figcaption></figcaption></figure>

### Pausing Attribution Events <a href="#block-cff695abc627464f9698b3eb6d9dd8a5" id="block-cff695abc627464f9698b3eb6d9dd8a5"></a>

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.

<figure><img src="https://images.spr.so/cdn-cgi/imagedelivery/j42No7y-dcokJuNgXeA0ig/fdddceed-0062-4d84-a720-b968b6254c9d/Image_2022-10-17_at_6.20.23_PM/w=1920,quality=80" alt=""><figcaption></figcaption></figure>

### Getting Help <a href="#block-c403b8dd435a4cc78fdb9253b0afaec8" id="block-c403b8dd435a4cc78fdb9253b0afaec8"></a>

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,](/more-info/get-support.md) where consultants, developers, and other merchants are available to lend a hand.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.fueled.io/apps/bigcommerce-marketplace-app/google-analytics-4-connector/configuring-fueleds-bigcommerce-app.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.