> For the complete documentation index, see [llms.txt](https://docs.nosto.com/shopify/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nosto.com/shopify/tracking-and-session-management.md).

# Tracking & Session Management

Nosto relies on accurate session tracking to deliver personalized experiences and measure performance. Depending on how your Shopify store is built, the tracking setup may differ.

Use this page to choose the right guide for your store’s technical setup:

## Choose your Storefront Type

### Standard Shopify Storefronts

If your store uses Shopify’s built-in Online Store and a theme like Dawn, Refresh, or any other Online Store 2.0-compatible theme, this is the guide for you:

→ [Go to Standard Shopify Storefront Tracking](https://docs.nosto.com/shopify/tracking-and-session-management/standard-shopify-storefronts)

Tracking is handled through:

* The Nosto script and 2c.cId cookie
* Nosto's Shopify Pixel

{% hint style="info" %}
This is the most common setup used by merchants who manage their store using the Shopify theme editor.
{% endhint %}

### Custom Storefronts (Hydrogen, Headless & more)

If you’re using a **custom storefront**, such as one built with Shopify Hydrogen, Next.js, or another headless setup, you’ll need a slightly different tracking setup:

→ [Go to Custom Storefront Tracking](https://docs.nosto.com/shopify/tracking-and-session-management/custom-storefronts-hydrogen-headless-and-more)

Tracking can be handled through:

* Manual session token syncing to Nosto
* Nosto's Shopify Pixel
* Custom logic to bridge tracking gaps


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nosto.com/shopify/tracking-and-session-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.