GA4 setup checklist

From the property to consent mode, from internal traffic to testing: the items to work through in order to set up GA4 properly from day one.

· 13 min readUpdated: Data

Short answer

A sound GA4 setup starts with a single tag source, marked key events, complete e-commerce events, working consent mode, an internal traffic filter and data retention raised to 14 months. Test every step with Tag Assistant and DebugView before going live.

As the site goes live, someone pastes the GA4 code into the theme’s header field, says “analytics is set up” and the job is closed. A few months later the marketing team wants to compare last season in an exploration and finds that only the last two months of data are there. The reason is simple: GA4 properties keep user-level data for two months by default, and nobody changed the setting. A GA4 setup doesn’t end with adding a snippet of code; the checklist in this article gathers, in order, the settings that need doing from day one.

If your numbers already don’t match between GA4 and the ad platform, we suggest starting with why GA4 and Google Ads show different numbers. Here we go one step earlier, to the setup itself.

The eleven stages of the GA4 setup checklist, from the measurement plan to testing 1 Measurement plan 2 Property, data stream and basic settings 3 Google tag or Tag Manager 4 Enhanced measurement 5 Key events 6 E-commerce events 7 Consent mode 8 Internal traffic and unwanted referrals 9 Cross-domain measurement 10 Google Ads and Search Console 11 Testing: Tag Assistant and DebugView The eleven stages of the GA4 setup checklist, from the measurement plan to testing 1 Measurement plan 2 Property, data stream and basic settings 3 Google tag or Tag Manager 4 Enhanced measurement 5 Key events 6 E-commerce events 7 Consent mode 8 Internal traffic and unwanted referrals 9 Cross-domain measurement 10 Google Ads and Search Console 11 Testing: Tag Assistant and DebugView
Figure: the checklist starts with the measurement plan, moves through property settings, the tag, events, consent mode, filters and links, and ends with testing in Tag Assistant and DebugView.

Before you start: the measurement plan

A Google Analytics 4 setup starts with a one-page document before any tool. It records three things:

  • The events where the business makes money. A purchase, a quote form, an appointment, a phone click or a registration.
  • Each event’s name and parameters. Which name each event is sent under, and what information travels with it.
  • Which event will feed ad bidding. Usually one or two events; not all of them.

In a property set up without a plan, each team member adds their own event, and a year later “form_send”, “form_submit” and “contact_form” are counting the same thing under three different names. We walk through writing the plan step by step in how to write a GA4 measurement plan.

Property, data stream and basic settings

  1. Open the property in the right account. The GA4 property should sit in the business’s own Google Analytics account; the agency or freelancer should be added only as a user. When the agency changes, the owner of the data shouldn’t.
  2. Set the time zone and currency. Set the property to the same time zone as the Google Ads account and to the currency sales will be reported in.
  3. Create a single web data stream. Opening a second stream for the same site splits the data in two. Note the measurement ID (the one starting with “G-”).
  4. Raise data retention to 14 months. For standard properties the options are 2 months and 14 months; the default is 2 months. The setting doesn’t affect standard reports, but explorations and funnel reports can’t show data older than the retention period. Because the setting doesn’t work retrospectively, it needs doing on the first day.

Google tag or Google Tag Manager

You can add the tag directly to the site’s code as the Google tag (gtag.js). But if the site has forms, a basket, checkout steps and several ad platforms, Google Tag Manager (GTM) is usually the tidier route. Tags are managed in one place, changes are tested in preview, and every publish is saved as a version.

Whichever route you choose, the rule is the same: the GA4 tag must load from one place on the site. A tag added to the theme settings, an e-commerce plugin and GTM at the same time counts every page view twice. This mistake is especially common on e-commerce sites built on a ready-made platform, where the platform’s own GA4 integration is switched on and the same events are also sent through GTM.

Enhanced measurement: what to leave on

When a web data stream is created, enhanced measurement is on by default and collects these events without any code: page views, scrolls, outbound clicks, site search, YouTube video engagement, file downloads and form interactions.

Two of them need checking:

  • Site search. GA4 recognises search results from certain parameters in the address (for example “q” or “s”). If your site’s search address uses a different parameter, add it in the settings, or no search data will arrive. We explain how to read and act on those search terms in how to improve on-site search in an online shop.
  • Form interactions. The automatic form event doesn’t work reliably on every site; it may count failed submissions, or miss some forms entirely. Don’t leave an important conversion such as a quote form to this automatic event. Set up a separate event that shows a successful submission and, if needed, turn form interactions off so the two counts don’t get mixed up.

Key events: the actions that count as conversions

In GA4, the actions that matter to the business are now marked as “key events”; the word “conversion” is used on the Google Ads side. Things to check:

  1. Is there an event for each important action in the measurement plan, and does it fire at the right moment? For a form, a successful submission rather than a button click; for a purchase, the confirmation after payment.
  2. Are these events marked as key events in the admin panel?
  3. Are the event names consistent? Using Google’s recommended event names (for example “generate_lead”, “purchase”) makes it easier for reports and integrations to recognise them.
  4. Does the event fire again when the thank-you page is refreshed? If it does, fix it so it counts once.

E-commerce events

For GA4 to be useful to a shop, the whole purchase funnel has to be measured. From the recommended events in Google’s e-commerce guide, set up at least these: view item (view_item), add to cart (add_to_cart), begin checkout (begin_checkout) and purchase (purchase). The item list view, shipping and payment info steps make the funnel easier to read too.

Three parameters on the purchase event are vital:

  • transaction_id: A unique ID for each order. GA4 deduplicates purchases that arrive with the same ID, so use a different ID every time, even for test orders.
  • value and currency: If a value is sent, the currency must be sent too; otherwise revenue metrics may not be calculated correctly. According to Google’s guide, value is the sum of price times quantity across the items, excluding shipping and tax.
  • items: The list of products sold. Without this array, the product reports stay empty.

If your platform completes the purchase on the payment provider’s page, always test that the customer comes back to the site and that the event fires on the confirmation page.

When a visitor rejects the cookie notice, Google’s tags have to respect it. Google’s consent mode handles this with four consent types: analytics_storage for analytics cookies, ad_storage for advertising cookies, ad_user_data for sending user data for advertising, and ad_personalization for personalised advertising. The last two were added with the second version of consent mode (Consent Mode v2).

Things to check:

  1. Is the default state set before any measurement? Before the consent notice has loaded, tags shouldn’t run, or should run assuming consent was refused.
  2. Basic or advanced? In a basic implementation, tags don’t load at all until consent is given. In an advanced implementation, tags load and, without consent, send limited signals without cookies, which Google uses to model some of the data. Decide which suits you together with your legal adviser.
  3. Is the choice really passed on? Press “Reject” in the notice and look at how the tags behave in preview mode; then accept and look again.

The general framework is similar under KVKK (Türkiye’s Personal Data Protection Law, Law No. 6698) and, for visitors in Europe, the GDPR. Get consent in advance for non-essential cookies, make accepting and refusing equally easy, and explain in plain language which data is processed for what purpose. The notice text and the legal assessment are outside the scope of this article; prepare them with a legal adviser.

Internal traffic and unwanted referrals

Visits from your own team and the agency inflate the numbers noticeably, especially on small sites.

  1. Define internal traffic. In the data stream’s tag settings, add your office IP addresses to a rule; this traffic is marked with the “traffic_type” parameter (default value “internal”).
  2. Run the data filter in Testing first. While a filter is in Testing, it doesn’t delete matching data; it only marks it. Google suggests waiting 24 to 36 hours before validating. If the result is right, switch the filter to Active. The effect of an active filter is permanent and isn’t applied to past data.
  3. List unwanted referrals. A customer returning to the site from the payment provider’s page can show up as a new session and as “referral” traffic. Add third-party domains such as payment and authentication services to the list of unwanted referrals in the tag settings, so the sale is credited to the channel that brought the customer and not to the payment page.

Cross-domain measurement

If visitors move from the main site to a shop or booking system on a separate domain, and your tag is on both, set up cross-domain measurement in the configure your domains section of the tag settings. Both sides must use the same measurement ID from the same data stream. If it works, the “_gl” parameter appears in the address bar on the way across.

  • Google Ads: Link the GA4 property to the Google Ads account. What must be on for audiences to reach Google Ads after linking is covered in our GA4 audiences article. If you are going to import key events into Google Ads and also use a separate Google Ads tag for the same sale, decide which one is primary; if both are primary, the bidding strategy sees the same sale twice.
  • Search Console: Set up the link from the product links section of the admin panel. You need to be a verified owner of the Search Console property. The link lets you see organic search queries side by side with page behaviour in GA4.

Testing: Tag Assistant and DebugView

No setting counts as “done” until it has been tested.

  1. Turn on debug mode with Tag Assistant. When you connect your site to Tag Assistant, events from your own device are marked as debug data in GA4. If you use GTM, preview mode does the same job and shows which tag fired with which trigger, and how many times.
  2. Watch the events in DebugView. DebugView in the admin panel shows events from the device in debug mode as they happen. Check that each event arrives under the right name, with the right parameters, and once.
  3. Test with consent accepted. If consent mode is in place and consent to analytics cookies hasn’t been given, events don’t appear in DebugView. That isn’t a fault, but it means you need to test with consent given.
  4. Run a real transaction. Fill in the form, place a test order, cancel it. Write down how many times it appears in GA4, in the ad platform and in the CRM.

Common mistakes

  • The tag loading from both a plugin and GTM, so everything is counted twice.
  • Data retention left at 2 months.
  • Form conversions measured by button clicks, so failed submissions count too.
  • The currency or a unique order ID missing from the purchase event.
  • The payment provider getting the credit for sales.
  • No internal traffic filter at all, or one switched to Active without testing.
  • No record of the setup, so a year later nobody knows what each event counts.

Once the setup is clean, the weekly read gets easier too; in the Monday report we describe how we report a few chosen numbers each week. Writing the measurement plan, doing the setup and auditing it are part of our data and CRO service.

Common questions

How long does a GA4 setup take?

Adding the code takes minutes; most of the time goes on the measurement plan, the e-commerce events and testing. It depends on the site’s platform and how many events need measuring, so a single figure wouldn’t be accurate.

Do I need to set up events if enhanced measurement is on?

Yes, for the actions that matter to the business. Enhanced measurement collects general interactions; key events such as a purchase, a quote request or an appointment, and the e-commerce events, have to be set up separately.

If I raise GA4 data retention to 14 months later, does the old data come back?

No. Data deleted while the period was short can’t be recovered; the change applies from that moment on. Standard reports aren’t affected by this setting; the loss shows in explorations and funnel reports.

The observed numbers may drop, because events from visitors who refuse are no longer measured with cookies. In an advanced implementation, Google estimates part of that gap by modelling; but an estimate is not a real count.

If you want to try this list on your own property today, start with the two quickest checks. Look at the data retention period in the admin panel, then send a form from your own phone and count how many events arrive in DebugView. If either of them isn’t what you expected, the rest of the list probably holds a few more surprises.

From here there are two routes: you can work through the whole list with your own team and note the test date next to each item. If you would rather have an outside pair of eyes on the setup, we check the same list item by item as part of our data and CRO service.

Sources

This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 27 October 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.

Tell us about
your project.

Fill in the form or write to us directly, and we will agree on a day to talk.

Your first meeting is with Deniz Sezer, founder of Detmore.

First meeting free · Reply within one working day · Written proposal in 2 to 3 days · NDA ready

What do you need? pick as many as you like

Name, email and phone are required.

Contact

We reply within one working day.