By Andy Gaber, Founder · Published August 13, 2026 · Last updated August 13, 2026
31 terms a Shopify merchant running Meta ads runs into sooner or later — in a GTM debug console, a Meta Events Manager warning, or a developer's explanation of why last week's numbers looked wrong. Each definition links back to Shopify's or Meta's own documentation where one exists, rather than a third-party summary of it.
A snippet of JavaScript that Meta (Facebook/Instagram's parent company) provides so a website can report visitor actions, page views, add-to-cart events, purchases, back to Meta's ad system. Meta uses that data to measure ad performance and build lookalike/retargeting audiences. On Shopify, the Meta Pixel is typically installed through the Meta channel app rather than pasted manually into theme code, though older stores sometimes still have a manually-pasted version left over from before that integration existed.
Meta's server-to-server alternative to the browser-based Meta Pixel. Instead of a visitor's browser sending an event directly to Meta (which ad blockers, Safari's Intelligent Tracking Prevention, and third-party cookie restrictions can all interfere with), the store's own server sends the same event data to Meta directly. Meta explicitly recommends running CAPI alongside the browser Pixel, not instead of it, and uses an event_id field to deduplicate events that arrive from both paths for the same action.
The general category CAPI belongs to: tracking events sent from a server rather than a browser. Server-side events are harder for ad blockers and browser privacy features to stop, because there is no browser-side script for them to block. The tradeoff is that a server-side pipeline is more infrastructure to build and maintain than a pixel snippet, which is the gap that dedicated server-side tracking vendors are built to fill.
A JavaScript array/object that Google Tag Manager (and many other tag managers) read from to know what happened on a page, a purchase, a product view, a cart addition, without each individual marketing tag needing its own custom code. A well-formed dataLayer push typically includes an event name plus structured data (product ID, price, currency), and most GTM tracking failures trace back to a dataLayer variable that stopped populating correctly after a theme or app update.
A free Google product that lets a store manage multiple tracking tags (Meta Pixel, GA4, ad platform pixels, and more) from one interface, without editing theme code for every new tag. GTM reads from the dataLayer and fires the configured tags when specific triggers occur. A GTM container that looks "published" in the GTM interface can still be silently broken if the dataLayer variables it depends on stop populating, publishing a container is not the same as verifying it fires correctly.
Google's current analytics platform, which replaced the older Universal Analytics (fully sunset by Google in mid-2024). GA4 uses an event-based data model rather than Universal Analytics' session-based model, which changed how e-commerce events (purchase, add_to_cart, view_item) need to be structured and sent. A GA4 property with no e-commerce events flowing in for several days is a common early signal of a broader tracking breakage, not just a GA4-specific problem.
Shopify’s own sandboxed system for running pixel/tracking code, documented at shopify.dev, designed to replace older methods (Additional Scripts, manually-edited checkout.liquid) that Shopify is deprecating for security and performance reasons. Pixels registered through the Web Pixels API run in a restricted sandbox and receive standardized Shopify customer events (checkout_started, product_added_to_cart, and similar), rather than having free-form access to the page.
Shopify's framework for customizing checkout using Shopify-approved extension points, replacing the older, less restricted checkout.liquid editing model. Checkout Extensibility is mandatory for all stores as of Shopify's Aug 26, 2026 checkout upgrade, stores still relying on Additional Scripts or checkout.liquid for tracking lose that tracking entirely once the upgrade lands, unless they have migrated to the Web Pixels API first.
The legacy, directly-editable checkout template that many older Shopify stores used to inject custom tracking code (including manually pasted Meta Pixel snippets) directly into the checkout page. Shopify has been phasing checkout.liquid out in favor of Checkout Extensibility; stores that never migrated are the ones most exposed to sudden tracking loss when the Aug 26, 2026 upgrade removes checkout.liquid support entirely.
A legacy Shopify checkout settings field (Settings → Checkout → Order status page / Additional scripts) that let merchants paste custom JavaScript, including tracking pixels, directly into checkout without touching theme files. Like checkout.liquid, Additional Scripts is being removed as part of Shopify’s checkout upgrade; any tracking pixel still relying on this field needs to move to the Web Pixels API or a server-side integration before the deprecation date.
A score Meta assigns (visible in Meta Events Manager) reflecting how well the customer data attached to an event, email, phone, name, IP address, can be matched to a real Meta user profile. Higher EMQ generally means better ad optimization, because Meta can attribute the conversion to the correct person with more confidence. A sudden EMQ drop, even without an outright tracking outage, is a real signal that data quality has degraded somewhere in the pipeline.
The mechanism Meta uses to avoid double-counting a single real-world action (like one purchase) when it arrives from both the browser Pixel and server-side CAPI. Both events need to carry the exact same event_id value for Meta to recognize them as duplicates rather than two separate conversions. A missing or mismatched event_id is a common, hard-to-spot cause of inflated conversion counts that looks like good news but is actually a tracking bug.
Meta's official browser extension for Chrome that inspects a page in real time and reports which Meta Pixel events fired, what data they carried, and any errors Meta detected. It is a useful first diagnostic step for a single page, but it only checks the page you are currently viewing, it does not continuously monitor a whole storefront the way a dedicated monitoring tool does, and it will not tell you a pixel broke three days ago on your product pages while you were looking at the homepage.
The specific Meta Pixel/CAPI event fired when a customer completes an order, generally the single most important event for ad optimization because it is the one tied most directly to revenue. A broken Purchase event does not stop sales from happening; it stops Meta from knowing they happened, which degrades ad targeting and reporting even while the store keeps selling normally, making it one of the more dangerous silent failures to miss.
The baseline Meta Pixel event that fires on every page load, used as a foundation for building custom audiences (like "people who visited in the last 30 days") and as the most basic signal that the Pixel is installed and executing at all. A PageView failure is usually the easiest tracking break to catch, because it is the most frequent event; a Purchase or AddToCart failure is more dangerous precisely because it happens less often and is easier to miss.
The Meta Pixel/CAPI event fired when a shopper adds an item to their cart, used both for ad optimization and for retargeting audiences like abandoned-cart campaigns. Because AddToCart typically fires from theme-level JavaScript rather than Shopify's native checkout events, it is more exposed to breakage from theme updates and app conflicts than checkout-stage events are.
The Meta Pixel/CAPI event fired when a shopper begins the checkout process, sitting between AddToCart and Purchase in the funnel. Because Shopify's Aug 26, 2026 checkout upgrade specifically affects checkout-stage tracking (Additional Scripts, checkout.liquid), InitiateCheckout is one of the events most directly at risk for stores that have not migrated to the Web Pixels API.
Google's version of server-side, hashed first-party data matching for Google Ads (conceptually parallel to Meta's CAPI). It sends hashed customer data (email, phone) alongside a conversion event to improve Google's ability to match the conversion to a real ad click, particularly as browser-level tracking restrictions reduce the reliability of cookie-based matching alone.
Data a business collects directly from its own customers (email addresses at checkout, logged-in account activity, direct purchase history) as opposed to third-party data purchased or inferred from other companies’ tracking. The industry-wide shift toward first-party data is a direct response to third-party cookie restrictions and privacy regulation; both Meta CAPI and Google Enhanced Conversions are built around sending a store’s own first-party data to the ad platform in a privacy-conscious (typically hashed) form.
Cookies set by a domain other than the one the visitor is currently on, historically the backbone of cross-site ad tracking. Browser vendors (Safari and Firefox first, Chrome moving in the same direction) have been restricting or blocking third-party cookies by default, which is the underlying reason server-side tracking (CAPI, Enhanced Conversions) has become the more reliable approach rather than an optional upgrade.
Apple Safari's built-in system for limiting cross-site tracking, including aggressively capping the lifespan of first-party cookies set via JavaScript and blocking many third-party tracking mechanisms outright. ITP is one of the main reasons a Meta Pixel that appears to be installed correctly can still under-report Safari/iOS traffic specifically, which is part of why Meta pushes CAPI as a supplement rather than treating the browser Pixel as sufficient on its own.
Google's framework letting a site adjust what Google tags (GA4, Google Ads) collect based on a visitor's cookie-consent choice, rather than an all-or-nothing block. Stores selling into regions with cookie-consent legal requirements (EU/UK GDPR-adjacent rules, and increasingly some U.S. state laws) need Consent Mode configured correctly, or their GA4/Ads data can be systematically incomplete for visitors who decline consent, which looks like a tracking bug but is actually a consent-configuration gap.
Tagged URL parameters (utm_source, utm_medium, utm_campaign, and related fields) appended to a link so that when someone clicks it, the destination site’s analytics can attribute the visit to a specific campaign. UTM tracking is independent of Meta Pixel/CAPI and GA4 event tracking, but a store diagnosing "why does my traffic look wrong" often needs to check both UTM tagging on outbound links and pixel/analytics tracking on the landing page, since either one breaking can produce similar-looking attribution gaps.
The time period an ad platform looks back to credit a conversion to a specific ad click or view, for example, a "7-day click, 1-day view" window on Meta means a purchase is credited to an ad if it happens within 7 days of a click or 1 day of a view on that ad. Attribution windows shrank industry-wide as third-party cookie and cross-device tracking limitations increased, which is a separate dynamic from outright tracking breakage but often gets confused with it when reported conversions drop.
Meta's general-purpose API for reading and writing data across Meta's platforms (Pages, ad accounts, and more), versioned (e.g., v20, v21) with each version eventually sunset on a published schedule. Apps and integrations built against an older Graph API version stop working once Meta retires that version, which is a distinct failure mode from pixel/CAPI event tracking breaking, but can look similar from a merchant's perspective ("my Meta integration stopped working").
Meta's API specifically for managing ad campaigns programmatically, creating campaigns, adjusting budgets, pulling performance data. Like the Graph API, Marketing API versions are sunset on a schedule Meta publishes at developers.facebook.com; a store or app relying on a version approaching its sunset date needs to migrate before that date or lose programmatic ad-management functionality.
Meta's framework for measuring conversions from users who have limited ad tracking (primarily iOS 14.5+ users who declined App Tracking Transparency), which caps the number of distinct conversion events a domain can report per app and requires those events to be explicitly prioritized. A store that has not configured its AEM event priority correctly can under-report or mis-attribute conversions from privacy-restricted traffic even when the Pixel and CAPI are both technically firing correctly.
Apple's requirement, effective from iOS 14.5, that apps must explicitly ask a user's permission before tracking them across other companies' apps and websites. Most users decline when asked, which sharply reduced the volume of individually-trackable iOS traffic and pushed the ad industry toward aggregated, privacy-preserving measurement approaches like AEM and server-side, modeled conversion reporting.
A version of Google Tag Manager that runs in a server-side container (often on Google Cloud) instead of the browser, letting a store route events server-to-server to multiple destinations (GA4, Meta CAPI, ad platforms) similarly to how CAPI works for Meta specifically, but generalized across more platforms. sGTM is more infrastructure-heavy to set up and maintain than standard client-side GTM, which is the tradeoff vendors selling server-side tracking infrastructure are pricing for.
A specific named value GTM reads out of the dataLayer (for example, a variable that captures the current cart total or product price) and makes available to use inside tags and triggers. A tag that looks correctly configured in the GTM interface will still fail silently if the data layer variable it references stops being populated by the page, which is one of the most common root causes behind "GTM says it published fine but the numbers are wrong."
Shopify's name for the standardized set of events (checkout_started, product_added_to_cart, checkout_completed, and others) that the Web Pixels API exposes to registered pixels, replacing the free-form DOM access older tracking methods relied on. Because these events are standardized by Shopify rather than scraped from page structure, they are less likely to break silently when a merchant changes their theme, which is one of the stated reliability benefits of the Web Pixels API migration.
A specific pixel registered through Shopify's Web Pixels API, either a custom app-based extension a developer builds or one of Shopify's own built-in integrations for major ad platforms. Web Pixel Extensions run in a sandboxed context and can only access the standardized Customer Events API data, a deliberate security tradeoff versus older methods that had broader page access but were more fragile and harder for Shopify to secure.
A step in Meta Business Manager where a business proves ownership of a domain (via DNS TXT record, HTML file upload, or meta tag) in order to control event configuration and priority for that domain under Aggregated Event Measurement. An unverified or incorrectly verified domain can silently limit how Meta processes events from that domain, particularly for privacy-restricted iOS traffic, which is a configuration issue distinct from the pixel simply not firing.
Most terms here (Meta Pixel, Conversions API, GTM, GA4) are platform-agnostic and apply anywhere Meta or Google tracking runs. A handful of entries, Web Pixels API, Checkout Extensibility, Additional Scripts, checkout.liquid, are Shopify-specific, and we say so in each definition.
Because most of the traffic that lands on tracking-breakage problems starts with a specific term someone doesn't recognize in an error log, a GTM debug console, or a Meta Events Manager warning. We would rather explain the term accurately, with a link to the platform's own documentation, than gate that information behind a signup.
Yes, Additional Scripts and checkout.liquid tracking are both being removed from non-Plus store checkouts as part of that upgrade, replaced by the Web Pixels API and Checkout Extensibility. Those four entries cross-reference each other directly below.