How to set up Google Analytics 4: 2026 guide

Google Analytics 4 (GA4) helps you understand how people use your website and which actions support your marketing goals. A good setup helps GA4 record the correct website actions, avoid duplicate or missing events, respect user consent, and create reports your team can use.

Google Analytics 4 is Google’s current analytics platform for websites and apps. It collects data through events, such as a page view, form submission, login, or purchase. Each event can include parameters that add useful details, for example, the page URL, product name, value, or traffic source. 

GA4 organizes data through three main levels:

GA4 matters in 2026 because Universal Analytics no longer processes new data. Businesses now use GA4 to measure website and app activity, build audiences, analyze attribution, and connect analytics data with products such as Google Ads. 

The quality of the setup matters as much as the tool itself. A duplicated tag can report two page views instead of one. A broken purchase event can report the wrong revenue. Missing consent signals can affect data collection and advertising features.

Businesses use server-side tracking to collect more complete data and control what reaches Google Analytics. The browser sends each tracking request to a server container first, where you can filter or enrich the data based on your business and privacy needs. The server container then forwards the processed events to GA4. This setup can also help you create more resilient first-party cookies.

Write down the actions that support the business before creating tags. Examples include:

This becomes your tracking plan. It stops the property from filling up with events that nobody uses.

Keep data together when it belongs to the same logical user journey and business. Keep it separate when access, ownership, branding, or reporting needs are different.

For connected domains, such as a main website and a separate checkout domain, you can usually use one web stream with cross-domain measurement. Cross-domain measurement helps GA4 recognize one user and one session while the person moves between the domains. 

GA4 does not collect or manage users’ consent choices. Your consent banner or consent management platform (CMP) collects each user’s choice and passes the corresponding consent state to Google tags through Google Consent Mode V2. Google tags then adjust their behavior based on that state.

Set up and test consent before publishing your GA4 tag. Do not install analytics first and add consent later, especially if your website receives visitors from regions with privacy and consent requirements.

Before adding GA4, check whether it is already installed through your CMS or website builder, a plugin, the website code, or a Google Tag Manager web container.

Running the same Measurement ID through a plugin, website code, and GTM at the same time can create duplicate events.

You can add GA4 through a website platform, directly in the website code, or with a Google Tag Manager web container. You can also extend the setup with server-side tracking through Stape Gateway or server Google Tag Manager. The account and data stream steps are the same for every option. After that, this guide explains each setup route one by one.

Go to Google Analytics and sign in with the Google account that will own and manage the setup.

In the bottom-left corner, click Admin. At the top of the Account column, click Create, then select Account. Enter the business name and review the account data-sharing options.

Do not create a new account when the business already has a suitable one. One account can contain several properties.

In Admin, select Create, then Property.

Add:

The reporting time zone decides which day receives an event. The currency affects how GA4 displays revenue values, so both settings should be correct from the beginning. 

Under Data collection and modification, open Data streams and select Web.

Enter the main website address and give the stream a clear name. Leave Enhanced Measurement enabled for now. You can review each Enhanced Measurement option later. 

After creating the stream, GA4 will show its Measurement ID. It starts with G-, for example: G-ABC1234567. The Measurement ID tells the Google tag where to send the website’s data. 

Your GA4 property and web data stream are now ready. Next, choose how to connect your website to GA4. The following options explain each setup route, from a CMS or website code to Google Tag Manager and server-side tracking.

Some website platforms provide a field for a Google tag ID or GA4 Measurement ID.

This route works well when the platform has a reliable native GA4 integration, and you only need basic measurement. 

Use the manual method when the website does not support a native integration, and you do not want to use GTM.

Google advises against adding more than one Google tag for the same setup to each page. 

A developer will normally handle this route. Future event changes can also require code updates, which is why marketing teams often choose GTM instead.

First, create a GTM account and web container, then install the web container on every page of the website.

Then configure GA4:

Google’s current setup instructions use a Google Tag with the Initialization - All Pages trigger. 

Do not install the same GA4 setup directly in the website code and through Google Tag Manager. Using both methods can send duplicate data.

This setup installs the main Google tag and collects standard information such as page views. Actions such as form submissions, booked calls, account registrations, and purchases require additional event tracking.

Stape Gateway provides a simpler and faster route to server-side tracking for GA4 and Google Ads. It works with the GTM web container configured in Option 3, so you do not need to manually create GA4 clients, server tags, or triggers.

Before continuing, complete Option 3 and use GTM Preview to confirm that the Google tag fires correctly. You should also check the GA4 Realtime report to make sure GA4 receives your website visit.

Server Google Tag Manager gives you more control over how website data reaches GA4 and other platforms. Requests first go to the server container, where you can filter events, enrich their data, remove information you do not want to share, and choose which platforms receive each event. 

This option is more flexible than Stape Gateway because it is not limited to GA4 and Google Ads. You can use the same server container to configure tracking for Meta, TikTok, and other platforms, with separate tags and rules for each destination. It is a better fit when you need advanced data control or plan to expand your server-side tracking setup, although it requires more technical work. 

Google Analytics Measurement Protocol sends events to GA4 through Hypertext Transfer Protocol (HTTP) requests. It is useful for offline actions and server events, such as a lead being qualified in a customer relationship management system or a refund being completed in a backend.

Google states that Measurement Protocol should support normal website or app tagging, rather than replace it. A Measurement Protocol-only setup can provide partial reporting because some information depends on the browser tag or app software development kit. 

This route normally requires a developer. Events must include the correct user, session, consent, event, and eCommerce information to connect properly with the online journey.

For GTM installations, open Preview mode and connect Tag Assistant to the website.

Confirm that the Google tag fires once on the expected pages. Test several page types, including the homepage, product pages, forms, checkout, and confirmation pages.

Open Reports, then Realtime.

Visit the website from a test device and perform several actions. Realtime shows activity from the last 30 minutes and is useful for confirming that GA4 is receiving events. 

Enable debug mode through Tag Assistant or your testing setup, then open DebugView in GA4.

DebugView shows the events sent by one test device and lets you inspect their order and parameters. It is especially useful for checking forms, eCommerce events, event names, values, and currencies. 

Open the browser’s developer tools and use the Network tab to find GA4 collection requests.

For server-side tracking, confirm that GA4 requests use the first-party tagging URL configured for your setup. If you use server Google Tag Manager, open the server container Preview mode and confirm that it receives and processes the request. If you use Stape Gateway, follow the testing steps in the Gateway setup guide.

GA4 should be compared with the system that records the business results.

For example:

The numbers will not always match exactly because the systems collect and process data differently. Large or sudden differences still need investigation.

Google notes that standard reports and explorations can take 24 to 48 hours to process fully. Use Realtime and DebugView for immediate installation checks. 

Enhanced Measurement can collect several website interactions without extra code. These include page views and optional events for scrolls, outbound clicks, site search, video engagement, file downloads, and form interactions. 

Open the web data stream and review every option. Disable an event when another tool or custom tag already measures the same action, as two implementations can create duplicates.

A key event is an event that represents an important business result.

Common examples include:

generate_lead

sign_up

purchase

book_appointment

subscribe

Any collected event can be marked as a key event. Do not mark every event as important. A page view or scroll is normally an interaction, not a final business result.

Standard GA4 properties offer two user and event data retention options: 2 months and 14 months.

The setting affects explorations and funnel reports, but it does not remove historical data from standard aggregated reports. Choose 14 months when the business needs longer user-level analysis and its privacy policy supports that period. 

Internal visits from employees, developers, and agencies can change website results.

GA4 lets you identify internal traffic with Internet Protocol (IP) address rules and exclude it through a data filter. Start with the filter in Testing mode. An active exclusion filter permanently removes matching incoming data from Analytics and BigQuery. 

Payment providers, login systems, and external booking tools can appear as referral sources when users return to your website. If these services should not receive marketing credit, add their domains to the unwanted referrals list.

To add a domain:

After you save the change, GA4 will continue collecting the user’s events but will no longer attribute the session to the matching domain.

Use the unwanted referrals list only for domains that support the customer journey without introducing the user to your business. For example, a payment provider may send the user away from your website during checkout and return them after payment. The provider should not replace the original traffic source, such as Google Ads or organic search, so adding its domain to the list protects the correct attribution.

This setting does not filter traffic. If the referrals come from bots or spam, adding the domain to the unwanted referrals list will only change the reported source. The unwanted traffic will still appear in GA4. To identify and remove bot or spam referrals from your GA4 reports, follow our guide to filtering bot traffic in GA4.

Use cross-domain measurement when a user moves between connected domains during one journey.

This is common when a company uses:

Without this configuration, GA4 can identify the same visitor as two users and two sessions. 

Link your Google Ads account to the GA4 property so data can move between both platforms. This allows you to view Google Ads campaign data in GA4, create Google Ads conversions from GA4 key events, and use relevant conversions for bidding. 

Choose events that represent completed business outcomes. For example, use a successful form submission rather than the button click that happens before it. Do not set both actions as primary conversions, as Google Ads could treat one customer result as two separate actions.

For detailed instructions on creating, testing, and improving your conversion setup, use our Google Ads conversion tracking guide.

Connect your consent management platform (CMP) to Google Consent Mode so Google tags receive each user’s consent choice. Consent Mode does not replace the consent banner or collect consent itself. It changes how Google tags behave after the CMP communicates whether the user accepted or rejected each data category.

For users in the European Economic Area, configure the analytics_storage, ad_storage, ad_user_data, and ad_personalization signals. Test the setup after accepting all cookies, rejecting them, and changing individual preferences. Then check Consent settings in GA4 to confirm that the web data stream receives the required signals.

Our Google Consent Mode V2 guide explains the available implementation options, consent signals, and testing process in more detail. 

Use this checklist after setting up GA4 through a Google Tag Manager web container. It covers the main checks explained in this guide.