# How our attribution works?

## Conversion event attribution

### OnChain Conversion Events Attribution

For onchain conversion events, we cannot pinpoint the exact visitor who fulfilled the conversion event, as we only have information about the wallet that performed the onchain action. 

<figure><img src="/files/LQzjDb8bdYjnxot4u2Us" alt=""><figcaption><p>This is how we assign conversion events to specific website or app visits</p></figcaption></figure>

To attribute the goal, we search through all visits to the website for instances where the visitor connected the wallet that completed the goal. We then select the visit closest to the goal completion date, matching it to the wallet. Once the visitor is identified, we apply the last non-direct click attribution model, as outlined in the previous section.

### OffChain Conversion Event Attribution

For offchain goals, we can identify the specific visitor who fulfilled the goal. The goal of attribution is to determine the exact visit that should be linked to the goal’s completion. This is crucial because it allows us to credit the appropriate links or referrers responsible for driving the goal conversion. We use a **last non-direct click attribution** model. This model identifies the most recent visit before the goal completion that was not direct—meaning it had a referrer or UTM parameters associated with it. If all visits were direct, the model attributes the closest visit to the goal.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cookie3.com/cookie3-analytics/features/conversion-events/how-our-attribution-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.