TruLata now connects to Google Analytics 4, so you can see where your visitors come from and what they do, next to the leads that actually landed. Sessions, sources, pages and key events sit beside your leads and your revenue on one screen, and the header stamp says how old the data is.
For an owner, that means one place to answer the four questions you ask of analytics: how many people came, where from, what they read and what they did. It also means your GA4 conversions and your real leads stay two separate counts, on purpose, so a dead tag does not talk you into cutting the campaign that carried the leads.
What TruLata reads from Google Analytics 4
Every number is a report request against the GA4 Data API on the property you connected. The full GA4 integration page has the complete spec. In short:
- Six totals for any window: sessions, users, new users, pageviews, bounce rate and average session duration.
- Sessions by default channel group and by source and medium.
- Top pages, ranked by views.
- Key events, GA4's name for conversions, by name and count.
- A day-by-day series of sessions, users and pageviews for the trend chart.
- Sessions by device and engaged sessions.
The numbers land in two places. The Overview carries the headline cards, and the Analytics view is the full read. You can pick the last 7, 30 or 90 days, the last 6 or 12 months, or a custom start and end, then add a comparison window. Every preset ends yesterday, because GA4 lags hours intraday. If your site moved to a new GA4 property, TruLata reads a range that spans the move from both properties, stitched.
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. Where the watch is set up on your forms, it compares the two every morning at 7:20 Eastern, so a silent tag shows up the next morning rather than at the end of the quarter. Calls get the same treatment: the CallRail integration puts every tracked call on your Leads tab.
How to connect
Add our Google account to the property from access management in your own GA4 admin. That is the whole connection. You never hand over a password, and our team does the linking from the inside. On our side the property is saved once in your account's connection map, so the property id stays on our side and out of the browser.
To take it back, revoke the invitation in the same screen you granted it in. The live read then fails cleanly: the view shows an unavailable card and the nightly bake leaves the last good page up.
What stays in Google Analytics 4
Every click on the screen reads from GA4. The write paths from TruLata are a question to the team, a lead outcome, a website change request and a content or targeting request, each logged. A change to your GA4 setup, where your engagement asks for one, is made by our team with the access you granted and shows in your GA4 admin's change history.
On freshness, GA4 numbers run hours behind intraday, and that ceiling is Google's. Press Refresh and a pull of two seconds to a little over three minutes starts, and the page reloads when the stamp moves.
Who it fits
It fits service businesses that run a GA4 property and want traffic read against the leads that actually came in, not on its own. If you also send email campaigns, the ActiveCampaign integration reads your campaign statistics live on the same dashboard. You can see everything else that connects in the TruLata integrations directory.
If you want to see traffic and leads side by side before you connect anything, book a TruLata demo and we will walk you through the Overview and the Analytics view.

™



