Analytics and Tracking Checklist for Australian Businesses

Quick answer

If you only do five things this week: install GA4 via GTM, configure Consent Mode v2, mark your primary enquiry or purchase as a Conversion, standardise UTMs, and build a simple Looker Studio dashboard. Then QA it in Realtime while you trigger each event yourself.

Analytics and Tracking Checklist

Work through each area in order. Skip anything that does not apply to your business model.

1) Foundation

• GA4 property created with correct time zone (AEST/AEDT) and currency (AUD).
• GTM container installed site‑wide once (no duplicate GA4 tags hardcoded).
• Enhanced Measurement enabled where appropriate (disable site search or video if custom rules needed).
• Google signals assessed; enable only if aligned to your privacy policy.
• Internal traffic filters added (office IPs, agencies, developers, test environments).
• Cross‑domain measurement set up for your domains and payment providers if required.

2) Privacy, consent and governance

• Privacy policy updated to reflect analytics, advertising and data use in Australia (Privacy Act 1988, OAIC guidance).
• Consent mechanism in place; Google Consent Mode v2 configured if using Google tags.
• Data retention set (e.g., 14 months) and access control applied via least privilege.
• PII blocked from URLs, events and UTMs; validate with GA4 DebugView and Tag Assistant.

3) Event and conversion blueprint

Map events to your buying journey. Use GA4 recommended names where possible.

• Core engagement events: page_view, session_start, scroll, file_download, outbound_click.
• Lead gen: view_contact, click_to_call, email_click, form_start, form_submit, generate_lead (mark as Conversion).
• eCommerce: view_item, select_item, add_to_cart, begin_checkout, add_payment_info, purchase (mark purchase as Conversion).
• High‑value micro‑conversions: brochure_download, calculator_complete, booking_start.
• Values and parameters passed (currency, value, items, lead_type, form_name, content_id).

4) Channel integrity and UTMs

• Enable auto‑tagging for Google Ads and link GA4 to Google Ads.
• Connect Search Console to GA4 for organic query and landing insights.
• UTM naming standard created and shared (source, medium, campaign, content, term).
• Block internal UTM pollution (email signatures, staff testing).
• Use lowercase UTMs and avoid spaces; verify in GA4 Traffic Acquisition.

5) eCommerce and payment flows (if relevant)

• Implement GA4 eCommerce schema with item_id, item_name, item_category, price, quantity and currency.
• Test purchases end‑to‑end including third‑party checkouts (Shopify, WooCommerce, Stripe, PayPal).
• Deduplicate server‑side and client‑side purchase events if using both.
• Capture refunds and cancellations for accurate revenue reporting where possible.

6) Site health signals that affect tracking

• 404 and 500 error tracking implemented; broken links monitored.
• Page speed monitored (Core Web Vitals); heavy tag payloads minimised.
• Single‑page app views tracked correctly (history changes, router events).

7) Dashboards and reporting cadence

• Looker Studio dashboard for leadership: traffic, leads/sales, cost, ROAS/CAC, top channels and pages.
• Channel owner dashboards: SEO, Ads, Social, Email with goal‑level reporting.
• Weekly performance review, monthly strategy review, quarterly roadmap.

8) QA, alerts and documentation

• Use GTM Preview/Debug and Tag Assistant to verify each event and parameter.
• Realtime checks for key user journeys (mobile and desktop).
• Anomaly alerts set for traffic and conversions (sudden drops or spikes).
• Change log maintained for tags, triggers and variables; rollback plan in place.

9) Hand‑off and continuity

• Access shared with correct roles (Owner, Analyst, Editor) across GA4, GTM and dashboards.
• Backup exports or BigQuery streaming enabled if required.
• SOPs for new campaign UTMs, new form tracking and new page templates.

When each box is ticked, your analytics becomes an asset you can trust. If you find gaps, close them before you make big budget decisions.

Common tracking mistakes

• Installing GA4 both via GTM and directly in code (double count).
• Not marking primary goals as Conversions in GA4.
• Inconsistent UTM naming causing channel misattribution.
• Missing cross‑domain measurement for booking engines or payment gateways.
• Ignoring internal traffic filters and staging environments.
• No consent configuration despite using ad personalisation.
• Dashboards that don’t match commercial questions.

Analytics and Tracking Pages

Explore related pages to deepen your setup and decision making.

Related pillars

Implementation tips for Australia

• Set currency to AUD and ensure GST handling is consistent in revenue values.
• Use AEST/AEDT time zones so daily reports match your trading day.
• If you advertise, connect Google Ads and enable enhanced conversions only when lawful and disclosed.
• Document data ownership and make sure the business, not a vendor, controls admin access.

FAQs

How long does a clean GA4 + GTM setup take?

Simple lead‑gen sites can be audited and fixed in 1–3 days. Multi‑domain or eCommerce setups often take 1–3 weeks including QA and dashboarding.

Do I need server‑side tracking?

It can improve data quality and page speed for high‑scale advertisers, but most small to mid‑sized Australian businesses do well with a solid client‑side GTM setup and good consent controls.

What should I include on my dashboard?

Leads or sales by channel, cost per lead/sale, conversion rate, top landing pages, top queries (Search Console), and a section for QA notes or anomalies.

What a sensible next step looks like

Confirm your measurement plan, deploy events through GTM, test in Realtime, standardise UTMs and ship a simple dashboard. Then move to optimisation: improve conversion rate, creative and channel mix using your new insights.

Related Marketing Help