Comment on page
GA4 Shopify App Event Definitions
📌 Bookmark this page.Understanding how attribution metrics are derived and how event properties are translated from one platform to another can be difficult. Our team is committed to taking the guesswork out of managing attribution. The definitions below are shared to provide transparency and clarity in setting up and maintaining your attribution model.
Note: If you are exclusively leveraging Fueled’s GA4 Connector App for Shopify, you don’t need to worry about Fueled’s naming convention, as events will show up in Google Analytics correctly, using Google’s event schema.
One of the challenges in attribution tracking is that every platform, from Shopify to Google Analytics to Facebook Ads to Segment, uses different naming conventions to describe a shopper’s behavioral events, and the properties of those events.
It’s Fueled’s job handle all of these translations on behalf of our merchants. However, if you are looking to customize any of your Fueled events, it’s helpful to understand and adopt our naming conventions to keep your data clean and consistent.
Fueled’s internal event naming convention follows the “Object-Action Framework.” What that means is that event names begin with the object upon which an action occurs, followed by a past-tense verb describing the action.
For example: when a user visits a product description page, we refer to this event as a
Product Viewedevent, not a
viewed_productevent. The majority of CDPs and attribution platforms follow this Object-Action Framework. (Google Analytics, however, does the opposite.)
Moreover, Fueled events are Title Cased, and use spaces between the Object and the Action. Google Analytics, on the other hand, uses snake_case naming.
camelCasingwhen labeling event properties. Google Analytics typically uses
When Fueled’s GA4 Connector App is installed, we provide an option for enabling a theme extension that installs a data layer and, optionally, injects client-side event tracking. You can leverage this data layer for your own purposes. Doing so is actually a great idea, as it helps ensure that you are using the data storefront variables across all of your client-side attribution scripts.
Our data layer exposes the following objects in your theme.
The Customer Object is only exposed when a shopper is logged into your store.
Product objects are exposed both on individual product pages, and as an array of products on Collection pages and so forth.
Exposed on the cart page (https://examplestore.com/cart).
Note: Fueled currently supports event properties marked with ✅. Properties marked with ❌ are not currently supported.
This event fires when an item is added to a cart for purchase.
add_to_cartevent maps to Fueled’s generalized
Product Addedevent specification. The
add_to_cartevent is populated with the following properties.
Note: The “add to cart” experiences on a Shopify theme are often heavily customized. Fueled’s out-of-the-box
add_to_cartattribution events only cover standard use cases. Customized tracking scripts may be needed to capture all
add_to_cartevents on your website.