> 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/everyone-else.md).

# Everyone else

Follow these pages to get events flowing into Chord from any commerce platform other than Shopify, such as Salesforce Commerce Cloud, Adobe Commerce (Magento), SAP Commerce or your own custom stack.

## What to set up

Set these up in order:

1. [**Browser events**](/collect-data/everyone-else/browser-events.md)**.** Add the Chord analytics package to your storefront and call it when shoppers act: viewing products, adding to cart, checking out.
2. [**Consent**](/collect-data/everyone-else/browser-events/consent.md)**.** Connect your consent management platform, so Chord respects each shopper's choices.
3. [**Server events**](/collect-data/everyone-else/server-events.md)**.** Send order events, such as Order Completed and Order Refunded, from your backend to Chord's events endpoint.

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

## Reference

* [**SDK reference**](/collect-data/everyone-else/sdk-reference.md): configuration, methods and options for `@chordcommerce/analytics`.
* [**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/everyone-else.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.