Online Store Analytics Agent
Tracks the shopping funnel and repeat purchase and explains drops.
- Industry
- Retail
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Investigator
- Approver
- E-commerce Director
- Code
- PRD-06
It tracks the online shopping funnel (visit, search or browse, product page, add to basket, checkout, order) and repeat purchase by cohort on web and app, and when a step drops or a cohort repeats less, explains why by testing competing causes: a release, a tracking change, a traffic mix shift, stock availability, a price or delivery fee change, a payment failure or seasonality. It ranks the causes by evidence and files the insight with the owning team. **The problem it solves:** Why a step in the online shopping funnel or repeat purchase changed: which step, on which device, since when, and what changed around it.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the e-commerce platform: funnel analytics by step, device and traffic source for the window and baseline, the release log and online stock availability of top sellers..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to E-commerce Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the product management tool: it files the insight with the owning team. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The analytics guide: funnel definitions, conversion baselines by device and season, tracking change log, release calendar, promotional calendar and the known causes of funnel drops in retail.
Reads from
the e-commerce platform: funnel analytics by step, device and traffic source for the window and baseline, the release log and online stock availability of top sellers.
Acts in
the product management tool: it files the insight with the owning team.
Hands back
An object with step, change_percent, causes (a ranked list, each with cause, evidence, confidence and how_to_confirm), orders_lost_estimate, owner_team and urgent (true or false).
Asks a person when
A checkout or payment step dropped 15 percent or more, or the cause points to a payment or data incident.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Change worth explaining (%) | 8 | A step moving this much from baseline is explained. |
| Baseline (weeks) | 4 | The comparison window, adjusted to the same weeks last year in a trading peak. |
| Rule out tracking first | On | When on, a tracking or tag change is ruled out before any other cause. |
| Urgent drop at checkout (%) | 15 | A checkout or payment step falling this much is urgent, because orders are being lost now. |
| Least sessions to judge | 5000 | A segment with fewer sessions in the window is not judged. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Explain a step that moved 8 percent against the 4-week baseline, or the same weeks last year in a peak.
- When on is true, rule out a tracking or tag change before any other cause.
- Weigh competing causes by evidence: a release, traffic mix, stock-outs on top sellers, price or delivery fee changes, payment provider errors, site speed and seasonality.
- A checkout or payment drop of 15 percent is urgent and goes to the owning team and the E-commerce Director at once.
- Judge only segments with 5000 sessions or more.
See the Online Store Analytics Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.