> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/collect-data/shopify.md).

# Shopify

Follow these pages to get events flowing from your Shopify store into Chord. They apply to every Shopify storefront: Liquid themes, Hydrogen and custom headless builds.

## What to set up

Set these up in order:

1. [**Browser events**](/collect-data/shopify/browser-events.md)**.** Add the Chord analytics package, the identifiers script and the Chord web pixel. These track shopper activity on your storefront and checkout.
2. [**Consent**](/collect-data/shopify/browser-events/consent.md)**.** Set the pixel's privacy settings and turn on a cookie banner, so Chord respects each shopper's choices.
3. [**Server events**](/collect-data/shopify/server-events.md)**.** Create the Chord Webhook Events app. Shopify then sends live order and customer events to Chord as they happen.
4. [**Historical data**](/collect-data/shopify/historical-data.md)**.** Create the Chord Data Ingestor app. Chord uses it to bring in your past orders and other store data.

Browser events and server events are separate sources. Set up both so Chord sees the full journey, from browsing through purchase and refund.

## Optional

* [**Subscription events**](/collect-data/shopify/server-events/subscription-events.md), if your store sells subscriptions.

## Reference

* [**Webhook events reference**](/collect-data/shopify/server-events/webhook-events.md): the Shopify webhook topics Chord listens to, and the events they produce.
* [**Support access**](/collect-data/shopify/support-access.md): how to give Chord's support team access to your store. We recommend every store does this.
* [**Tracking plan**](/collect-data/tracking-plan.md): every event Chord expects, and its properties.


---

# 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.chord.co/collect-data/shopify.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.