> 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/model-your-data/commerce-data-models/marketing-attribution/order-attribution-on-chord.md).

# Order attribution on Chord

## Order attribution on Chord

{% hint style="info" %}
This is a **NEW** Explore introduced in May 2025.
{% endhint %}

## Introduction

Since a customer can purchase from a brand more than once, it follows that brands will want to analyze different purchase paths than rolling them all up to the first order’s attribution. Instead of centering analysis at the user-level, this new Explore is centered around orders, or when a customer makes a purchase.

On Chord, we identify the session when a customer makes their first purchase and then we repeat the attribution exercise with every following session as part of Order Attribution. Thus, we apply a brand’s chosen specific attribution methodology based on orders. **Essentially, order attribution allows brands to analyze sessions and revenue for all purchase data.** It’s useful for understanding both marketing attribution and connecting sessions to specific orders.

You can use Chord’s Order Attribution Explore when:

* You want to measure the performance of marketing efforts tied to multiple purchases.
* You're evaluating campaign ROI, revenue by channel, or purchase funnel effectiveness.
* You're reporting on conversion events, like how many orders were driven by a campaign.

## Getting started

![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-bc3885d9f7f40b9caf67759d7b72a7fbb283bc90%2Forder-attribution-on-chord-1.png?alt=media)

![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-feb1948d2b3ee28ea45254c69cc27e3bf8b00aef%2Forder-attribution-on-chord-2.png?alt=media)

![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-60c324531ec3f2b862b358a6a856c0f8b3e0c263%2Forder-attribution-on-chord-3.png?alt=media)

1. Log into the Chord Commerce Data Platform.
2. Navigate to your **Analytics** page.
3. Click the **Explores** tab.
4. Select the **Marketing Attribution - Order Attribution** item in the dropdown menu (see first image).
5. Navigate to the **Order Attribution** Field list on the lefthand side to access the new **attribution point** dimensions (see second image).
6. Select an attribution point dimension applicable to your analysis.
7. Additionally, if you’d like to use different attribution measures, you can select attribution measures under the measures list on the lefthand navigation pane (see third image).

{% hint style="info" %}
For more information on the differences between **Dimensions** and **Measures**, click here.
{% endhint %}


---

# 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/model-your-data/commerce-data-models/marketing-attribution/order-attribution-on-chord.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.