> 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/user-attribution-on-chord.md).

# User attribution on Chord

{% hint style="info" %}
This is our original marketing attribution explore. It was previously called the ***Marketing Attribution Explore***.
{% endhint %}

## Introduction

On Chord, user attribution is the process of determining which marketing channel, campaign, or touchpoint led to a specific purchase at the user level. **A brand should select this attribution Explore when they want to better analyze when a user became a customer (i.e. when someone made a purchase)**. It helps you understand what drove a customer to *convert*—whether that was an ad, an email, a discount code, or another action right before the sale.

Based on the specific attribution points selected (first-touch, last-touch, linear, or 40-20-40), Chord will attribute revenue metrics based on when the user converts (i.e. makes a purchase).

You can use Chord’s User Attribution Explore when:

* You're tracking customer acquisition or lifecycle journeys.
* You want to understand which sources or campaigns brought in high-value or loyal customers.
* You're segmenting customers by first touch or most recent meaningful engagement.

## Getting started

![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-0c0f35ef9cd72865f09cf233a12e98be2c1173da%2Fuser-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-58758a5e64e1317adac127b62d56ae4ab2c0804e%2Fuser-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-3a1802be4902735d0b809c8cc3ac394c6fc1c7fe%2Fuser-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 - User Attribution** item in the dropdown menu (see first image).
5. Navigate to the **User 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/user-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.