Google Analytics 4 Setup: The Configuration Most Sites Get Wrong

The mistake: Leaving site search enabled but not verifying the query parameter. If your search uses a parameter GA4 does not recognize by default, search terms will not be captured. Test it: search your site, check the URL, and confirm the parameter matches what GA4 expects.

Check: Admin > Data Streams > Enhanced measurement. Click the gear icon to review individual toggles.

3. Custom Events for Business Goals

Enhanced measurement covers generic interactions. It does not know what matters to your business. You need custom events for actions that represent real value: form submissions, demo requests, purchases, newsletter signups, account creation.

There are two ways to create custom events:

In GA4 directly: Admin > Events > Create event. This lets you create new events based on conditions applied to existing events. For example, you could create a generate_lead event that fires whenever a page_view event occurs on your /thank-you page.

Through Google Tag Manager: More flexible, more reliable. GTM lets you fire events based on element clicks, form submissions, scroll depth thresholds, timer triggers, and custom JavaScript conditions. For anything beyond basic page-based triggers, GTM is the right tool.

The mistake: Relying entirely on enhanced measurement and never setting up business-specific events. Without them, you know how many people visited your site but not how many did something valuable.

4. Marking Conversions (Key Events)

GA4 changed its terminology in early 2024. What used to be called "conversions" are now called "key events." The functionality is identical, the name just changed to align with Google Ads terminology.

Creating an event is step one. Marking it as a key event is step two. Until you mark an event as a key event, it will not appear in conversion reports, it will not be available for Google Ads optimization, and GA4 will not calculate conversion rates for it.

Check: Admin > Key events. You should see every business-critical event listed here. If the list is empty or only contains purchase, you are missing data.

Common key events to mark: generate_lead, sign_up, purchase, begin_checkout, add_to_cart, contact_form_submit.

5. Google Signals

Google Signals enables cross-device reporting. When a user is signed into their Google account on multiple devices, Signals connects those sessions into a single user journey. Someone who browses on their phone during lunch and converts on their laptop that evening shows up as one user with one conversion path, not two separate anonymous sessions.

The tradeoff: Enabling Signals triggers data thresholds. If your traffic is low, GA4 will withhold data in reports to protect user privacy. You might see "(other)" in some dimensions or missing rows in reports. For most sites with reasonable traffic (a few thousand sessions per month), this is not an issue.

Check: Admin > Data collection > Google signals data collection. Toggle it on if it is not already.

6. Data Retention Settings

This is the setting most sites get wrong, and the consequences are invisible until someone tries to run a year-over-year comparison.

GA4 defaults to two months of data retention for event-level data. This means the Explorations section (where you build custom reports, funnels, and path analyses) can only access the last two months of data. Standard reports are not affected because they use aggregated data, but any custom analysis is limited.

Fix: Admin > Data retention. Change event data retention from 2 months to 14 months. There is no reason not to do this unless you have a specific legal requirement for shorter retention.

If your property has been running for six months with the default setting, you have already lost four months of exploration data. It will not backfill. Change it now to stop losing more.

7. Internal Traffic Filters

Your own visits skew your data. If your team visits the site 50 times a day during development, those sessions mix with real user sessions and inflate page views, distort engagement metrics, and dilute conversion rates.

GA4 handles internal traffic through a two-step process:

Step one: Define internal traffic. Admin > Data Streams > Configure tag settings > Define internal traffic. Add your office IP address (or IP range). GA4 adds a traffic_type parameter to events from those IPs.

Step two: Create a data filter. Admin > Data filters. Create a filter that excludes events where traffic_type equals internal. Start it in "testing" mode to verify it is catching the right traffic, then switch to "active."

The mistake: Skipping step two. Defining internal traffic without activating the filter does nothing. The traffic is tagged but not excluded.

8. Connect Google Search Console

This is free data that many sites never connect. Linking Search Console to GA4 brings organic search query data directly into your Analytics reports. You can see which queries drove traffic to which landing pages, along with impressions, clicks, click-through rate, and average position.

How: Admin > Product links > Search Console. Click "Link" and select your verified Search Console property. Once linked, the data appears under Reports > Search Console.

Without this connection, organic search traffic in GA4 shows up as (not set) for query data. The connection fills that gap with real query information from Google.

For a deeper look at what Search Console offers, see our guide to using Search Console for SEO.

9. Connect Google Ads

If you run Google Ads, this connection is essential. Linking Google Ads to GA4 does two things: it imports your GA4 key events into Google Ads for campaign optimization, and it pushes Google Ads cost and click data into GA4 for unified reporting.

Without the link, your Google Ads campaigns optimize based on Ads-side conversion tracking only, which cannot see what happens after someone lands on your site (beyond the initial click). GA4 key events give Ads a fuller picture of which clicks lead to valuable actions.

How: Admin > Product links > Google Ads. Click "Link" and select your Google Ads account. You will need admin access to both GA4 and the Ads account.

The Configuration Audit

If your GA4 property has been running for a while, run through this checklist:

1. One data stream per domain, no duplicates
2. Enhanced measurement events reviewed, site search parameter verified
3. Custom events for every business-critical action
4. All important events marked as key events
5. Google Signals enabled
6. Data retention set to 14 months
7. Internal traffic filter defined and activated (not just defined)
8. Search Console linked
9. Google Ads linked (if running paid search)

Most sites will find at least two or three items that need attention. The data retention setting alone is worth checking immediately, since every day at the two-month default is a day of exploration data you lose permanently.

Monitoring Your Setup Over Time

Configuration is not a one-time task. New team members join and change tag setups. Developers rebuild pages and break event tracking. IP addresses change and internal traffic filters stop working.

Set a calendar reminder to audit your GA4 configuration quarterly. Check the Realtime report to verify events are firing. Test key events by completing the actions yourself and confirming they appear. Review the data stream for anomalies in event counts.

If you want to combine your GA4 data with search performance, competitor analysis, and site health metrics in one place, Ooty Analytics connects directly to your GA4 and Search Console properties and surfaces the insights that matter for growth.

Good measurement starts with good setup. Get the foundation right, and every analysis you build on top of it will be more accurate and more useful.