REFERENCE · GLOSSARY
Shopify tracking glossary.
Plain-English definitions of the terms that come up in Shopify tracking, attribution, and analytics. Meta CAPI, pixel match rate, attribution_source, is_first_order, server-side tracking, the lot. Each entry is short, factual, and links to the related concepts.
- attribution_source
- A custom field that captures which marketing channel drove a customer to make a purchase. On Shopify, attribution_source typically combines utm_source from the landing URL, the source_name field from Shopify's order, and any referring_site data. Shopify does not capture attribution_source by default; merchants add it via Customer Events, hidden cart input fields, or a third-party server-side tracking tool.
- Automatic Advanced Matching
- A Meta Pixel feature that automatically hashes and sends customer parameters (email, phone, name, address) along with each event. With Advanced Matching enabled, Meta can match events to users in its graph using the customer-level identifiers instead of just browser cookies, which boosts pixel match rate by 10 to 25 percentage points. On Shopify, Automatic Advanced Matching is enabled by default via the Meta channel app.
- cart_abandoned event
- An event that fires when a Shopify visitor enters checkout without completing a purchase. Klaviyo's abandoned-cart flow is triggered by this event. The event must carry the customer's email to be useful, plus typically the cart total, time in cart, and abandonment stage. Shopify fires the underlying signal natively (sometimes called Started Checkout in Klaviyo); failures usually trace to the Klaviyo onsite snippet not being installed, the customer not having entered an email, or a broken Shopify-Klaviyo integration.
- Google Tag Manager (server-side)
- A version of Google Tag Manager that runs in a server container hosted on Google Cloud rather than in the visitor's browser. GTM server-side moves tag execution off the browser, which bypasses iOS tracking restrictions and ad blockers and gives the merchant control over what data third parties see. Setup costs $40 to $100 per month in cloud charges plus engineering time. Recommended for Shopify stores at $5M+ ARR with paid spend above $50K/month.
- iOS 14.5 (App Tracking Transparency)
- Apple's April 2021 update introducing the App Tracking Transparency framework, which requires apps to ask users for explicit permission before tracking them across apps and websites. The Meta Pixel and other browser-side trackers lose access to the fbp and fbc identifier cookies when users opt out, causing a 20 to 35 percentage-point drop in pixel match rate on iOS visitors. Conversions API is the standard mitigation.
- is_first_order
- An order-level boolean field that indicates whether a given Shopify order is the customer's first ever purchase. is_first_order is required for distinguishing acquisition revenue from retention revenue, computing accurate cohort LTV, and branching post-purchase email flows on customer status. Shopify exposes the data via customer.orders_count = 1 at the time of order; deriving the historical boolean requires a SQL window function over the orders table.
- Klaviyo
- An email and SMS marketing platform widely used by Shopify direct-to-consumer brands. Klaviyo's value depends on the quality of event and property data it receives from Shopify. Common Shopify-Klaviyo integration gaps include missing flow trigger events, profile properties not syncing (Total Orders, First Order Date), and the onsite tracking snippet not being installed for pre-checkout abandonment signals.
- Meta Conversions API
- A server-to-server API from Meta (formerly Facebook) that lets advertisers send conversion events directly to Meta without relying on browser-side Pixel calls. CAPI bypasses iOS 14.5 cookie restrictions and ad-blocker suppression, which can recover 15 to 30 percent of attribution that the Pixel alone misses. On Shopify, CAPI is installed automatically via the official Meta channel app.
- Pixel match rate
- The percentage of conversion events a Pixel sends to an ad platform (typically Meta) with enough customer-level data for the platform to match the event back to a known user in its graph. Meta's recommended match rate for Purchase events is 85% or higher. Below 85%, Meta flags the event quality as low and reduces optimization confidence. Most Shopify stores sit between 50% and 70% before fixing customer-parameter coverage.
- Server-side tracking
- Sending tracking events from a server rather than a visitor's browser. Server-side tracking bypasses browser restrictions like iOS 14.5 cookie limits, ad-blocker suppression, and consent-mode-driven blocking. Common server-side tracking implementations on Shopify include Meta Conversions API, Google's enhanced conversions, and managed services like Elevar or Stape that run a Google Tag Manager server container.
- Shopify Customer Events
- Shopify's sandboxed JavaScript runtime for custom storefront tracking, formerly called Web Pixels. Customer Events runs on every page including checkout, on both Plus and non-Plus stores. It is Shopify's officially supported way to install custom tracking pixels and capture analytics data without modifying theme.liquid. Common uses: capturing utm parameters, firing third-party pixels (TikTok, Pinterest), and sending custom events to Klaviyo's onsite API.
- Shopify DTC tracking stack
- The canonical set of tracking and analytics tools installed on a typical Shopify direct-to-consumer brand. The base stack is Shopify (storefront and orders) + Klaviyo (email and SMS) + Meta Pixel (paid social attribution) + Google Analytics 4 (web analytics). Brands at scale add server-side tracking (Meta CAPI, GTM server), warehouse syncing (BigQuery, Snowflake), and analytics dashboards (Triple Whale, Northbeam).
- Shopify tracking audit
- A diagnostic process that checks a Shopify store's analytics and tracking instrumentation against a reference model of events and properties. A typical audit identifies missing events (cart_abandoned, return_initiated), incomplete event properties (attribution_source, is_first_order), and missing pixel installations (Meta Pixel, GA4, Klaviyo, GTM). The output is a ranked list of gaps with fix paths, usually as code snippets or no-code Shopify app recommendations.
- Tracking reference model
- A versioned specification of what events, properties, and tables a particular vertical's tracking stack should capture. DataGap's reference model for Shopify DTC covers 50+ events across browse, cart, checkout, post-purchase, retention, and warehouse-hygiene categories. Each entry specifies the canonical event name, required properties, value tier (critical / high / medium), and detection rule. The model is public and versioned at datagap.app/reference-model.RELATEDShopify tracking audit