Monitor real-time active users

Monitor real-time active users in Google Analytics — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
We need a real-time dashboard for active users for the product launch so support can spot spikes.…
We need a real-time dashboard for active users for the product launch so support can spot spikes. Ask Laila in support and Vince in product to confirm which regions and events to show, set the alert threshold to 200% above baseline, and verify mobile versus web counts before I publish the dashboard for the Friday launch.

Improve — make it easier to accept

+
Before I publish the live active-users feed, make it easy for product and support to approve: put…
Before I publish the live active-users feed, make it easy for product and support to approve: put current active-user count and a one-hour trend at the top, surface the top three pages where users are concentrated, and flag what would trigger paging support so Vince knows when to call a war room.

Decide — diagnose the stuck moment

+
The real-time active-users card dropped to zero while our backend logs show normal traffic. I fear…

the live active users panel shows zero despite traffic

The real-time active-users card dropped to zero while our backend logs show normal traffic. I fear the tracking snippet failed to load or a property filter is excluding events, and I can't tell which without deeper access. What is the most likely diagnosis and the immediate two checks I should run so support can trust the dashboard for the launch?

Become — change the pattern

+
Support keeps ignoring the real-time dashboard because it has been noisy or inaccurate during prior…

support ignores the real-time dashboard

Support keeps ignoring the real-time dashboard because it has been noisy or inaccurate during prior launches and they prefer server logs. Where is credibility being lost—what repeat configuration or alerting choice causes mistrust—and what one change will make product and support rely on the dashboard for the next launch?

Next to this one

Other web analytics work people do in Google Analytics.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.