Know who came to your site, where from and what they did, without opening GA4.
The Analytics view reads your Google Analytics 4 property and puts the four answers on one screen: how many people came, where they came from, what they read and what they did, for any range you pick. Every number carries its window, its source and its age.
Is my website traffic going up?
Open the Analytics view and the first card answers it. It shows sessions for the window, the change against the period before, and the trend drawn underneath. The window is printed on the card. Click it and the drill-down shows the latest figure, the change, and the source, named as GA4. On the Overview, the same 30-day sessions figure is a headline card with its daily trend.
Pick the range you want to read. The picker offers the last 7, 30 and 90 days, the last 6 and 12 months, or a custom start and end, and compares any of them with the previous period or the same period last year. The default is the last 30 days. Each read is a live request to your GA4 property for that window. The chart is bucketed by day for spans up to about three months, by week up to about a year, and by month beyond that, so a two-year series reads as a trend instead of 730 daily points.
Every preset ends yesterday. Today is partial in GA4, and a half day at the right edge of a chart reads as a collapse, so the picker leaves it out. A window you have already asked for is held for five minutes, so clicking between 30 days and 90 days and back costs one GA4 read, not three. Export the view and the CSV holds what is on the screen for the range you picked, not a default window.
Where did they come from, and what did they read?
Traffic by channel splits sessions the way GA4 groups them: organic search, paid search, direct, referral and organic social, each with its share of the total. Under it, source / medium lists up to twelve rows, so google / organic and google / cpc are separate lines and a referral from one site has its own row. A devices table splits the same sessions by mobile, desktop and tablet.
Top pages ranks the pages people read by views, with the average time beside each, and a click on a row opens the page detail. Read the two cards together. A service page that draws its views from organic search and holds a reader for three minutes is doing its job. A blog post that draws views from social and loses them in twenty seconds is a post, not a lead source. This is the card that says which is which.
The demo shows the shape with illustrative numbers. Its Analytics view reads 1,740 sessions in the latest month, up 7 percent on the month before. Organic search carries 38 percent of traffic, AI referrals 16 percent and direct 15 percent. The top page holds readers for 3 minutes 12 seconds, and 84 demo requests were counted in the last 30 days. Your instance shows your property; the demo is the one place the figures are invented, and it says so.
What did they do, and can I trust the count?
The conversions card counts each key event over the last 30 days: form submissions, call taps, chat starts, quote requests, whatever your property is set to record. Click an event and the drill-down shows its 30-day count and any note attached to it.
On a dashboard with a live Leads feed, lead actions lead the page. The conversions tile comes first, the chart opens on lead actions, and the first table lists each event under a plain label instead of its snake_case name. Traffic is the supporting cast, because traffic only matters when it turns into a request, and the layout says so.
A key event is what a tag counted. It is not a lead. Your lead sheet, written server-side by your form handler the moment a form is submitted, is the record, and the Leads view reads it. On an instance whose forms feed that sheet, a watch runs every morning at 7:20 Eastern with five checks, and one of them is exactly this case: leads in the sheet and zero form events in GA4, so the site tag is dead. It exists because of one account, anonymised, where a tag change stopped every conversion for six weeks, 21 real leads landed while Google Ads reported zero, and the owner paused the campaign that carried every counted lead and cut its budget by 90 percent.
Where conversion tracking was rebuilt on a property, for example an older setup that counted page taps and map clicks as conversions, the figures from before that date are excluded rather than shown wrong. The tile reads not tracked in this era, a note on the page says when and why, and sessions and users stay comparable across the whole range.
Why is GA4 hours behind when my CRM is live?
Because Google publishes GA4 intraday data on its own schedule, hours after the fact, and no dashboard can read what Google has not released. The page states the ceiling per source instead of labelling everything live. Your CRM, Stripe, your booking platform, website leads and email stats are live, and a refresh moves them. Google Ads lags a few hours. GA4 intraday lags hours. Search Console releases each day two to three days later.
Here is what happens when you open the page. Last night's snapshot renders first, so there is something to read before any network call returns. The live payload comes from cache at once. If that snapshot is older than five minutes, a pull runs behind the request and the tiles update when it lands. The header stamp says how old the data is, and its hover text says which case you are in: pulled live when you opened the page, or the last saved snapshot because the live refresh was unreachable. Press Refresh and a pull of two seconds to a little over three minutes starts; the page reloads when the stamp moves, and it never shows an error.
Two things run on a schedule whether anyone is at a desk. At 12:01am Central, one job rebuilds the fallback snapshot for every client, and a pull that fails or a file that fails its syntax check leaves the previous page up, so nothing empty or broken ships. At 7:20am Eastern, the lead watch runs where it is set up. Two things stay with a person. Which events count as key events is set in your own GA4 admin. A change you request from the screen, to content, keywords or targeting, goes to the team and is logged; nothing on the screen writes to GA4.
Is Search Console on this view too?
No, on purpose. Search Console sits on the search visibility view with queries, impressions, clicks and average position, and Google AI Overviews are measured there as well. Analytics is the on-site half: what happened after the click. Search visibility is the off-site half: what happened before it. Keeping them on separate views keeps two different Google systems from being read as one number.
Both are read from Google and both print their lag. GA4 runs hours behind. Search Console runs two to three days behind, so the search view carries a note beside its chart: the empty right edge is Google's publishing delay, not a drop in search traffic.
How do I connect it, and what should I check in the demo?
Add our Google account as a manager on the property, from access management in your own GA4 admin. That is the whole connection. There is no wizard, no password held on our side and no client-side sign-in. You grant the access in week one of setup, and you can revoke it in the same screen at any time. Setup takes two to four weeks and is not billed.
On our side the property is saved once in your account's connection map, and every request the dashboard makes uses that saved property; the browser never sends a property id. Revoke the access and the view says so: an unavailable card replaces the live read, and the nightly bake leaves the last good page up.
Check it in the demo before you buy. Open demo.trulata.com, go to Analytics and click the sessions card: the drill-down shows this month's figure, the change on the month before, and names GA4 as the source. Click a traffic source for its share, a page for its detail, and a conversion tile for its 30-day count. The demo is the fictional company Meridian on the same engine code every client runs, with no form in front of it. The date picker is switched on per instance during setup, so the demo shows the twelve-month view.
What the analytics view reads.
| What | Where it comes from | How fresh |
|---|---|---|
| Sessions, users, new users, pageviews, bounce rate, average session duration | GA4 Data API, your property | Hours behind intraday, set by Google |
| Traffic by channel, source / medium, device | GA4 Data API | Hours behind |
| Top pages, views and average time | GA4 Data API | Hours behind |
| Key events, by name and count | GA4 Data API, last 30 days by default | Hours behind |
| Date ranges | 7, 30, 90 days, 6 or 12 months, custom, with a comparison | Held five minutes per window |
| Form leads, the record | Your lead sheet, on the Leads view | Live |
| Writes to GA4 | None | Never |
A key event is what a tag counted and your lead sheet is what a form recorded, so on an instance whose forms feed the sheet the two are compared every morning at 7:20 Eastern.
Questions, answered.
Is GA4 data live in the Command Center?
No, and it is not live inside GA4 either. Google publishes intraday data hours behind. The view shows the newest point Google has released and the header stamp says how old it is.
Do I still need to log in to GA4?
Not for sessions, sources, pages and key events, for any range you pick. GA4 stays yours for deeper exploration, and our manager access changes nothing in it.
What counts as a conversion?
Whatever key events your GA4 property is set to record: form submissions, call taps, chat starts, quote requests. On a dashboard with a live Leads feed they are labelled lead actions with plain names.
Why compare GA4 with my lead sheet?
Because a tag that stops firing makes GA4 report zero while leads keep landing. On an instance whose forms feed the sheet, the watch runs at 7:20am Eastern every day and raises it the first morning.
Can I pick my own date range?
Yes. The last 7, 30 or 90 days, the last 6 or 12 months, or a custom start and end, compared with the previous period or the same period last year. Every preset ends yesterday, because today is partial in GA4.
Can the product change my GA4 settings?
No. It reads the property through manager access you grant and never writes to it. Key events are configured in your own GA4 admin.
Where is Search Console?
On the search visibility view, with queries, impressions, clicks and average position, two to three days behind on Google's schedule.
Which tier includes the analytics view?
The Command Center and full analytics are on all tiers. Prices and seats are on the pricing page.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.