What it is.
Five steps in order. First configure event capture, so the events you care about are named deliberately, then build one dashboard instead of browsing insights. Invite the team, because analytics one person reads is a hobby.
Then set up subscriptions so important dashboards, events, and actions get delivered on a schedule instead of waiting to be opened. Last, start an experiment, since that is what the data was collected for.
The order matters. Teams that skip event configuration end up with autocaptured clicks nobody can name, and teams that skip subscriptions build a dashboard nobody opens twice.
What you get.
- A deliberate event set, named by you instead of inherited from autocapture.
- One dashboard covering the questions you ask weekly.
- The team invited, so more than one person can answer a question.
- Scheduled subscriptions delivering dashboards and events to inboxes.
- A first experiment, so the data changes a decision.
How to set it up.
Configure event capture before anything else, and name events for what happened instead of for the element clicked.
Build one dashboard that answers the three questions you get asked weekly.
Invite the people who ask those questions, since a locked-down install stays unused.
Create subscriptions on that dashboard so it arrives on a schedule.
Add subscriptions on the two or three events where a spike or a stall matters.
Set up one experiment, even a small one, so the install starts paying for itself.
Use cases
Go past the snippet
Work the five steps so the install produces answers.
Name your own events
Define the set deliberately instead of inheriting whatever autocapture found.
One dashboard that gets opened
Build the view around the questions people ask.
Best for
An install nobody uses
The snippet is the easy part. These five steps are what makes anyone open it.
A new analytics owner
Inheriting an install with no naming convention starts with step one.
Small teams
One dashboard and a subscription beats a warehouse project you will not finish.