Analytics

Reveal reports on four things: how often a guide was shown, how often someone started it, how far they got, and how they felt about it. Each of those answers a different question, and each one points at a different fix.

The numbers live in two places. The Dashboard gives you the state of the whole workspace. A guide's Overview tab gives you the detail on one guide.

Note. Guides only collect analytics once they're published. A draft can be recorded, previewed, and configured, but it never runs on your site, so it never reports. The guide card says as much: "Finish & publish to collect analytics."

The dashboard

The dashboard is a 30 second page. Glance, spot something, click in. It isn't built to be studied.

It opens with a time-of-day greeting and a one-line summary of the shape of your workspace, along the lines of "N guides gained traction in the last 14 days. N guides need attention." Under that sits a date range selector, defaulting to Last 14 days, plus a New guide button and the notification bell.

The four KPI cards run across the top: IMPRESSIONS, GUIDE STARTS, COMPLETION RATE, and AVG. RATING. Each shows a delta against the previous period, so you're reading the direction as much as the value.

Top performer and Needs attention sit side by side below. Each spotlight shows COMPLETION, STARTS or DROP-OFF, VS LAST WK, and a small STEP FUNNEL strip, so you can see the shape of a guide without opening it. Before you have traffic they read "Waiting for traffic. Publish a guide to see your top performer." and "Nothing to flag. No underperforming guides."

Recent guides is a table with GUIDE, STEPS, IMPRESSIONS, COMPLETION, RATING, and UPDATED, plus New guide and All guides buttons. It's the fastest way to compare guides against each other.

Latest feedback runs down the right, described as "From users who finished a guide." It's the one panel on the page that tells you something a number can't.

The guide Overview tab

Open any guide and you land on Overview. This is where you go once the dashboard has pointed you at something.

Five KPI cards across the top: IMPRESSIONS, STARTS, COMPLETION, AVG. WATCH / STEP, and AVG. RATING.

Step funnel, labelled "% of users reaching each step", with its own range selector defaulting to Last 30 days. A longer window than the dashboard, because a funnel needs more traffic before its shape means anything. Before you have data it reads "No steps recorded yet. Record this guide to see funnel data." Reading the funnel covers it in detail.

Steps lists what the guide actually does, with the reminder that "Edits happen in the Chrome extension, click Open in Editor to jump to a step." Read this alongside the funnel, because the funnel tells you which step and the step list tells you what's in it.

Rating breakdown gives you a row per reaction: Love, Happy, Neutral, Sad.

Latest feedback at the bottom, with a View all link, showing comments left on this guide specifically.

What each number means

Impressions

The number of times the guide was eligible and shown to a user. This is a measure of your trigger and audience settings, nothing else.

Low impressions on a published guide usually means the pixel isn't seeing traffic on the right domain, or the audience is narrower than you thought. Check the Issues tab first.

Starts

The number of times a user actually began the guide. The gap between impressions and starts is the most diagnostic number in Reveal.

High impressions with low starts means the trigger is wrong. The guide is appearing, and people are declining it. Try After a delay, narrow the audience, or move it to Manual only so people come to it.

Completion

The percentage of users who started the guide and reached the end.

High starts with low completion means the content is wrong. People wanted what you offered and gave up part way through. Open the step funnel to find out where, then shorten, re-record, or split the step they quit on.

Avg. watch / step

The average time users spend on a step before moving on. It tells you whether people are watching your clips or clicking past them.

Avg. rating

The average of the reactions users left on the feedback screen, and the only number here that reports how the guide felt rather than what people did. A guide can complete well and still be rated poorly, which usually means it worked but took too long. Ratings and feedback goes into this.

Heads up. Be careful with AVG. WATCH / STEP. A short watch time is not automatically bad. A confident three second "click the blue button here" clip should have a short watch time, because it did its job quickly. Read it alongside completion: short watch with high completion means your steps are tight, short watch with low completion means people are skipping ahead and giving up. The number on its own tells you very little.

A routine that works

Open the dashboard once a week. Read the summary line, look at whether the four KPIs moved up or down, then open whatever sits in Needs attention. On that guide's Overview, find the cliff in the funnel, read the latest feedback, fix one thing, and close the tab.

Fixing one step a week compounds. Rebuilding a guide from scratch because a number looked bad usually doesn't.

Next steps

• The step funnel: Find the step where people leave.

• Ratings and feedback: What users thought, in their own words.

• Triggers: The fix when impressions are high and starts are low.

• Publish a guide: Analytics start once a guide is live.