> 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/connect-sources/chord-cdp/cdp-sources.md).

# CDP sources

## CDP sources

A CDP (Customer Data Platform) source is any system or touchpoint where customer data originates before being collected and unified in the CDP. CDP sources include ecommerce platforms, server-side applications, or third-party tools that generate customer interactions and behavioral data.

## Source types

### Browser sources

A browser source captures data directly from a customer's browser in real-time as they interact with your website. This includes page views, product views, completed orders, and other front-end interactions. Browser sources use JavaScript SDKs to track customer behavior as it happens.

### Server sources

A server source sends data from your backend systems or applications to the CDP. This includes order data, customer account information, subscription updates, or any events that happen on your servers rather than in the customer's browser. Server sources give you more control over data quality, aren't affected by ad blockers or browser restrictions, and are ideal for tracking sensitive information or backend processes that don't have a user interface. Please see the [Server Events Overview](/collect-data/everyone-else/server-events.md) documenation for more information.

## Understanding write keys

Each CDP source uses one or more write keys to authenticate and route data into the Chord platform. Write keys are unique identifiers that ensure data is sent to the correct source and CDP workspace account. When implementing tracking via SDKs or APIs, you'll need to use the appropriate write key(s) for your configured source.

{% hint style="danger" %}
Write keys are sensitive credentials. Treat them like passwords and never expose them in public repositories.
{% endhint %}

## Viewing your sources

Sources are configured and managed by the Chord team during your initial CDP setup and integration process. To view your configured sources:

1. Navigate to the **CDP Overview** page on Chord.
2. View **Sources** on the left hand side of the page.

## Working with sources

If you need to add a new source, modify an existing source configuration, or have questions about your source setup, please contact your Chord integration team or [reach out to Chord support](mailto:help@chord.co).


---

# 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/connect-sources/chord-cdp/cdp-sources.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.