# User timeline: see everything one user did · Ahem

Source: https://useahem.com/features/user-timeline

1.  [Home](https://useahem.com)
2.  Features
3.  User timeline

# See everything one user did, in order

Ahem turns the events your app already sends into a timeline for each user. Add a `user` field (an id, a name, an email, or any of them) and every event about that person appears on their timeline: signup, trial, payment, errors, feedback. You open it from any event or the People page, or ask the API for it.

A user timeline in Ahem: one customer’s signup, upgrade, a sync error and her feedback, newest first. Example data.

How it works

## How it works

1.  ### Send the person with the event
    
    Add `user` to any event. Use the same id every time.
    
2.  ### Open any of their events
    
    The event shows who it was about. Click through to their profile on the People page: every event about them, across every channel of the project, grouped by day.
    
3.  ### Or read it from code
    
    `GET /v1/events?user=u_381` returns the same timeline, newest first, for your scripts and support tools.
    

```
{
  "title": "Upgraded to Pro (yearly)",
  "level": "success",
  "type": "subscription.upgraded",
  "user": { "id": "u_381", "name": "Marta P." },
  "metadata": { "amount": 39, "plan": "pro_yearly" }
}
```

The product calls this **People**: a list of everyone your events are about, each with a profile and this timeline.

Use cases

## What you can do with it

### Answer support emails with the facts

“My streak reset!” Open her timeline: a timezone error at 23:59, two minutes before the reset. You reply with the cause, not a guess.

### Notice churn before it happens

A failed renewal, two errors and a 2★ rating in one week is a customer worth a personal email.

### Debug with the five events before the error

What the user did right before the crash is usually the bug report you never got.

### Thank your first customers by name

Your first hundred paying users each have a story. Now you can read it.

## Details and limits

<table class="compare two-col" data-astro-cid-fx4qdzz2=""><tbody data-astro-cid-fx4qdzz2=""><tr data-astro-cid-fx4qdzz2=""><th scope="row" data-astro-cid-fx4qdzz2="">Fields</th><td data-astro-cid-fx4qdzz2=""><code data-astro-cid-fx4qdzz2="">user.id</code>, <code data-astro-cid-fx4qdzz2="">user.name</code>, <code data-astro-cid-fx4qdzz2="">user.email</code>, each up to 200 characters</td></tr><tr data-astro-cid-fx4qdzz2=""><th scope="row" data-astro-cid-fx4qdzz2="">Timeline key</th><td data-astro-cid-fx4qdzz2="">The id if you send one, otherwise the email</td></tr><tr data-astro-cid-fx4qdzz2=""><th scope="row" data-astro-cid-fx4qdzz2="">Scope</th><td data-astro-cid-fx4qdzz2="">One project. The same person in two of your apps has two timelines.</td></tr><tr data-astro-cid-fx4qdzz2=""><th scope="row" data-astro-cid-fx4qdzz2="">History</th><td data-astro-cid-fx4qdzz2="">As long as your plan keeps events: 7 days on Free, 365 days on Maker</td></tr><tr data-astro-cid-fx4qdzz2=""><th scope="row" data-astro-cid-fx4qdzz2="">On every plan</th><td data-astro-cid-fx4qdzz2="">The People list, search, profiles and timelines, adding and editing people, erasing a person with their events</td></tr><tr data-astro-cid-fx4qdzz2=""><th scope="row" data-astro-cid-fx4qdzz2="">On Maker</th><td data-astro-cid-fx4qdzz2="">Details on people from <code data-astro-cid-fx4qdzz2="">user.properties</code> (plan, country, MRR), watching a customer, and funnels on the overview (up to 20 per project)</td></tr><tr data-astro-cid-fx4qdzz2=""><th scope="row" data-astro-cid-fx4qdzz2="">API</th><td data-astro-cid-fx4qdzz2=""><code data-astro-cid-fx4qdzz2="">GET /v1/events?user={id or email}</code> and <code data-astro-cid-fx4qdzz2="">/v1/people</code>, with a key that has <code data-astro-cid-fx4qdzz2="">events:read</code></td></tr><tr data-astro-cid-fx4qdzz2=""><th scope="row" data-astro-cid-fx4qdzz2="">Privacy</th><td data-astro-cid-fx4qdzz2="">Send an id only if you’d rather not store emails or names with Ahem. Deleting an event removes it from the timeline.</td></tr></tbody></table>

## Compared with product-analytics tools

Mixpanel, PostHog and Amplitude build user journeys from page views and clicks collected by an SDK in your app. Ahem’s timeline is built from the handful of events you chose to send from your backend: the ones a person would actually want to read. Maker adds simple funnels on the overview, with each step written as an inbox search, but Ahem is not a replacement for cohorts or product analytics. LogSnag has a similar “journeys” feature; Ahem adds severity levels and per-channel notification rules on top.

[Compare Ahem with LogSnag](https://useahem.com/vs/logsnag)

FAQ

## Questions

**Do I need to identify users up front?**

No. There is no separate “identify” call. Any event that carries a `user` adds to that person’s timeline. You can also add a person before their first event, in the app or with `PUT /v1/people/{id}`.

**Can I see a user across all my projects?**

Not today. A timeline belongs to one project, because each project usually has its own user ids.

**Can I delete everything about one person?**

Yes. Erasing a person, in the app or with `DELETE /v1/people/{id}`, deletes them and every event about them.

**Is this GDPR-friendly?**

You decide what you send. Many people send only an internal id and keep names and emails in their own database.

## Related

[Guide · **Phone notifications from Claude Code**](https://useahem.com/guides/claude-code-notifications) · [Compare · **Ahem and six other tools, side by side**](https://useahem.com/compare) · [Pricing · **What Free and Maker include**](https://useahem.com/pricing)

## Add user to one event and open its timeline.

[Start free](https://app.useahem.com/sign-in) · [Read the API docs](https://app.useahem.com/docs)
