> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/referral-program/analytics/activity.md).

# Activity Log

The activity log is the raw, event-by-event pulse of your referral program — every join, share, claimed reward, purchase, or ban writes one line here, newest first. Where analytics gives totals, the activity log lets you watch it unfold in real time — useful for confirming momentum, following one customer's path, or grabbing a referrer's share link.

### Activity types

Each entry records one action against one customer:

| Activity  | What it means                                                                                                                           |
| --------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Joined    | A customer joined the program as a referrer and received their share link and code.                                                     |
| Claimed   | A reward was claimed — a referee collected their referral discount, or a referrer received their earned reward.                         |
| Purchased | A referee completed a qualifying purchase, turning a referral into a successful one.                                                    |
| Revoked   | A referrer reward was clawed back because the order behind it was cancelled or refunded. The entry carries a short note explaining why. |
| Banned    | A referrer was banned in the Fraud center and can no longer receive rewards.                                                            |

### What each entry shows

The feed is enriched with details relevant to the action:

* **Joined** entries include the referrer's share link, and their referee discount code if one applies — handy for quickly grabbing a customer's sharing link.
* **Claimed** entries show what was claimed: the referee's discount code, or the referrer's reward (discount code, store credit, cash, or a custom reward's description) and the order it came from.
* **Purchased** entries connect the referee to the order that completed the referral.
* **Revoked** entries name the reward that was reversed and carry the reason (a cancelled or refunded order), linked to the order it came from. See [reward revocation](/referral-program/rewards.md#revoking-a-reward).
* **Banned** entries record that a referrer was blocked.

Every entry shows the customer's name and email and links back to their record, so you can move from a single event to the full customer history in one click.

### Read the feed

Open the **Activity** tab — entries are listed newest first by default, sortable either way. Click a customer in any entry to open their detail and see their full referral chain. A steady run of **Joined** and **Claimed** entries confirms the program is live; **Purchased** events show momentum.

For an aggregated view — conversion rates, revenue, top referrers — use [Referral analytics](/referral-program/analytics/analytics.md) instead; this log is for event-by-event detail.

### Next steps

* See the full picture for one person in [Manage referral customers](/referral-program/management/customers.md).
* Track the discount codes behind **Claimed** events in [Track referral discount codes](/referral-program/management/track-coupons.md).
* Review program results in [Referral analytics](/referral-program/analytics/analytics.md).


---

# 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://docs.bloop.plus/referral-program/analytics/activity.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.