Capability
ARCY Pulse
One place to read how your product is actually going: where users stall, what they fight, what they ask, and what ARCY recovered, in the order worth acting on.
Insights
- Identity documents lost 1,979 sellers this window.Create a flow for this stepI1
- "Which documents count as proof of address?" was asked 88 times and your sources answer none of it.Add a sourceI2
- 412 sessions struggled on /onboarding/documents.Create a flow hereI4
If nothing notable happened, this rail renders nothing at all.
What it does
A product owner has plenty of numbers and no answer to the only question that matters on a Monday morning: what is wrong right now, and what do I do about it. Pulse ranks what ARCY saw last week by size, names the route it happened on, and puts the action next to it.
- Ranks what changed, so the top of the page is the thing worth reading
- Names the route and the step behind every number, never a score on its own
- Carries the action ARCY can take there, so a finding does not end in a shrug
- Links straight through to the sessions and conversations the number came from
How it works
- It reads the signals ARCY already hasDrop-off, struggle signals, conversations and measured lift are all derived from the events arcy.js sends. Pulse is the place they are put next to each other, so a stall, the behavior around it and what users asked about it are one story rather than three tabs.
- Findings are ranked, not listedA rail of twenty equal cards is a list nobody reads. Pulse orders by how much is running through the problem, so the first item is the one with the most at stake this week.
- Every finding carries an actionA place, a number and something ARCY can do there. If there is no action, the finding does not render, because a number you cannot act on is only a reason to feel bad.
- Quiet weeks look quietWhen nothing notable happened, Pulse says so rather than padding the page. An overview that always looks urgent stops being read within a month.
The technical detail is in the documentation
The documentation is the maintained version, written for the person who will install this. This page does not restate it.
Read the documentationRelated
See your own product's week
Book a walkthrough and we will read your first week back to you, ranked, on your own routes.