Open Tracked/Guides/Inadequate measures in Google analytics use

Inadequate measures in Google analytics use

Most GA4 properties have the same handful of set-up gaps. A short audit finds them.

3 min read · Updated October 26, 2026

CollectionConfigurationConsentReportingGovernance
In this guide
Key takeaways
  • The usual gaps: duplicate tags, no key events, missing consent, bot traffic, no internal traffic filter, short data retention, unassigned traffic and PII in URLs.
  • Each takes minutes to check in the interface.
  • Fix them in order, then document the set-up.

Google Analytics 4 is flexible, and its defaults are not tuned to your business. Many properties run for years with the same gaps. This page lists the most common, how to check each and the fix. It complements GA4 event tracking, unassigned traffic and Google Tag Manager audit.

The checklist

GapHow to checkFix
Duplicate GA4 tagsPreview shows two page views; DebugView shows doubled eventsRemove one tag
No key eventsAdmin, Key events is empty or full of everythingMark the few that matter
Consent not connectedTags fire before the choiceConsent Mode and tag consent settings. See Consent Mode v2
Bot and spam trafficOdd countries, zero engagementBot filtering. See filtering spam
No internal traffic filterTeam visits mix with customersDefine internal traffic and a data filter
Short data retentionEvent data retention set to 2 monthsSet the longer option where you need it
Unassigned trafficLarge share in channel reportsUTM standard and custom channel groups. See unassigned traffic
PII in URLs or parametersSearch for "@" in page pathsRemove it. See PII
Cross-domain not setSelf-referralsConfigure domains. See multi-domain tracking
Google Ads not linkedNo Ads data in GA4Link the accounts
Check your setup

Check your tracking in one pass

This is an example. Run the check on your own site to see where yours stands.

Governance

  • Name an owner and limit admin access.
  • Keep a change log of property settings.
  • Review the set-up twice a year.

Server-side GA4

A server container can improve GA4 data: first-party cookies, bot exclusion, extra parameters and stripping PII before it reaches Google. See the GA4 tag in a server container. With Open Tracked, Bot Detection and the Visitor Location and Device Info power-ups (every plan) support this.

The short version

3 things to remember

Scroll and the points stack up.

01

The usual gaps: duplicate tags, no key events, missing consent, bot traffic, no internal traffic filter, short data retention, una

02

Each takes minutes to check in the interface.

03

Fix them in order, then document the set-up.

A one-hour audit

1

Admin settings

Retention, key events, data streams, filters, links.

2

Debug

DebugView on a test visit and a test purchase.

3

Reports

Traffic acquisition for unassigned and bot patterns.

4

Explore

Search page paths for personal data.

5

Write the findings

And fix the top three.

0 of 7 done

A realistic example

A store inherits a GA4 property from a previous agency. A one-hour audit finds two GA4 tags on the site, so every event is doubled. Fourteen events are marked as key events. The consent banner is installed but GA4 fires before the choice. There is no internal traffic filter, and data retention is at the short default. The new owner removes the duplicate tag, keeps three key events, connects consent, defines the office network as internal and extends retention. Sessions fall by about a third because the double counting stops, and conversion rate rises to a figure that finally matches the shop. A property can run for years like this, and only an audit shows it.

For online stores

Orders from your store, back to the ad that earned them

Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.

Frequently asked questions

What are common GA4 mistakes?

Duplicate tags, no key events, missing consent, bot traffic, no internal filter, short retention and personal data in URLs.

How do I check my GA4 set-up?

Use Admin settings, DebugView and the traffic acquisition report.

How long is the default data retention?

It is often set to a short period by default. Check and set the longer option you need.

Can server-side tagging improve GA4 data?

Yes, with first-party cookies, bot exclusion and field control.

How often should I review GA4?

Twice a year and after major changes.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Open Tracked
Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...

Turn better tracking into better marketing performance

Start free