> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/referrals/tracking-referral-progress.md).

# Tracking Referral Progress

**The Referrals page is your control panel — level, tasks, rewards, and the invitees flowing through.**

Use the Referrals page to monitor invited users, your current account level, in-flight tasks, and accrued rewards. The panel surfaces the state of every stage of the funnel; this page is the map.

{% hint style="success" %}
**Read the panel, not the email**

The Referrals page is the source of truth for your account state — not external notifications, screenshots, or third-party trackers.
{% endhint %}

## Progress Panels

The Referrals page composes several blocks:

* **Current level** — what your account has reached.
* **Next level** — what the next tier unlocks.
* **Level details** — the conditions and benefits attached to your tier.
* **Referral percentages** — your share of rewards.
* **Tasks** — active actions tied to invites or trading.
* **Reward panel** — claimable balances and totals.
* **User name block** — your identity for the referrals system.

Together these tell you what your account has unlocked and what activity might be needed for the next level.

## Tasks

Tasks orchestrate the activity that contributes to referral progress. They can reference:

* **Inviting friends.**
* **Making trades.**
* **Completing transactions.**

If there are no active tasks for your account, the panel shows a **no-tasks** state. That's a normal idle state — not an error.

## Level Details

Level details can expose:

* **Current level.**
* **Unlocked states** for benefits.
* **Upgrade status** — eligibility for next tier.
* **Instant upgrade** option when available.
* **Status upgrade cost** when paid upgrades are exposed.
* **Trading volume to upgrade** — the activity threshold for the next tier.

Treat these as **account-specific** — they differ by network, product mode, and current eligibility. Don't compare against another account's view as a benchmark.

## Reviewing Results

A regular cadence for checking referral progress:

* **Invitee count.** Did the number of invited users go up?
* **Status changes.** Did any invitee status advance (pending → active → trading)?
* **Reward changes.** Did earned SOL, USDCe, or points move?
* **Claimable balances.** Are any rewards now claimable?
* **Awaiting withdrawal.** Anything in-flight from a previous claim?

If values don't update after expected activity — **wait for processing**, then check again. Indexing can lag a few seconds to a few minutes on busy networks. Don't assume the referral didn't count until processing has clearly settled.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/a59SPBTSoTjUn3JjsVCP"><strong>Referral Link</strong></a></td><td>The funnel's entry point.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/7FUZgcWcqRilPG9GsUYw"><strong>Inviting Users</strong></a></td><td>What turns a click into a tracked invite.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/smBjK7KKa5qg1hWO3uYw"><strong>Referral Rewards</strong></a></td><td>The reward side of progress.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr></tbody></table>

{% hint style="info" %}
A frozen progress view almost always means an indexing lag or a missed task condition — not a system error. Re-check after a short delay before assuming something's wrong.
{% endhint %}

## FAQs

<details>

<summary>How often does the Referrals page update?</summary>

Near real-time. Indexing can delay surface time by seconds to minutes during high-activity windows.

</details>

<details>

<summary>I see no tasks — is something broken?</summary>

Not necessarily. The no-tasks state appears when no active tasks are scoped to your account. New tasks can surface as the product evolves.

</details>

<details>

<summary>Why hasn't my next-level upgrade triggered yet?</summary>

Check the upgrade conditions — trading volume, invite counts, or tier-specific requirements. Each is enumerated in level details. Meeting all conditions usually triggers automatically; some flows expose an Instant upgrade button when applicable.

</details>

<details>

<summary>Can I see who invited a downstream Level 2 or Level 3 user?</summary>

The user table surfaces the rows visible to your account. Downstream attribution depends on the current level structure shown for your account.

</details>

<details>

<summary>What's the fastest way to audit a missing invitee?</summary>

1\) Confirm they used your link. 2) Confirm they completed any required sign-in / wallet step. 3) Check whether referral tasks require trading activity that hasn't happened. 4) Wait for indexing. 5) Re-check.

</details>


---

# 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 dynamically by asking a question.

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

```
GET https://graphdex-1.gitbook.io/graphdex-docs/referrals/tracking-referral-progress.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
