A 1st-Party Attribution Suite for eCommerce
  • Introducing Fueled
  • How Fueled Works
    • Key Concepts
    • Use Cases
    • Is Fueled a CDP?
  • Apps
    • Shopify App
      • Shopify Event Tracking
        • Customizing Client-Side Shopify Events
        • Custom Pixel
          • Custom Pixel For Tracking ATC Events
          • Custom Pixel For Tracking Checkout Steps
        • Working with Fueled’s Shopify Data Layer
      • Google Analytics Connector
        • Configuring Google Analytics 4
        • Configuring GA4 Settings in Shopify
          • Shopify Order Source IDs
        • GA4 Shopify App Event Definitions
      • Google Ads Connector
      • Facebook Pixel/CAPI Connector
      • Segment Connector
      • Google Tag Manager Integration
      • Data Warehouse Connector
      • Domain Name Proxy
    • BigCommerce App
      • Google Analytics 4 Connector
        • Configuring Google Analytics 4 for BigCommerce
        • Configuring Fueled’s BigCommerce App
        • BigCommerce Event Tracking
          • Working with Fueled’s BigCommerce Data Layer
          • Customizing Client-Side BigCommerce Events
        • GA4 BigCommerce App Event Definitions
      • Google Ads Connector
      • Segment Connector
      • Data Warehouse Connector
  • Integrations
    • Sources
      • Shopify
      • BigCommerce
      • Headless eCommerce
        • Pack Digital
        • TakeShape
        • Next Commerce
      • Gorgias
        • Ticket Created
        • Ticket Updated
      • Loop Returns
      • Klaviyo
        • Email Opened
        • Email Bounced
        • Email Unsubscribed
        • Email Marked as Spam
        • Email Link Clicked
        • Newsletter Signup Started/Completed
      • KnoCommerce Surveys
      • ReCharge Payments
      • Yotpo Reviews
        • Identify
        • Product Reviewed/Review Updated
        • Site Reviewed/Review Updated
      • WordPress
    • Destinations
      • Google Analytics 4
      • Google Ads
      • Facebook Pixel/CAPI
      • Data Warehouses
      • Segment.com
        • Segment Event Specifications
          • Page
          • Identify
          • Account Created/Updated
          • Cart Viewed
          • Checkout Started
          • Order Completed
          • Product Added/Removed
          • Product List Viewed
          • Product Viewed
          • Products Searched
      • RudderStack
      • MixPanel and Amplitude
  • Resources
    • Recipes & Open Source
      • BigCommerce, dbt & BigQuery
      • Working With GA4 Data In BigQuery
        • Simple 'Page View to Purchase' Funnel Analysis
        • Querying Device Information for Shoppers with Purchases
        • Debugging User IDs in GA4 Events
      • Downgrading To Shopify's Free GA4 Connector
      • Demos
        • Configuration In Under 5 Minutes
    • News, Articles & Podcasts
      • Upgrading To A Paid Fueled Plan On Shopify
      • Feature Comparisons
  • More Info
    • About Us
    • Get Support
Powered by GitBook
On this page
  • Overview
  • Why Leverage Fueled’s Data Layer?
  • Enabling Fueled’s Data Layer
  • Data Layer Object Definitions
  • Leveraging Fueled’s Data Layer with Google Tag Manager
  • Getting Assistance with Fueled’s Data Layer
  1. Apps
  2. Shopify App
  3. Shopify Event Tracking

Working with Fueled’s Shopify Data Layer

PreviousCustom Pixel For Tracking Checkout StepsNextGoogle Analytics Connector

Last updated 1 year ago

Overview

Fueled provides a lightweight data layer and data layer listeners that can be leveraged with Google Tag Manager, or used to create your own event tracking scripts/events.

Why Leverage Fueled’s Data Layer?

If a merchant needs to set up multiple client-side attribution scripts to run on their Shopify store, leveraging our data layer can help ensure that the same event data is sent to all destinations. Our data layer defines a data model in one place for consistent tracking and metrics.

Enabling Fueled’s Data Layer

Fueled’s data layer is enabled whenever the Theme App Extension is enabled for our Google Analytics 4 Connector App.

The App Extension settings can be found in your theme, as see below:

Note: You do not have to check the “Track client events” box in the App Extension Settings to utilize our data layer. In fact, if you’d like to leverage our data layer in combination with our client-side event library to manage all of your own client-side events, you would disable this checkbox.

Data Layer Object Definitions

Visit:

Leveraging Fueled’s Data Layer with Google Tag Manager

⚠️ We are not fans of GTM here at Fueled… While Google Tag Manager remains a popular way for marketing teams to inject and manage attribution tags and other scripts on their website, GTM is highly problematic:

  • Google Tag Manager is stripped from websites by ad blockers up to 12% of the time in the United States.

  • It’s difficult to document and control attribution configuration with GTM.

  • It’s difficult to debug errors in attribution scripts that are managed via GTM.

That said, you can still leverage Google Tag Manager with our data layer to help ensure consistent tracking and client-side metrics.

Fueled’s data layer is instantiated in the DOM’s window.dataLayer object, as a variable called fueled.

Inside your Google Tag Manager instance, you can map the data layer to the variables you need for GTM events.

Go “Variables” and click “New” to to create new user-defined variables.

Then click “Data Layer Variable” as seen below.

An example of how you would access properties of Fueled’s data layer are described in the screenshot below.

fueled is the javascript variable to which we populate all of our event and data layer data. To access customer-related data (when a shopper is logged in), you’d select values such as:

  • fueled.customer.first_name

    • fueled.customer.email

Getting Assistance with Fueled’s Data Layer

For help working with our data layer, please consider .

GA4 Shopify App Event Definitions
joining our Community Slack Channel
A screenshot of the App Extension settings for the Fueled app.
Google Tag Manager UI for adding user-defined data layer variables.
Google Tag Manager UI for adding a custom data layer variable.
Google Tag Manager UI for naming a custom data layer variable