How a review week runs

Ten working days, one path, no hosted dashboard. This page is the sequence we actually follow.

This is the custom working method for conversion funnel analytics at Page Grove Hub. If you need dates on a calendar rather than a description, write to us after you skim the flagship review.

Day 0 — Access, not theatre

You name the path and the success event in a sentence. We send a short access list: export format, date range, and whether iOS and Android must be split from hour one. Nothing is “connected” on our side beyond a folder for your files.

Days 1–2 — Dictionary before counts

Wei Jun (or whoever is assigned) lines up event names against screens. Duplicate fires, screen-view events pretending to be taps, and OS drift get a strike-through. If the dictionary is fiction, we say so before any percentage is written.

Days 3–5 — The step table

Amina rebuilds up to eight steps. Each row is a screen or a decision, not a marketing stage. Conversion is counted only with the definition you locked on day 0. Gaps in instrumentation stay visible as gaps.

Days 6–7 — Recordings against the table

We watch a sample you help select — usually failures at the suspected step, plus a handful of successes. The written map will quote gestures (back swipe, permission deny) rather than invent causes from counts alone.

Days 8–9 — The document

You receive a PDF: the table, annotated screenshots, competing explanations, and a short test list. We do not bury a “north star” slide in the appendix.

Day 10 — Readout

Ninety minutes at Level 7 or on a call. Owners of the leaking screen should be in the room. After that, the engagement is done unless you book a drop-off session or a later check-in.

What this method refuses

We will not average iOS and Android when the screens differ. We will not call a tracker migration “out of scope” and then silently skip broken names. We will not present the review as access to software.

When you are ready for a start week, ask about an engagement.