All blog posts →

GA4 setup often starts by copying an ID into a website. That connection matters, but it leaves a more useful question unanswered: what do you want the reports to tell you? A visitor clicking a form button and a successfully received enquiry are different actions. Decide which one you need before building the tracking.

The steps below are a starting plan for a website using Google Tag Manager. If your ecommerce platform already provides tracking, or the site has an existing setup, review that first. Adding the same set of tags to every website, or deleting every tag you do not recognise, can create problems that are harder to diagnose later.

1. Write down the actions you need to measure

Keep the first list short: a completed enquiry, a purchase, an account registration or another action your business needs to count. For each one, record the success condition, event name and required information. A form button click is not proof that the server accepted the form. Choose a success condition that matches how that form actually works.

Use recommended event names where they fit, and keep the same name for the same action across pages. Record where each field will come from. Separate information that a developer must provide from information GTM can read on the page. Do not place customer email addresses, phone numbers or similar personal information in event names, URLs or parameters.

2. Review the tags already on the website

GA4 may already be installed through the theme, a plugin, a platform integration or GTM. More than one can be sending data. Before adding a tag, identify which setup sends to which GA4 stream. A tag you do not recognise may support another team or an advertising account; investigate its purpose before removing it.

Check who controls the GA4 property and GTM container, and who can publish changes. Your business should retain access after a contractor or employee leaves. When the task is to understand an existing installation, a GA4 and GTM audit may be a better starting point than immediately building a new one.

3. Prepare the GA4 property and web data stream

Confirm the property, reporting time zone and currency, then identify the website’s web data stream. Record its G- measurement ID; this is different from the GTM- container ID. A Google tag ID can use another prefix too. What matters is that the tag is connected to the intended GA4 stream as its destination.

Decide how testing and production will be separated. A test page should not accidentally feed the production reports. If an existing property is in use, review its reports and integrations before opening another property simply to make the account look tidier.

4. Connect GA4 through GTM

Google’s current setup guide covers two valid interfaces. Use the path your container provides:

  1. Open the website’s container. Select Tags > New > Tag Configuration, then Google Analytics > Google Analytics. Where that destination interface is unavailable, use the Google tag method.
  2. In Tag ID, enter the tag ID associated with the intended GA4 stream. You can use its G- measurement ID. Do not enter the GTM- container ID; check the GA4 destination when using another tag ID.
  3. Under Triggering, choose the appropriate Initialization option: All Initialization Events or Some Initialization Events in the newer interface. Check that the default consent state is established before the tag runs, then Save.
  4. Use Preview, enter your site URL and select Connect. After testing, select Submit > Publish and Create Version, name the version and click Publish. Section 6 covers the live checks.

Review the order of consent choices and tag execution together. Do not remove the consent mechanism just to make a tag fire. Define the expected behaviour for a test with analytics consent and another without it, then compare the results with those expectations.

5. Add the events your reports need

Once the connection is ready, work through the actions on your measurement list. Choose useful actions rather than creating a separate event for every button. Ecommerce tracking also needs product and order information. Our GA4 purchase and transaction ID guide covers the data you need to plan for a purchase implementation.

Check that two implementations are not both sending page views. Google’s page_view guidance explains how automatic and manual collection can produce duplicates. On a site that changes the URL without reloading the page, test real navigation as well. Inspect the current method and its records before disabling automatic settings.

You can mark the actions that matter to your business as key events in GA4. This setting does not repair an incorrectly triggered tag. Creating or importing a Google Ads conversion is also a separate consideration. Google’s key event explanation describes that reporting distinction.

6. Test the preview and the published website

Open a personal test session with GTM Preview. Use Tag Assistant to check the action and tag, then inspect the expected event and parameters in GA4 DebugView. If the event is missing, follow our GA4 event troubleshooting sequence to find the stage at which it stops appearing.

When the tests pass, publish the changes with a descriptive version name. Test the live page again outside the preview session. Keep a short record of the page, action, expected event and result. This gives your team a repeatable check after the next website change.

Getting help with the setup

Our GA4 setup and consulting service covers property and stream selection, GTM settings and event implementation. Share your platform, existing setup and the actions you need to track in the project enquiry form. That is enough to start discussing the scope; you do not need to send real customer data.