Google Analytics 4 Setup: A Complete Configuration Checklist

Tarık Tunç
a few seconds ago
6 min read

If your google analytics 4 setup is incomplete or misconfigured, you are making every marketing decision on faulty data. A missed event here, a miscounted session there — these errors compound over weeks and months into reports that mislead rather than inform. Getting the foundation right matters more than any dashboard you build on top of it.

This guide covers every step of a proper GA4 configuration, from creating the property to verifying that your data is clean and trustworthy.

⠀

Why GA4 Setup Requires More Attention Than UA Did ve Google Analytics 4 Setup

⠀

Universal Analytics was relatively forgiving. Drop in a tracking code and pageviews appeared automatically. GA4 operates on a fundamentally different model. It is event-based rather than session-based, which means nearly everything you want to measure must be explicitly defined or enabled.

Out of the box, GA4 collects a handful of automatic events — page views, scrolls, outbound clicks, site searches, and video engagement. Anything beyond that requires deliberate configuration. If you skip the setup steps, you will end up with a property that looks functional but is quietly missing most of the signals that matter for business decisions.

The good news is that a thorough initial setup pays dividends for years. Once your events, conversions, audiences, and data streams are configured correctly, reporting becomes reliable and scalable.

⠀

Step 1: Create Your GA4 Property and Data Streams

⠀

Start in Google Analytics Admin. Create a new GA4 property and fill in the business details accurately — industry category and business size affect the recommended events GA4 suggests later.

Next, create a data stream for each platform you want to measure. A typical setup includes one web stream and possibly iOS and Android app streams if you have a mobile app. For the web stream, enter your domain exactly as it appears in the browser, including or excluding www consistently.

Once the web stream is created, copy the Measurement ID (formatted as G-XXXXXXXXXX). You will need this for the next step.

⠀

Step 2: Install the GA4 Tag

⠀

You have two main options: install the Google tag directly in your site's code, or deploy it through Google Tag Manager.

Google Tag Manager is the strongly recommended approach. It keeps your tracking layer separate from your site code, makes future changes faster, and gives you a staging environment (preview mode) to test before publishing. If you are doing a serious google analytics 4 setup, GTM is not optional — it is the right foundation.

In GTM, create a new tag of type "Google Tag," paste your Measurement ID, and set the trigger to "All Pages." Publish the container and verify using GTM's Preview mode that the tag fires on every page.

If you must install the tag directly, paste the Google tag snippet into the <head> of every page. Use Google Tag Assistant to confirm it is loading.

⠀

Step 3: Configure Enhanced Measurement

⠀

Inside your GA4 data stream settings, Enhanced Measurement is a toggle that activates automatic tracking for scrolls, outbound clicks, site search, video engagement, and file downloads. Enable it, but review each sub-setting individually.

Pay particular attention to site search. GA4 tries to detect your search query parameter automatically, but if your site uses a non-standard parameter (anything other than q or s), you need to specify it manually. Incorrect site search configuration is one of the most common setup errors.

⠀

Step 4: Set Up Key Events (Conversions)

⠀

In GA4, what used to be called "goals" are now called "key events" or conversions. Navigate to Admin > Events, and mark the events that represent meaningful business outcomes as conversions.

Common conversions include:

purchase for e-commerce
generate_lead for lead generation forms
sign_up for registrations
begin_checkout for e-commerce funnel analysis

⠀

If these events are not firing yet, you will need to configure them — either through GTM tags, GA4's event modification feature, or developer implementation. Do not mark an event as a conversion until you have verified it fires correctly.

⠀

Step 5: Link GA4 to Google Ads, Search Console, and BigQuery

⠀

Standalone GA4 is useful. GA4 connected to your other tools is significantly more powerful.

Google Ads linking enables audience importing, conversion importing, and cross-platform reporting. Go to Admin > Google Ads Links and connect your Ads account. This single step allows you to push GA4 audiences directly into your ad campaigns for remarketing.

Search Console linking brings organic search data — queries, clicks, and impressions — into GA4 reports. This is how you connect SEO performance to on-site behavior in one place.

BigQuery linking is recommended for any business with significant traffic. It exports raw, unsampled event-level data to Google Cloud, enabling custom SQL queries and advanced analysis that GA4's interface cannot perform. The export is free for most volumes.

⠀

Step 6: Configure Data Retention and Custom Definitions

⠀

By default, GA4 retains event data for only two months. Go to Admin > Data Settings > Data Retention and change this to fourteen months. This is essential for year-over-year comparisons in exploration reports.

Next, register your custom dimensions and metrics. If you are pushing custom data to GA4 — user properties, content categories, subscription tiers — you must register each parameter as a custom dimension before it becomes available in reports. Navigate to Admin > Custom Definitions to set these up.

⠀

Step 7: Set Up Internal Traffic Filters

⠀

Your own visits are polluting your data right now unless you have filtered them out. Create an IP filter to exclude internal traffic: Admin > Data Streams > Configure Tag Settings > Define Internal Traffic. Add your office IP addresses, then go to Admin > Data Filters and activate the filter.

Do not forget to exclude traffic from QA environments, staging sites, and developer machines. These sessions can skew engagement metrics significantly, especially on lower-traffic properties.

⠀

Step 8: Verify Everything in DebugView

⠀

Before calling your setup complete, use GA4's DebugView (Admin > DebugView) to watch events fire in real time. Visit your site in a separate tab with ?gtm_debug=1 in the URL if using GTM, or enable the GA4 DebugView mode in Tag Assistant.

Watch for:

Page view events on every page
Scroll events triggering at 90%
Conversion events firing on the correct actions
No duplicate events
Custom parameters appearing with the correct values

⠀

This real-time verification step catches the majority of implementation errors before they silently corrupt weeks of data.

⠀

Common Google Analytics 4 Setup Mistakes to Avoid

⠀

Skipping data filters: Unfiltered internal traffic is one of the top reasons engagement rates look artificially high in new properties.

Not registering custom dimensions: You can send any parameter you want, but if it is not registered as a custom dimension, it will not appear in reports. Many teams spend hours wondering why their data is missing, only to discover they skipped this step.

Marking events as conversions before verifying them: A broken conversion event still appears as a conversion in reports, creating phantom data that distorts ROAS and CPA calculations.

Ignoring BigQuery export: For businesses with more than a few thousand monthly users, the sampled data in GA4's interface will eventually mislead you. Set up the export early, even if you do not use it immediately.

At Blakfy, we have audited dozens of GA4 implementations and the pattern is consistent: the properties with the most reliable reporting are those where someone invested time in a structured setup process rather than rushing to get data flowing.

⠀

Frequently Asked Questions

⠀

How long does a proper GA4 setup take?

A basic setup — property creation, tag installation, and conversion configuration — takes two to four hours. A full enterprise setup including BigQuery, custom dimensions, audience configuration, and cross-property linking can take one to two days.

Do I need Google Tag Manager for GA4?

Technically no, but practically yes. GTM makes it dramatically easier to manage your tracking configuration, test changes, and scale your implementation over time. Most professional implementations use GTM.

How do I know if my GA4 setup is working correctly?

Use DebugView to watch events fire in real time, compare session counts to your previous analytics tool during a parallel tracking period, and audit your conversion events by manually triggering them and confirming they appear in reports.