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
  • Getting Started with Fueled
  • Example
  • Collecting Event Data
  • Cleaning and Transforming Event Data
  • Associating Events with the Correct Customers
  • 1st-Party Data Integrations Done Right, and Done for You

How Fueled Works

PreviousIntroducing FueledNextKey Concepts

Last updated 1 year ago

Getting Started with Fueled

While not technically required, most eCommerce merchants who leverage Fueled get started by connecting our platform with their eCommerce store — either of .

Our Shopify and BigCommerce integrations sync customer records into Fueled and push these records to various .

More interestingly, our Shopify and BigCommerce integrations collect all of your interactions with your customers (think: website clicks, purchases, refunds, sign-ups, etc.) and push these to all of your Destinations as well.

Example

Collecting Event Data

Cleaning and Transforming Event Data

Once Fueled receives event data from a Source, this data is cleaned and transformed, so that it can be sent to each integrated Destination, in the format that that Destination requires. A purchase event, for example, is transformed into different data formats for Destinations such as Google Analytics, Facebook Conversion API, or Klaviyo.

All of these data structures (or "schemas") and transformations can be tricky. One of the most important benefits of Fueled is that we handle all of this logic and translation steps for you.

Associating Events with the Correct Customers

Associating events with specific customers, also known as "Identity Resolution", can be complex. Customers generally visit your website anonymously, until they make a purchase. This conversion of a customer from an anonymous site visitor to an identified purchaser might take days or weeks of interaction with your website.

Fueled stitches all of these events together, retroactively associating anonymous interactions with an identified user once that user provides an email address, phone number, or other identifying/identifiable piece of data.

1st-Party Data Integrations Done Right, and Done for You

Fueled is not unique among products in the CDP category in providing the functionality described above. But it is unique in that it handles all of these integrations, data transformations, and setup for you. Fueled doesn't require weeks of planning and building out of data tracking plans manually. Fueled doesn't require that an engineering team implement each integration on your behalf.

With Fueled, CDP functionality and customer data strategies can simply be turned on or unlocked for your business — instantly.

You can install Fueled's or our to get started.

Fueled collects customer event data from different through both client-side and server-side integrations. When customers click through an eCommerce website, for example, searching for products, adding products to their cart, checking out, and so forth, client-side javascript fires on the website to collect these events and send them to Fueled. Similarly, when purchases are made, or customer service emails are sent back and forth between a customer and a merchant, these server-side events fire and are sent to Fueled.

Shopify App Store App
BigCommerce Marketplace App
Sources
Shopify
BigCommerce
Destinations
Events
Diagram of how Fueled collects, cleans, transforms, and pipes customer events from "Source" applications to "Destination" applications.
Fueled captures Shopify’s `Product Viewed` event and then translates it to match Google Analytic’s `item_viewed` format and Facebook’s `View content` format.