What Is a Shopify Web Pixel? Modern Tracking Script API Explained

A Web Pixel is Shopify's official API for running tracking and analytics scripts on your storefront and checkout pages. Introduced as part of Shopify's Checkout Extensibility platform, Web Pixels replaced the legacy approach of injecting scripts directly into checkout.liquid or the "Additional Scripts" field that Shopify removed for stores on Checkout Extensibility. The key architectural difference is that Web Pixels run inside a sandboxed iframe, meaning they cannot access the main page's DOM, cookies, or local storage directly.

There are two types of Web Pixels. App Pixels are managed by Shopify apps — when you install a tracking app like ScaleUp, it registers an App Pixel that Shopify loads automatically on all pages including checkout. Custom Pixels are JavaScript snippets you write and configure manually through the Shopify admin under Settings > Customer Events. Both types receive the same standardized e-commerce events from Shopify (page_viewed, product_viewed, checkout_started, payment_info_submitted, checkout_completed, and others) through the Shopify Web Pixel API.

The move to Web Pixels represents a fundamental shift in how Shopify handles third-party tracking. Instead of giving scripts full access to the page — which created security risks, privacy concerns, and performance issues — Shopify now acts as the intermediary. Your tracking scripts receive structured event data from Shopify rather than scraping it from the page. This is more reliable (no more broken selectors when themes update), more private (scripts only get the data Shopify chooses to expose), and more secure (sandboxed scripts cannot modify the checkout experience).

Web Pixels matter because they are now the only way to run tracking scripts on Shopify checkout pages for stores on Checkout Extensibility. Shopify deprecated checkout.liquid in August 2024 and required all Shopify Plus stores to migrate to Checkout Extensibility by early 2025. Standard Shopify stores were transitioned automatically. If your Google Ads tracking relied on scripts in checkout.liquid or the Additional Scripts field, those scripts stopped working after the migration. Web Pixels are the required replacement.

For Google Ads tracking specifically, the transition to Web Pixels affects how conversion data is captured. The old approach of placing a gtag.js snippet in your checkout page and reading order data from the dataLayer no longer works. Instead, your tracking code (whether via an app or a custom pixel) must listen for Shopify's standardized checkout_completed event and extract the conversion data from the event payload. This includes the order total, transaction ID, currency, and line item details. The event structure is defined by Shopify, not by your theme or custom code, which makes it more consistent but also means you must adapt to Shopify's data format.

The sandbox model also impacts cookie-based tracking. Because Web Pixels run in an iframe, they cannot directly access first-party cookies set on your main domain. This means traditional cookie-based attribution (reading the _gcl_aw cookie to get the GCLID) does not work inside a Web Pixel. Tracking apps must use alternative methods — such as passing attribution data through Shopify's event payload, using server-side approaches, or leveraging Enhanced Conversions — to maintain accurate Google Ads attribution. This is a significant technical change that catches many merchants off guard during migration.

When a page loads on your Shopify store, Shopify's platform checks which Web Pixels are registered for your store. Each pixel is loaded inside its own sandboxed iframe — a completely isolated browser context that shares neither cookies, local storage, nor DOM access with the main page. Shopify then pushes standardized e-commerce events into each pixel's iframe through a messaging API. For example, when a customer views a product, Shopify fires a product_viewed event containing the product title, price, variant ID, and other structured data. Your pixel code receives this event and processes it however you need — typically by sending it to Google Ads, GA4, or another analytics platform.

The event flow continues through the entire customer journey. As a customer adds items to cart, begins checkout, enters payment info, and completes the purchase, Shopify fires corresponding events (collection_viewed, product_added_to_cart, checkout_started, payment_info_submitted, checkout_completed) into every registered pixel. The checkout_completed event contains the full order details: transaction ID, subtotal, tax, shipping, discount codes applied, line items with quantities and prices, and the customer's email (if consent is granted). This data is what your pixel code uses to send conversion events to Google Ads.

For App Pixels specifically, the app developer (such as ScaleUp) writes the pixel code and registers it through Shopify's Partners API. When a merchant installs the app and enables tracking, Shopify begins loading that pixel on every page. The app can also configure which customer events it wants to receive and can store configuration data that gets passed to the pixel at load time. Custom Pixels work similarly, but the merchant writes the JavaScript directly in the Shopify admin. Both types have access to the same event stream and the same sandbox constraints.

The most significant issue merchants face with Web Pixels is the loss of cookie-based attribution data. Because pixels run in a sandboxed iframe, they cannot read first-party cookies like _gcl_aw (GCLID) or _ga (GA4 client ID) that were set on the main domain. If your tracking relies on reading these cookies at conversion time, it will break inside a Web Pixel. This is the primary reason many Shopify stores see a drop in attributed conversions after migrating to Checkout Extensibility — the conversion fires, but the attribution link to the original ad click is lost.

Another common issue is incomplete event data in Custom Pixels. While Shopify's standardized events provide structured data, certain fields may be empty depending on your store's configuration, the customer's consent choices, and the specific checkout flow. For example, the customer email in checkout_completed may be redacted if the customer has not consented to marketing. Line item data may use variant IDs that do not match the product IDs you have in your Google Merchant Center feed. These mismatches require careful data mapping in your pixel code.

Web Pixels are part of Shopify's broader tracking infrastructure. Understanding these related concepts helps you navigate the transition to modern Shopify tracking effectively.