Is Your GA4 Bounce Rate Too Low? How to Check Your Tracking

An unusually low bounce rate is worth questioning. It could be correct, but it could also mean GA4 is recording more activity than actually took place. Before treating a low figure as a win, check that the measurement is sound. 

How GA4 calculates bounce rate

Universal Analytics is no longer the reference point. Standard Universal Analytics properties stopped processing data in July 2023. GA4 uses an event-based model and calculates bounce rate in a different way.

GA4 calls a session engaged if at least one of these things happens:

• • The visitor stays for more than 10 seconds.

• • The visitor completes a key event.

• • The visitor views two or more pages or screens.

Bounce rate is the percentage of sessions that didn’t meet any of those conditions. Engagement rate is the percentage that did. You can read more about engagement and bounce rate on Google’s support page.

What bounce rate is likely to be correct?

A low GA4 bounce rate is not, by itself, evidence of good or bad tracking. Someone can spend 15 seconds reading a single vehicle page, leave without enquiring and still count as engaged.

There is no sensible site-wide target. A vehicle-detail page, a contact page and a buying guide each ask something different of the visitor. Compare like with like: similar pages, similar traffic sources and the same period of time.

Signs that the data may be wrong

If bounce rate drops sharply after a website release, a tag change, a consent-platform update or a change of marketing supplier, inspect the setup. The same applies when nearly every page and campaign suddenly shows unusually high engagement, but enquiries, calls and bookings have not changed.

A genuine improvement usually has supporting evidence. Visitors may spend more time on stock pages, view more vehicles or send more enquiries. A sudden site-wide drop towards zero, with no corresponding change in lead activity, points first to measurement.

The usual causes are duplicate page_view events and key events that fire too readily. Either can convert an ordinary visit into an engaged session.

Duplicate page views in GA4

On a normal website, the Google tag sends a page_view when a page loads. It can also send a page view when browser history changes. If a site also sends manual page views without turning off the automatic behaviour, GA4 can record the same visit twice. You can find more information on page views in Google’s developer documentation.

This issue often comes down to a simple overlap. The site has a Google tag in its code and a Google Tag Manager container sending data to the same GA4 property. A CMS plugin, agency or third-party tool has added another tag. Or a developer has added manual page-view tracking for a single-page application without changing GA4’s automatic settings.

Two page views are enough to qualify a session as engaged. If the second one is a duplicate, the bounce rate will be lower than it should be.

Test the tracking, not just the report

You should use one controlled visit from your own device. The aim is to see the event sequence for a normal page load, then find anything that fires twice without a customer action.

Check a standard page load

On a conventional automotive dealer website, one page load should normally create one page_view. You may also see automatically collected events such as session_start, first_visit or user_engagement.

GA4 collects several events by default, so an event list with more than one entry is not necessarily a problem. Google’s developer documentation provides more information on measuring events.

You're looking for a duplicate measurement event. If two page_view events appear for one page load, find out which tag or setting produced the second one.

Use Google Tag Manager Preview or Tag Assistant

For a site using Google Tag Manager, open Preview mode and visit the page you want to test. The debug panel lists data-layer events and shows which tags fired, which did not, and which values were passed to them. You can find out more about GTM debugging on Google’s support pages.

Check whether more than one Google tag is sending data to the same GA4 measurement ID. Look for a manual page_view tag firing alongside the automatic page view. It is also worth checking outside the container: the website template, CMS analytics settings and installed plugins are common places for a second tag to appear.

Your website may have legitimate advertising, consent and conversion tags. The issue is duplicate GA4 measurement, not the presence of third-party tags in general.

Confirm the sequence in GA4 DebugView

Tag Assistant can put your device into debug mode. In GA4, go to Admin and open DebugView. Use the site as a customer would and watch the events arrive from your test device. DebugView shows the event time and its associated parameters. More information on DebugView can be found on Google’s support pages.

Load a page and confirm that the expected page_view appears once. Move to another page and repeat the check. Test more than one page type, including the home page, a vehicle-detail page and a finance page.A busy Real-time report is not a reliable implementation test. DebugView and Tag Assistant show what your own visit did and why a tag fired.

Check what is marked as a key event

A key event needs to reflect a meaningful business action. For a dealer, that is likely to be a completed enquiry form, a booked test drive, an online reservation or a submitted finance application.

Don't promote every single interaction to a key event. A page load, image click or basic scroll does not usually mean a customer has become a lead. If an event runs on every page or has a trigger that is too broad, it will inflate engagement and suppress bounce rate without giving your sales team useful information.

Read the event name, trigger and conditions in Google Tag Manager. Then decide whether the action represents a genuine move towards a sale or service booking. If it does not, record it as an ordinary event rather than a key event.

Single-page applications need a separate check

A single-page application (SPA) can change its content and URL without loading a new document. If your website works this way, then you may need manual page-view tracking. In that case, you should configure the automatic page-view setting and browser-history measurement together, so GA4 doesn't double-count visits.

Agree on the expected event sequence before development starts. Test it before release and after any significant site changes.

Read engagement with the rest of the journey

Bounce rate tells you whether GA4 considered a session engaged. It doesn’t tell you whether the visit produced a useful outcome.

A vehicle-detail page with low bounce rate, solid engagement time and regular enquiries or ‘click-to-calls’ is probably doing its job. A paid campaign with a near-zero bounce rate but no calls, booking starts, finance starts, or enquiries needs more scrutiny.

Context of a visit

A buyer might land on the contact page, find the number and call without visiting another page. This is a good example of why a page’s purpose is significant context when looking at page metrics. This visit can still be valuable, even if it doesn't lead to an online form submission.

In contrast, a website visitor can spend more than 10 seconds with a buying guide and count as engaged without being ready to buy.

Review bounce rate and engagement rate by page type, source or medium, device and campaign. Put those figures next to vehicle views, form submissions, click-to-calls, and test-drive bookings. That gives you a better basis for changing content or ad spend.

Keep control of changes to Google Analytics

Keep a simple record of the Google tags in use, the GA4 measurement ID, the events marked as key events and the people allowed to publish changes. Test new tags in Google Tag Manager Preview before publishing. Use DebugView after release to confirm the live event sequence.

Dealer groups need the same discipline across every dealership location. A central tag register and approval process help prevent a website provider, agency and internal marketer from adding overlapping measurement to the same property.

Google Tag Manager is useful because it brings tags into one managed container. You need named ownership, change logs, and regular checks to keep the data dependable, and GTM allows you to implement these.

What to do when the bounce rate changes

You should first decide whether the change reflects better customer behaviour or a change in measurement.If bounce rate drops sharply and the lead data doesn't support it, check the tags, page-view events, and key-event triggers.

Once the data is credible, it can help you improve the pages and campaigns that drive genuine enquiries. 

Speak to Autoweb Design about switching to our Studio website platform, where all of this will be handled for you. We run everything through GTM, meaning there is far less chance of any duplicate codes occurring.