How to Hide Revenue & Traffic Numbers in Google Analytics (GA4) When Presenting
Presenting a GA4 report to a client or the wider team? Here's how to blur revenue, conversions, real-time users, the property name and user emails — and why you should re-check your blurs after every date-range change.
To present a Google Analytics (GA4) report without exposing revenue, conversions or the client's property name, blur those specific cards and columns in the page before you share your screen — and re-check them after you change the date range, because GA4 rebuilds the whole report each time. BlurFirst paints the blur in as real pixels, so it survives Zoom, Meet, Teams, Loom and OBS, and every figure stays inside your browser.
This is the common case for agencies and in-house teams: you want to show the *trend* — traffic is up, conversions are climbing — without handing the room the absolute revenue numbers or the name of another client's property. Start blurring with Ctrl/⌘ ⇧ Y and keep Ctrl/⌘ ⇧ H ready to blur everything in a pinch.
What's sensitive in a GA4 report
- Revenue and conversion values — purchase revenue, ARPU and conversion rates in the Monetization and Reports scorecards.
- Total users and real-time users — the big scorecards and the Realtime overview counters that keep ticking as people arrive on the site.
- The account and property name — the property switcher at the top-left names the client or brand, and the account name above it can name others.
- Linked Google Ads figures — the Advertising and Acquisition areas can surface ad spend, CPC and ROAS you don't want disclosed.
- User IDs and emails in the User Explorer report — this report lists individual identifiers, and if you feed in user-provided data, those can be emails.
- Comparison segments — added comparisons and audiences can name other properties or customer cohorts in the chips at the top.
How to blur GA4 before you present
- 1
Open the exact report and date range
Get to the report you'll present with the dates already set, so the layout is settled before you start blurring.
- 2
Box-blur the property switcher and top nav
Drag a BlurFirst box over the property/account switcher at the top-left so the client or brand name never shows.
- 3
Blur the scorecards and revenue columns
Element-blur or box-blur the KPI scorecards, the revenue column in a table, and the Realtime counters — leave the trend chart visible so you can still tell the story.
- 4
Re-apply after changing the date range
GA4 re-renders the whole report when you change dates, add a comparison or switch reports. Re-check your blurs, or use a saved profile so they come back automatically.
- 5
Keep panic ready
If you land on the User Explorer report or a comparison surfaces a name, press Ctrl/⌘ ⇧ H to blur the entire page instantly.
| Sensitive item | Where it appears | Best gesture |
|---|---|---|
| Property / account name | Top-left switcher | Box-blur the switcher |
| Revenue / conversion value | Scorecards and table columns | Box-blur the card or column |
| Real-time users | Realtime overview counters | Box over the counters (covers ticking values) |
| Google Ads spend / ROAS | Advertising & Acquisition | Element or box blur on the metric |
| User IDs / emails | User Explorer report | Box-blur the identifier column |
Reports re-render when you change the date range
Every time you adjust the date range, add a comparison, or switch to another report, GA4 rebuilds its tables and cards. That can clear a blur pinned to one specific element, because the element it was attached to has been redrawn. Region (box) blurs pinned to a screen area survive this best, since they keep covering whatever renders underneath. If you present GA often, BlurFirst Pro's per-site auto-apply re-applies your saved boxes automatically on analytics.google.com — so your scorecard and property-name covers come straight back after a date change.
Why GA4's user roles don't solve this
GA4 roles — Viewer, Analyst, Editor, Administrator — control who can open the property. When you present, the account opening it is *yours*, with full access, so role restrictions do nothing about the revenue figure on your screen. Roles and in-page blurring solve different problems: roles govern access, blurring governs what the audience watching your screen can read during a live share.