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.
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.
How it works
Add user to any event. Use the same id every time.
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.
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
“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.
A failed renewal, two errors and a 2★ rating in one week is a customer worth a personal email.
What the user did right before the crash is usually the bug report you never got.
Your first hundred paying users each have a story. Now you can read it.
| Fields | user.id, user.name, user.email, each up to 200 characters |
|---|---|
| Timeline key | The id if you send one, otherwise the email |
| Scope | One project. The same person in two of your apps has two timelines. |
| History | As long as your plan keeps events: 7 days on Free, 365 days on Maker |
| On every plan | The People list, search, profiles and timelines, adding and editing people, erasing a person with their events |
| On Maker | Details on people from user.properties (plan, country, MRR), watching a customer, and funnels on the overview (up to 20 per project) |
| API | GET /v1/events?user={id or email} and /v1/people, with a key that has events:read |
| Privacy | Send an id only if you’d rather not store emails or names with Ahem. Deleting an event removes it from the timeline. |
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.
FAQ
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}.DELETE /v1/people/{id}, deletes them and every event about them.