> 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/get-started/implementation-guide.md).

# Implementation guide

This guide covers the steps to get Chord collecting data from your store, and how to check that everything is working.

## Before you start

The Chord team provides these values for setup:

| Value         | Description                                   |
| ------------- | --------------------------------------------- |
| CDP domain    | Your Chord endpoint                           |
| CDP write key | Authentication key for sending events         |
| OMS ID        | UUID identifying your order management system |
| Store ID      | UUID identifying your store                   |
| Tenant ID     | UUID identifying your organization            |

Contact <help@chord.co> if you haven't received these values.

## Steps

1. **Add client-side tracking.** Install the Chord analytics package. On Shopify, also add the identifiers script and the Chord web pixel. See browser events for [Shopify](/collect-data/shopify/browser-events.md) or [everyone else](/collect-data/everyone-else/browser-events.md).
2. **Set up server-side events.** These track events that happen outside the browser, such as orders and refunds. See server events for [Shopify](/collect-data/shopify/server-events.md) or [everyone else](/collect-data/everyone-else/server-events.md).
3. **Shopify stores only: install Chord's data ingestor app.** Chord needs to ingest your Shopify data to read historical transactional information. See [Historical data](/collect-data/shopify/historical-data.md).
4. **Verify your implementation** using the checks below.

## Verify your implementation

### Client-side events

1. Open your browser's developer console on any page of your site and run `window.chord`. It should return the Chord analytics object, not `undefined`.
2. Open your browser's developer tools, select the **Network** tab and search for "ingest". You should see your CDP domain load with a 200 status code.

   ![The Network tab filtered to "ingest", showing the CDP domain loading with a 200 status](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-c5bcc34175fad173dcf7eff2f55ea7c0fdedbecb%2Fverify-network-ingest.jpg?alt=media)
3. Take actions on your site that trigger events, such as viewing products or adding to cart. You should see these events post to the CDP domain with your write key and formatted properties.

   ![An event request posting to the CDP domain, with the write key and event properties](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-2e28f81f893fbc8bfa9c0b45286b80f00fdc04ff%2Fverify-event-payload.jpg?alt=media)
4. In Chord, go to **CDP > Live Events > Incoming Events** and filter the list by your website source. You'll see a live stream of events that you can search and filter.

   ![The Incoming Events list filtered to a website source](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-e3dd3f5ff512cace7817ea8a3a45a73625379290%2Fverify-live-events-website.png?alt=media)

### Server-side events

1. Trigger a notification from the system that sends data to Chord, such as a webhook notification for Order Completed or Checkout Started.
2. In Chord, go to **CDP > Live Events > Incoming Events** and filter the list by your back-end source. You'll see a live stream of events that you can search and filter.

   ![The Incoming Events list filtered to a back-end source](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-dd7633b40e3d537307594aefef6d62e39bd86ab0%2Fverify-live-events-backend.png?alt=media)


---

# 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/get-started/implementation-guide.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.