In brief: Google Analytics holds dozens of reports. Five cover almost every question a small business has: Traffic acquisition, Landing page, Pages and screens, Events and Queries. They sit under Acquisition, Engagement and Search Console in the left menu. The two acquisition reports count the same visit in different ways, and Google says plainly that their figures should not be compared.
Most owners open Google Analytics once. They see a left menu full of words no one taught them, poke at two, and close the tab. The tracking code keeps saving data that no one ever reads.
Five Google Analytics reports cover almost every question a small business has. All of this is Google Analytics 4, the version everyone calls GA4. The five sit in three menus. You can read all five over a cup of tea on the first Monday of the month.
This guide names those five, shows where each one lives, and tells you what to read in each.
Key Takeaways
- Five reports answer the real questions: where visits came from, where they landed, what got read, what people did, and what they typed into Google.
- A session counts as engaged only if it runs past 10 seconds, fires a key event, or reaches two page views.
- Search Console data reaches Analytics 48 hours after it is collected, and the whole Search Console section stays hidden until you publish it.
- Google says plainly that you should not compare figures across the two acquisition reports.
Which Google Analytics Reports Should You Actually Open?
Five of them, sitting in three menus. Traffic acquisition tells you where a visit came from. The Landing page report tells you which page it started on. Pages and screens shows what got read after that. Events shows what people did. Queries shows the searches your site turned up in.
The first four work the moment your tracking code is live. The fifth needs ten minutes of setup, which is why it comes last here. Most of the rest goes deeper on the same ground, or is built for shops and apps. Read these five and you will know what your website is actually doing. If you want the money side of the picture as well, we covered that in how to measure digital marketing ROI.
Report One: Where Did the Visit Come From?
Open Reports, then Acquisition, then Traffic acquisition. Google calls it a report “designed to help you understand where your website and app visitors are coming from” (Traffic acquisition report). Each row is a channel, with the sessions it sent beside it.
The channel names come from Google, and the default ones cannot be edited. They include Direct, Organic Search, Paid Social, Organic Social and Email (default channel group). Direct is the row that trips people up. Google defines it as the channel where people arrive “via a saved link or by entering your URL”. It also collects visits that turn up carrying no source information at all.
That happens more than people expect. A skincare clinic in Satellite sends a WhatsApp broadcast with a plain link. Those visits land under Direct, because the link carried no UTM tags. The campaign worked, and the report cannot see it.
Read two things here: which channels sent the most sessions, and the Key events column beside them. That column sits at zero until you mark a key event, which is report four’s job. Once it fills, a channel with plenty of visits and no key events is just noise. If your strongest channel turns out to be Google Maps, your Business Profile is doing the heavy lifting, and it deserves the attention.
Report Two: Which Page Did People Land On First?
Reports, then Engagement, then Landing page. Google says it “shows you the first page a visitor lands on when they visit your website” (Landing page report). Each row is the page path of the first pageview in a session. Beside it sit sessions, active users, average engagement time per session and key events.
Owners assume the home page is the front door. Across the accounts we look after in Ahmedabad, this is the report that changes minds fastest. Open it and the top row is often a blog post from two years ago. A furniture showroom on S.G. Highway may find its best front door is a post about sofa fabric. That one fact changes where you spend your next hour.
The column to read is average engagement time per session, next to the session count. A page that pulls in visits with a few seconds of engagement promised something the page never gave.
Read it the lazy way. Sort by sessions, then run your eye down the list until you reach a page you did not expect. That page is doing work nobody planned for. Send it the attention you were about to spend on the home page. Our guide to landing pages that convert in India covers what to put on it.
Report Three: What Did People Read After That?
Same menu again: Reports, then Engagement, then Pages and screens. It covers every page anyone saw, at any point in the visit. Google draws the line between this report and the last one. Pages and screens shows pages “whether that’s the first page or a page later in their session”.
If you want the first page instead, Google says to “use the Landing page report” (Pages and screens report). So Landing page judges your front doors, and this one judges the rooms behind them.
Views counts repeated views of the same page. Average engagement time is the total time your site was in focus, divided by the number of active users.
One thing earns your attention: pages that hold people for a decent stretch and sit nowhere in your menu. People are hunting for those. Put them one click from the home page, and the job is done.
When a page keeps showing up and you cannot tell why, build a path exploration. Google lets you set either a starting point or an ending point, though not both at once (path exploration). Pick your page, and the chart shows what people did next, or what they did just before.
Report Four: Did Anyone Do the Thing You Wanted?
Reports, then Engagement, then Events. It “shows how many times each event is triggered and how many users trigger each event on your website or app” (Events report). Straight out of the box you get rows like page_view, scroll, click and session_start. None of those is a sale.
The fix takes a minute. Find the event that matters, click the icon at the right of its row, and select Mark as key event. Google defines a key event as “an event that measures an action that’s particularly important to the success of your business” (about key events). Once marked, a Key events column turns up in many of the other reports, the Landing page report included. That is what turns a traffic report into a lead report.
Two warnings before you trust this screen. Event data can take up to 24 hours to appear here, so an hour after a launch this report proves nothing. Realtime is the place to look that day. And a tap on your phone number can be counted, while the call that follows cannot. That gap is why the sales figure at month end never quite matches this screen.
Report Five: The Words People Type Into Google
This one is missing from most accounts, and hidden in the rest. Two setup steps come first, and both need the right access. Search Console has to be linked to the property, which needs the Editor role in Analytics and verified ownership in Search Console (connect Search Console).
Then you switch the section on. The Search Console collection “is unpublished by default”, and you publish it from Library in the left menu (Queries report).
After that it sits at Reports, then Search Console, then Queries. Each row is a search your site turned up in, with the clicks, impressions and average position beside it. Three limits are worth knowing. Search Console keeps 16 months of data, so Analytics can show no more than 16 months. Data arrives 48 hours after Search Console collects it. And the history begins at your Search Console verification, or at the day the data stream was made, whichever came later.
Some rows go missing too. Google applies data thresholds to stop anyone working out who an individual user is (about data thresholds). Where a report includes search query information, “the row containing that data may be withheld if there aren’t enough total users”. A wider date range may bring them back. The queries here are the honest starting point for keyword research, because Google already shows your site for them.
Why Do Two Google Analytics Reports Count the Same Visit Differently?
This one is about a sixth report, User acquisition, sitting in the same menu as the first of the five. The two count different things, and Google says so in writing. One follows people, the other follows visits. That is how two reports can show different totals for the same week.
Google puts it plainly. “The User acquisition report is scoped to new users, while the Traffic acquisition report is scoped to new sessions” (user acquisition against traffic acquisition).
Its help page then works through an example that makes the split obvious. Somebody finds your site through Google. Then they come back ten more times by typing the address. User acquisition files all 11 sessions under Google, because Google introduced that person. Traffic acquisition splits them. The key event lookback window decides how, and it runs 90 days by default. If those later visits fall outside it, the report files 1 session under Google and 10 under (direct). Inside that window, all 11 stay under Google.
Both reports are right, and they answer different questions. Google’s instruction is blunt: “you should not compare the metric values across the reports.” The scopes differ, so the numbers differ. Use User acquisition to judge how new people find you. Use Traffic acquisition to judge how the ones you have keep coming back.
What Should You Check Before You Trust a Number?
Four things worth knowing before you act on any of these numbers. Match the date range and check how the channels are defined. Allow for the thresholds GA4 applies to small audiences, and remember that Search Console counts impressions of a page.
Match the date range. Compare a full month with a full month. A Navratri week will beat the week after it in any Gujarat business, and that tells you about the calendar.
Know what engaged means. Google sets a low bar. A session counts as engaged if it “lasts longer than 10 seconds” (engagement rate). Two page views or one key event also count. Bounce rate is the share of sessions that were not engaged.
Ignore the retention scare. People panic about the 2 month and 14 month settings for user-level data (data retention). Google says that setting “does not affect standard aggregated reports”. It only touches explorations and funnel reports, so the five above keep working. The path exploration earlier in this guide is the one place it bites.
Expect gaps. Thresholds can hide rows in the Queries report, and untagged links pile up under Direct. Reading any report as gospel is one of the quieter digital marketing mistakes we see.
Where to Start This Month
Block twenty minutes on the first Monday of next month. Open the five reports in the order above. Write down five lines: your top channel, your top landing page, the page holding attention longest, your key event count, and your top query. That is your baseline.
Do the same a month later. The numbers on their own mean little, and the movement between them tells you almost everything. If you would like someone else to read them and act on them, that is what our performance marketing team does each month.
Frequently Asked Questions
Why can I not see bounce rate anywhere?
It is off by default. Google notes that “by default, most reports in Google Analytics do not include the engagement rate and bounce rate metrics”. An Editor or Administrator adds them to a detail report. Engagement rate is the more useful of the two anyway, since bounce rate is only its mirror image.
My WhatsApp enquiries never show up. Is something broken?
Nothing is broken. Analytics sees what happens on your website. A tap that opens WhatsApp can be logged as an event, and the chat that follows cannot. Mark that tap as a key event, then count the real enquiries in WhatsApp Business and compare the two numbers each month.
How often should I open these reports?
Once a month for the full set. Daily checking creates noise, because one day rarely carries enough sessions to mean anything. The exception is a launch week, when the Realtime report answers one narrow question: is the tracking firing at all?
Why is the Queries report empty?
Three usual causes. Search Console may not be linked to the property yet. The collection may still sit unpublished in the Library. Or it is simply too new. Data appears 48 hours after Search Console collects it, and the history never reaches back past your verification date.
