Google Analytics Dashboard Design for a Small Team
Choose the few numbers that guide decisions.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Design a dashboard from Google Analytics data. Team decisions informed by the data: [DECISIONS]. Metrics available: [METRICS]. Review rhythm: [RHYTHM]. Work backwards from the decisions to choose no more than eight metrics; a metric with no decision attached is removed. For each give a definition, the comparison, a plain reading rule (what up and down mean), a threshold for attention as a placeholder, the action if it moves, and one chart idea with a table fallback. Describe the layout as a grid with the most important number top left. Provide a five-minute weekly review script with three questions: what moved most, is it expected, and does anything need action. Note data limits: consent can reduce counts, data can take a day to settle, and small sites have noisy numbers [VERIFY]. Tell me which three metrics to build first if time is short, and which to drop if the team does not use the dashboard after a month. Write the reading rules in words a non-analyst can follow, and say who owns the dashboard and who updates the thresholds.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Invented eight metrics with reading rules. Sessions (13,800 this week, up 4 percent), engagement rate (61 percent), conversions (400), conversion rate (2.9 percent), top landing page, top channel, new versus returning, and form errors. Threshold examples to confirm: conversion rate below 2.5 percent is flagged. Review script, 5 minutes: what moved most, is it expected, anything needing action. Example outcome: conversions up 8 percent, caused by the email campaign, no action; form errors up from 3 to 14, action: ask the web developer to check the form.
Illustrative only, made-up data. Your results will differ and must be reviewed.