> 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/overview.md). # Overview This section covers getting events from your store into Chord. Chord has a recommended set of tracking events that commerce sites implement to collect transactional and behavioral data. These events power the analytics and insights in Chord. The [tracking plan](/collect-data/tracking-plan.md) lists every event and the properties it expects. Events reach Chord from two places, and you set up both. ## Browser events Browser events come from the shopper's browser as they use your storefront: page views, product views, add to cart and checkout steps. They're sent by `@chordcommerce/analytics`, Chord's browser SDK. It also runs your browser (device-mode) destinations, such as Meta Pixel or GA4. On Shopify, the Chord web pixel works alongside the SDK. Shopify only reports shopper actions to pixels, so the pixel passes them to the SDK, and sends checkout events itself from Shopify's checkout pages. ## Server events Server events come from your backend, or from Shopify's servers, when something happens to an order: placed, cancelled, refunded or shipped. They don't depend on the shopper's browser, so they're the reliable record of what was sold. Chord links them back to the shopper's browser session using an anonymous ID saved on the cart. ## Set up your store * [**Shopify**](/collect-data/shopify.md): Liquid themes, Hydrogen and custom headless Shopify storefronts. * [**Everyone else**](/collect-data/everyone-else.md): Salesforce Commerce Cloud, Adobe Commerce (Magento), SAP Commerce and custom platforms. ## Reference * [**Tracking plan**](/collect-data/tracking-plan.md): every event Chord expects, and the properties each one carries. --- # 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/overview.md?ask=&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.