Know who came to your site, where from and what they did, beside the leads that actually landed.
Grant manager access on your Google Analytics 4 property and the Command Center puts sessions, sources, pages and key events next to your leads and your revenue. The header stamp says how old every number is, and this page lists exactly what it reads and where each number lands.
What will I see from my GA4 property?
Six totals for the window: sessions, users, new users, pageviews, bounce rate and average session duration. Sessions break down two ways, by default channel group and by source and medium. Pages rank by views. Key events, which is what GA4 reports as conversions, arrive by name and count. A day-by-day series of sessions, users and pageviews draws the trend chart. Every read is a report request against the GA4 Data API on the property you connected.
Sessions by device category and engaged sessions feed the devices and engagement tables. Together, the view answers the four questions you actually ask of analytics: how many people came, where from, what they read, and what they did.
Where will I find the numbers?
Two places. The Overview carries the headline cards, and on a lead-generation dashboard two of them come from GA4: website sessions over the trailing thirty days with the daily trend, and tracked lead actions, the key events your site fires for a call tap, a form or a chat. Where your funnel starts at traffic, that same sessions figure is its top stage.
The Analytics view is the full read: a sessions card with trend and change, traffic by channel, top pages with views and average time, and the key events table. On a dashboard with a live Leads feed, that table leads the page as lead actions, each event given a plain label instead of its snake_case name.
Can I pick my own dates and compare them?
Yes. Pick the last 7, 30 or 90 days, the last 6 or 12 months, or type a custom start and end, and add a comparison window. Each read is a live GA4 request for the window you chose, bucketed by day, week or month to suit the span. The comparison prints the change on the headline totals and the prior value beside each engagement measure. A window you have already asked for is held for five minutes.
Every preset ends yesterday. GA4 lags hours intraday, so the presets leave today out on purpose; a custom range takes the dates you type. If your site moved to a new GA4 property, the history stayed behind, so we record which property holds which dates and read a range that spans the move from both properties, stitched. An era whose conversions are known to be wrong, say a property that counted page taps, has those conversions excluded rather than footnoted.
Are GA4 conversions the same as my leads?
No, and the product keeps them apart on purpose. A key event is what a tag on your site counted. A lead is what your form handler wrote server-side into the lead sheet the moment the form was submitted, and that keeps working when every tag on the page is dead. The Leads view reads the sheet; the Analytics view reads GA4. Where we have set the watch up on your forms, it runs every morning at 7:20 Eastern with five checks, and one of them is exactly this: leads landed in the sheet while GA4 recorded zero form events, so the site tag is dead. The glossary entry on key events covers the vocabulary.
One incident, anonymised, is why. A tag change stopped the site's Google tag loading, so for six weeks nothing fired: GA4 recorded no form events and Ads reported zero conversions while 21 real leads landed in the sheet. The owner read those numbers, paused the campaign carrying every counted lead and cut its budget 90 percent. A daily comparison makes that failure loud on the first morning. The Leads view holds the ground truth; this use case is why the two counts sit side by side.
How do I connect it, and how do I take it back?
Add our Google account as a manager on the property, from access management in your own GA4 admin. That is the whole connection. We never hold your password, there is no wizard, and you revoke the invitation in the same screen you granted it in. Access is week one of setup.
On our side the property is saved once in your account's connection map. Every GA4 request the dashboard makes uses that saved property; the browser never sends a property id. Nothing on the screen writes to GA4. The complete list of write paths from the Command Center is a question to the team, a lead outcome, a website change request and a content or targeting request, and none of them touches Analytics. Revoke the access and the live read fails cleanly: the view shows an unavailable card and the nightly bake leaves the last good page up.
How fresh are the GA4 numbers?
Hours behind intraday, and that ceiling is Google's. Your CRM, Stripe, the lead sheet and email statistics are live on the same dashboard; Google Ads runs a few hours behind and Search Console two to three days. The page loads last night's snapshot first, so it is never blank, fetches the live payload from a cache at once, and runs a pull behind the request if the snapshot is older than five minutes. Press Refresh and a pull of two seconds to a little over three minutes starts; the page reloads when the stamp moves.
The header stamp says how old the data is. Every path through Refresh ends in a reloaded page; it never shows an error. If a live read fails on a range you picked, the view shows an unavailable card rather than quietly swapping back to the baked numbers. The nightly bake at 12:01am Central is the fallback: a pull that fails or a file that fails its syntax check leaves the previous page up. What live means per source has its own page.
What the GA4 integration reads, and how fresh each read is.
| What | Where it comes from | How fresh |
|---|---|---|
| Sessions, users, new users, pageviews, bounce rate, average session duration | GA4 Data API, the connected property | Hours behind intraday, set by Google |
| Traffic by channel and by source / medium | GA4 Data API | Hours behind |
| Top pages, by views | GA4 Data API | Hours behind |
| Key events, by event name and count | GA4 Data API | Hours behind |
| Daily trend of sessions, users and pageviews | GA4 Data API | Hours behind |
| Sessions by device, engaged sessions | GA4 Data API | Hours behind |
| Lead comparison | Your lead sheet against GA4 form events | Daily at 7:20am Eastern, where the watch is set up |
| Writes to GA4 from the screen | None | Never |
The Command Center shows the tag's count and the sheet's record side by side, and where the watch is set up on your forms it compares them every morning at 7:20 Eastern, because the day they disagree is the day a budget gets cut on the wrong number.
Questions, answered.
Is GA4 data live in the Command Center?
No. Google publishes intraday data hours behind, inside GA4 too. The dashboard shows the newest point Google has released and the header stamp says how old it is.
What does the product count as a conversion?
The key events your GA4 property is configured to record: form submissions, call taps, chat starts, quote requests. On a lead-generation dashboard they appear as lead actions with plain labels.
Do I have to give you a password?
No. You add our Google account as a manager on the property in your own GA4 admin, and you remove it in the same screen whenever you choose.
Can the Command Center change my GA4 settings?
No. Nothing on the screen writes to GA4. The write paths from the dashboard are a question to the team, a lead outcome, a website change request and a content or targeting request, and none of them reaches Analytics.
My site moved to a new GA4 property. Do I lose the history?
No. We record which property holds which dates, and read a range that spans the move from both properties, stitched. Conversions from an era that counted the wrong thing are excluded rather than footnoted.
Which tier includes the analytics view?
The Command Center and full analytics are on all tiers, and search visibility, where Search Console sits, on all tiers. The figures 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.