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
  • Step 1: Configure Client-Side Event Tracking
  • Optional: Adjust You "Add To Cart" Tracking Settings
  • Step 2: Configure Server-Side Event Tracking
  • Step 3: Configure Fueled's Custom Pixel
  • Step 4: (Optional) Configure Fueled's Domain Proxy
  • Next Steps:
  1. Apps
  2. Shopify App

Shopify Event Tracking

PreviousShopify AppNextCustomizing Client-Side Shopify Events

Last updated 4 months ago

To get started with Fueled, you will first need to configure how the app tracks client-side and server-side events. These configuration settings apply to all of the destinations where Fueled sends data, such as Google Analytics and Facebook Conversion API.

Step 1: Configure Client-Side Event Tracking

The first step in configuring Fueled is to enable our "App Extension" in your Shopify theme.

Click the link in the "Configure Client-Side Tracking section. This will take you to your active Shopify theme, where you can enable our App Extension Widget. Remember to hit "Save."

Optional: Adjust You "Add To Cart" Tracking Settings

We will cover this option in more detail in: Custom Pixel For Tracking ATC Events

However, it's good to know that you can customize how "Add To Cart" (ATC) events are tracked in your theme. By default, Fueled listens for standard ATC event buttons in your theme code. However, for highly customized sites, it's sometimes helpful to disable our standard ATC tracking and instead leverage our Shopify Custom Pixel implementation for these events.

Step 2: Configure Server-Side Event Tracking

Next, confirm your server-side event tracking configuration.

Out-of-the-box, Fueled will track checkout and purchase-related events server-side. We inject special code in your Shopify theme (when you have client-side tracking enabled) to send attribution events from the browser to our server-side event integration.

With server-side tracking, we can ensure near-perfect, 1-to-1 tracking of purchase events between Shopify and Google Analytics. With server-side tracking, we also allow merchants to use point-of-sale and recurring billing purchases for ad targeting in Facebook.

There are pros and cons to client-side vs. server-side tracking of purchase events into GA4. With server-side tracking, you get better parity between GA4 reports and Shopify order counts/totals. With client-side tracking, you do get a bit more metadata about purchase events, such as information about browser devices and geolocation data.

Step 3: Configure Fueled's Custom Pixel

Fueled leverages a Custom Pixel for tracking Checkout-related steps and purchases. If you installed our app before February 4th, 2025, you will likely need to update any custom pixel code that you have configured with us. Otherwise, you will simply need to install our Custom Pixel v2 following these instructions.

This pixel code can be found here:

This code can be added as a custom pixel here:

https://admin.shopify.com/store/[your-store-name]/settings/customer_events

Step 4: (Optional) Configure Fueled's Domain Proxy

At the bottom of our "Tracking Setup" tab, you will see a reference to our "Domain Proxy" feature:

This feature is only available on our "Fueled Advanced" and "Fueled Plus" plans. With domain proxying, we run all of Fueled's scripts, as well as our Google Analytics endpoint over a domain proxy, which helps with cookie expires and ensures more complete client-side event tracking.

If you are interested in learning more about our advanced features, please visit:

Next Steps:

We do offer customizations to track purchase event client-side. Please contact for more information on this.

support@fueled.io
Customizing Client-Side Shopify Events
Custom Pixel For Tracking ATC Events
Working with Fueled’s Shopify Data Layer
client-scripts/shopify/custom_pixel_v2.js at main · fueled-io/client-scriptsGitHub
Pricing | Fueled.io
Logo
Logo
Fueled's "Tracking Setup" configuration screen.
At the top o f our "Tracking Setup" screen, you will find a link to enable Fueled's App Extension in your theme.
Save Fueled's App Extension settings in your active theme.
By default, Fueled tracks checkout and purchase-related events server-side.
Instructions for installing Fueled's Custom Pixel v2.
Callout for our Domain Proxy feature