Google Analytics Setup NZ: GA4 + GTM Without the Guesswork | TienWave Labs

Why just installing the code is not a setup

Google Analytics 4 is not the old Universal Analytics. It is event-based, not pageview-based. There is no universal correct configuration: the events you measure depend on what your site is for.

Default GA4 gives you traffic, not business answers. Without Tag Manager, you may be editing website code every time you want to track something new.

For a NZ small business, proper setup is a foundation. The point is answering which pages, channels, and actions produce enquiries — not collecting a bigger pile of numbers.

What you will need before you start

The last item is the one people skip. The whole point of GA4 setup is answering which pages and campaigns produce enquiries. You cannot answer that if you never decide what an enquiry looks like.

• A Google account owned by the business.
• Access to the website so you can add code or use the correct plugin/integration.
• A list of the actions that matter: enquiry forms, phone clicks, quote requests, purchases, or bookings.

Step 1 — Create the GA4 property

A property is one website's analytics home. Do not reuse one property for two different businesses or you will never split the data cleanly.

1. Go to analytics.google.com and sign in with the Google account you want to own the property.
2. Create a new GA4 property and name it after the business, not just website.
3. Set the time zone to Pacific/Auckland so daily reports match the business day.
4. Add your website as a web data stream, not an app stream.
5. Copy the Measurement ID beginning with G-. You will need it for Tag Manager.

Step 2 — Set up Google Tag Manager

GTM is the plumbing: it holds tags (things that send data), triggers (when they fire), and variables (the data they read). Once it is installed, you can manage new event tags in GTM instead of editing website code for every measurement change.

1. Go to tagmanager.google.com and create a web container for the website.
2. Copy the two snippets GTM provides: the head snippet and the body snippet.
3. Add them to every page, or use the theme/plugin field that inserts them automatically.
4. Publish the default container version so the container is actually available to the site.

Step 3 — Connect GA4 to GTM

This is the core tracking connection. It gives GA4 a pageview-style signal on each page. The business events below are what turn that traffic data into useful reporting.

1. In GTM, go to Tags → New → Google tag/GA4 configuration.
2. Paste the Measurement ID from Step 1.
3. Set the trigger to All Pages.
4. Save and submit the container version.

Step 4 — Track what matters: events, not just visits

In GTM, create one GA4 Event tag per event. Use triggers such as Form Submission, Click – All Elements, or custom dataLayer events. Give each event a clear lowercase name such as generate_lead or phone_click. Keep names consistent so reports remain readable.

• Form submission — the main enquiry signal for a service business.
• Phone click — especially important on mobile.
• Email click — useful when email is a primary contact path.
• Outbound link — where a third-party destination matters to the business.

Step 5 — Mark key events as conversions

Events are data. Key events are the actions that matter as business results.

1. In GA4, open Admin → Key events.
2. Find generate_lead, phone_click, or another confirmed business event.
3. Mark the event as a key event.

The three mistakes that break NZ small-business tracking

1. Duplicate tags — GA4 is loaded by both a plugin and GTM, which can double-count sessions and events.
2. No key events marked — the setup appears to work, but nothing counts as a lead or business result.
3. Never verified — tracking is published and forgotten until nobody trusts the numbers six months later.

How to verify it actually works before you trust the data

The rule is simple: if you did not see your own test event in Realtime, tracking is not verified. Do not assume it works because a tag is present in the container.

1. In GTM, use Preview mode and walk through the site. Submit your own test form only in a safe test environment.
2. Confirm the expected GA4 event fires in the preview debugger.
3. Open the GA4 Realtime report and look for your test session within seconds.
4. Check that the event has the right name, not page_view when you expected generate_lead.

When to get help

If you have attempted this twice and the numbers still look wrong, the DIY path has already cost time without producing trustworthy data. A proper GA4 + GTM setup for a typical NZ small-business website is a defined job: map the business actions, implement the tags, test the success path, and document what is live.

Step 6 — Connect Search Console and keep the two views together

GA4 shows what people do on the site. Search Console shows which queries brought them there and which pages Google is testing. Connecting the two gives you a clearer picture of SEO and conversion performance.

1. Verify the domain property in Google Search Console.
2. Submit the current sitemap and review coverage for important pages.
3. Link Search Console to GA4 in the property admin settings where the integration is available.
4. Use query and page data together when deciding which content or tracking problem to fix next.

A practical NZ small-business tracking checklist

If any of those checks fails, fix that gap before drawing conclusions from traffic or campaign performance. A clean report built on a broken success path is still a bad report.

1. GA4 property created with a web data stream for the NZ domain.
2. GTM container installed and publishing to production.
3. Google tag and GA4 event tags sending to the correct Measurement ID.
4. dataLayer events firing for form starts and successful submissions.
5. generate_lead and other business events marked as key events in GA4.
6. Search Console verified and sitemap processing checked.
7. Reports limited to useful dimensions such as service page, source, device, and date.

Check data quality after launch

A successful first test proves that the path can work. It does not prove that every real submission will be counted cleanly over time. After launch, review the event names and counts regularly enough to catch duplicate tags, sudden zeroes, or a new form variant that no longer uses the expected event.

• Compare confirmed enquiry records with the number of generate_lead events instead of treating them as identical by default.
• Watch for duplicate pageviews or duplicate form events after a plugin, theme, or GTM change.
• Keep test submissions identifiable and separate from real customer data where possible.
• Record changes to forms, domains, consent tools, and containers because they can change what GA4 receives.