# Attribution

<figure><img src="/files/k1tFXOm9eTxfqHRKdw9N" alt=""><figcaption></figcaption></figure>

***

## Table of Contents

1. [Tutorials](#tutorials) (Q3 2025)
2. [First click Attribution Model ](#first-click-attribution-model)
3. [Channels Source ](#channel-source)

***

## Tutorials (Q3 2025)

***

## First click Attribution Model

Safary uses **a "first click" attribution model.** This means the source is determined by where a user first came from. Users retain this source tag throughout their lifetime, even when they return through different channels. First click attribution works well for crypto because users typically visit websites multiple times before making decisions.

{% hint style="info" %}
Many crypto users are labeled as "Direct" traffic, meaning they access your website by typing its name directly into Google or their browser's URL bar. We recommend implementing the Safary script before launch to identify these users' true traffic sources before they develop the habit of accessing your site directly.
{% endhint %}

***

## Visualize your Full Funnel

We built the attribution table to make it easy for you to recreate your full funnel and identify the conversion rates of your website.&#x20;

* Add multiple columns based to visualize all your events&#x20;
* Group by **channels, campaigns or device**&#x20;

{% hint style="info" %}
The Attribution table will only show **Connected Users** and **Connect Wallets.** We exclude the users imported through CSV or the wallets imported through Farcaster or socials which haven't been connected to your website.&#x20;
{% endhint %}

<figure><img src="/files/jiRZ2vBMJ9xbT4COeKfr" alt=""><figcaption></figcaption></figure>


---

# 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://safary-1.gitbook.io/safary-doc-2.0/dashboards/attribution.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.