---
title: Migrate Hydrogen analytics tracking
description: >-
  Maintain analytics attribution for your Hydrogen integration as Shopify
  deprecates the `shopify_y` (unique visitor) and `shopify_s` (session) cookies.
source_url:
  html: >-
    https://shopify.dev/docs/storefronts/headless/legacy/hydrogen/migrate/cookies
  md: >-
    https://shopify.dev/docs/storefronts/headless/legacy/hydrogen/migrate/cookies.md
api_name: hydrogen
---

Legacy Hydrogen

These pages refer to Hydrogen versions 2026-04 and earlier. For versions 2026-10 and later, refer to the latest [Hydrogen docs](https://shopify.dev/docs/storefronts/hydrogen). If you're not using the latest version of Hydrogen, then we recommend that you migrate your storefront. To learn more, refer to [Migrate to the latest version of Hydrogen](https://shopify.dev/docs/storefronts/hydrogen/migrate).

# Migrate Hydrogen analytics tracking

This guide explains how to maintain reliable [Shopify Analytics](https://help.shopify.com/en/manual/reports-and-analytics/shopify-reports) data for your Hydrogen integration without using the `shopify_y` (unique visitor) and `shopify_s` (session) cookies, which will be deprecated on April 30, 2026.

It includes instructions on how to migrate analytics tracking for different types of Hydrogen apps (React Router/Remix) deployed to Oxygen or to another host.

**Caution:**

If you don't migrate your analytics tracking before April 30, 2026, then the data for your integration's visitors and session attributions won't be reported accurately in Shopify Analytics.

***

## What's changing

Shopify will stop setting `shopify_y` and `shopify_s` cookies on April 30, 2026. Hydrogen now provides utilities that give you access to equivalent tracking values:

* `uniqueToken` replaces `_y`
* `visitToken` replaces `_s`

These values aren't meant to be read from browser cookies directly. Instead, fetch them using Hydrogen's utilities so they continue to provide data as privacy models evolve.

***

## Step 1: Update your Hydrogen build

Choose one of the following approaches based on how you've deployed Hydrogen:

* [Deployed to Oxygen](#hydrogen-deployed-to-oxygen)
* [Deployed to other hosts (like Node, Edge, or serverless)](#hydrogen-deployed-to-other-hosts)

**Info:**

The steps you need to take will be different if you have a [custom headless setup](https://shopify.dev/docs/storefronts/headless/legacy/hydrogen/migrate/cookies-custom-setup).

### Hydrogen deployed to Oxygen

In this case, only one step is required: run the Hydrogen CLI upgrade command (`shopify hydrogen upgrade`) to upgrade Hydrogen to the latest minor in your line (`2024.7–2025.7`).

You don't need to make any server-side changes on Oxygen.

For code examples, refer to our default [skeleton template](https://github.com/Shopify/hydrogen/blob/f4c30410d29291ea5550d85a5976d822da0f24b4/templates/skeleton/server.ts).

### Hydrogen deployed to other hosts

In this case, you need to make two small changes:

1. Run the Hydrogen CLI upgrade command (`shopify hydrogen upgrade`) to upgrade Hydrogen to the latest minor in your line (`2024.7–2025.7`).
2. Use Hydrogen's web-standard request handler so headers and cookies flow correctly through your domain. Choose the approach below based on your host's Web Fetch API support.

#### If your host supports Web Fetch API (Request/Response)

Use Hydrogen's `createRequestHandler` directly as your server entry point. No adapter is required.

## server.ts

```ts
import {createRequestHandler, createHydrogenContext} from '@shopify/hydrogen';
import {build} from './build'; // your Remix build
const mode = process.env.NODE_ENV;
const hydrogenContext = createHydrogenContext({
  // include storefront at minimum
  // storefront: createStorefrontClient({...})
});
const handleWebRequest = createRequestHandler({
  build,
  mode,
  getLoadContext: () => hydrogenContext,
});
export default {
  async fetch(request: Request): Promise<Response> {
    return handleWebRequest(request);
  }
};
```

#### If your host doesn't support Web Fetch API (Request/Response)

You can adapt Node.js requests to the Web Fetch API using a package such as [@remix-run/node-fetch-server](https://www.npmjs.com/package/@remix-run/node-fetch-server) (which is used by React Router's Node.js adapter), and then pass the request to Hydrogen's `createRequestHandler`:

## server.ts

```ts
import {createRequestHandler} from '@shopify/hydrogen';
import {createRequestListener} from '@remix-run/node-fetch-server';


// ...


const handleWebRequest = createRequestHandler({
  build,
  mode,
  getLoadContext: () => hydrogenContext,
});


const handleNodeRequest = createRequestListener(async (request, client) => {
  return handleWebRequest(request);
});


http.createServer(handleNodeRequest, ...)


// ...
```

***

## Step 2: Validate your changes

After you update your Hydrogen build, validate that your analytics tracking has been set up correctly.

1. Open your Shopify storefront.
2. Add a product to the cart, and then check out.
3. If cookies are enabled (meaning there's tracking consent), then you should see a `produce_batch` event. The payload has `custom_storefront_customer_tracking/1.2`.
4. If cookies aren't enabled (meaning there's no tracking consent), then you won't see a `produce_batch` event with a payload of `custom_storefront_customer_tracking/1.2`.

In the following example, `_shopify_s` matches the `deprecated_visit_token` value and `_shopify_y` matches the `unique_token` value.

![Developer tools showing cookie values](https://shopify.dev/assets/assets/images/custom-storefronts/hydrogen/cookie-values-hMGQl29S.png)

The exact payload fields might vary depending on which events fire.

***