hydrogen-headless-trackinglisted

# Hydrogen Headless Tracking Build an auditable event path across three separate surfaces: the Hydrogen storefront, Shopify-hosted pixels/checkout, and a server-side provider or webhook consumer. Do not collapse them into one browser-runtime assumption. ## Inspect the accepted event contract first Identify the business objective, provider, event names, source of truth for each event, consent purpose, allowed fields, retention, merchant/store scope, cart and checkout domains, current analytics implementation, CSP, webhook receiver, deduplication store, and tests. Do not print credentials or customer data. Read [Tracking delivery contract](references/delivery-contract.md) for all tracking work. Read [Shopify-hosted Web Pixels](references/web-pixels.md) for an App Pixel or Custom Pixel. Retrieve current official provider documentation before using its event fields, hashing rules, deduplication window, endpoint, or API version. Read [Shopify analytics cookie migration](references/shopify-analytics-cookie-migration.md) when an existing Hydrogen integration reads or depends on Shopify visitor or session cookies. ## Keep execution surfaces separate - **Hydrogen storefront:** owns server-rendered commerce interactions and its supported analytics/consent integration. Keep client enhancement optional. - **Shopify-hosted checkout and Web Pixels:** run in Shopify-controlled sandboxes. Use only their documented APIs; do not reuse Hydrogen session or DOM assumptions. - **Server