Hiring a Google Analytics Consultant in Melbourne

What a Google Analytics consultant actually does

The job is measurement, not reporting. Reporting is the visible part, but a dashboard built on bad measurement is worse than no dashboard, because people act on it. The work splits into four stages and most engagements are dominated by the first two.

Deciding what to measure. Which actions count as a result for this business: a form submit, a phone tap, a booking confirmed, a quote downloaded, a purchase paid. This sounds obvious and is where most of the value sits, because a business that has not written this down usually finds three people counting leads three different ways.

Implementing it. GA4 measures events rather than the old sessions and goals, so each action has to be defined, fired from the site or from Tag Manager, and marked as a key event. Anything involving a cart, a booking engine or a payment host also needs cross-domain configuration, or the customer looks like a brand-new visitor referred by your own checkout.

Verifying it. Realtime and DebugView while you click through the site yourself, then a month of data reconciled against the source of truth: Stripe, Shopify, the booking system, the inbox. If GA4 and Stripe disagree by more than a couple of percent, the tracking is wrong until proven otherwise.

Reporting on it. Once the events are right, Looker Studio or a scheduled email turns them into something a person reads on Monday. That last step is cheap when the first three are done and impossible when they are not.

The GA4 faults we find most often on Melbourne sites

These are the issues that show up again and again on Australian small business properties, roughly in order of how often we see them. Any one of them is enough to make the numbers misleading.

Internal traffic is not filtered. The office IP address is never excluded, so the team browsing the site all day counts as engaged users. For a business with a few hundred monthly visitors this can be a third of the traffic.

No key events are configured. The property collects pageviews and nothing else, so GA4 reports traffic but cannot report a single result. This is the most common state of a migrated property.

Form submissions are invisible. Modern forms post in the background without loading a thank-you page, so the default configuration never sees them. The fix is an event on successful submit, not a redirect nobody wants.

The tag is installed twice. Once hard-coded in the theme and once through Tag Manager, usually by two different people a year apart. Every pageview counts twice and the bounce rate collapses to something that looks flattering and means nothing.

Cross-domain tracking is broken. The site sits on one domain and the booking or payment step on another, so a completed purchase is attributed to a referral from your own checkout. Self-referrals in the acquisition report are the giveaway.

Ecommerce events are sent without value or currency. The purchase count looks right and revenue reads as zero, which makes every channel look equally worthless.

Consent is not handled. Without consent mode configured, GA4 and the ad platforms report different numbers for the same week, and nobody can say which one is closer to the truth.

GA4, Looker Studio, and whether you need anything else

The core stack is free. GA4 collects, Google Tag Manager fires the events without a developer touching the site for every change, Looker Studio visualises, and Search Console covers the search side that GA4 deliberately does not. For most Melbourne small businesses that combination is the whole answer and the only cost is the work to set it up properly.

Server-side tagging is the main paid upgrade. It improves data quality where browsers and blockers interfere, and it costs real money to run every month. It is worth discussing when ad spend is large enough that a few percent of lost conversions matters, and not before.

There is also a legitimate case for skipping GA4. If all you need is how many people came, from where, and which pages they read, a lighter privacy-first tool such as Plausible, Fathom, Matomo or Umami gives you that on one screen with no event modelling and no consent complexity. We run Umami on our own site alongside Search Console for exactly this reason. Choosing the simpler tool is a valid outcome of an analytics conversation, and a consultant who never mentions it is selling hours.

What analytics work costs in Melbourne

Melbourne agencies commonly quote analytics work as a monthly retainer of A$1,500 to A$5,000, often bundled with advertising management where the reporting exists to justify the ad spend. Bought as a discrete project instead, the same outcomes are much smaller.

A tracking audit with the faults fixed: A$1,000 to A$3,000. One to two weeks. You get a written list of what was broken, the corrected configuration, and a verification pass against your payment or booking system.

A full measurement setup from scratch, including event design, Tag Manager, ecommerce or booking events, consent, and a first Looker Studio report: A$3,000 to A$6,000. Two to three weeks.

A reporting layer that pulls GA4 together with the systems that hold the money, such as Xero, Stripe, Shopify or a booking platform: A$6,000 to A$15,000, depending on how many sources disagree with each other. This is the same work covered in our guide to automated reporting.

Ongoing help is usually better bought as a small block of hours when something changes than as a monthly retainer that bills whether or not anything happened. You own the GA4 property, the Tag Manager container and the dashboards throughout. If we stop working together, nothing switches off.

Check your own tracking in twenty minutes

Before hiring anyone, run these seven checks. They cost nothing and they will tell you whether you have a small problem or a rebuild.

Open Realtime, then load your site on your phone using mobile data. If you do not appear within a minute, the tag is not firing everywhere you think it is.

Open Admin and look for a data filter excluding internal traffic. If there is none, your own team is in every number you have ever looked at.

Open Admin, then Events, and check which ones are marked as key events. If the list is empty, GA4 is counting visits and nothing else.

Submit your own contact form and watch DebugView. If no event appears, your enquiries have never been measured.

Open the Traffic acquisition report and look for your own domain, or your booking or payment host, listed as a referral. That means sessions are being cut in half at the moment of purchase.

Compare last month in GA4 against Stripe, Shopify or your booking system. A gap larger than about two percent means the tracking is wrong, not the bank.

Check that Search Console is linked to the GA4 property. Without it you are blind to which search queries brought people in, which is usually the question the owner actually has.

Agency, freelancer, or someone already in the team

A large agency makes sense when analytics sits inside a bigger paid media programme and the same team owns the spend, the tracking and the optimisation. You pay for coordination and continuity, and the retainer is the price of that.

A freelancer is often the cheapest route for a straightforward audit and fix on a standard Shopify or WordPress site. The risk is availability six months later when something breaks after a theme update.

A studio that also builds the site has an advantage when the tracking problem is really a site problem: a form that does not emit an event, a booking flow spread across two domains, a checkout that cannot pass values. We usually end up in this category, because the fix lives in the code rather than in the analytics tool.

Someone in the team can absolutely own GA4 day to day, and that is the best long-term answer. What they generally need is a correct setup to inherit and a couple of hours of handover, not a permanent dependency.

Questions worth asking before you hire

Who owns the GA4 property and the Tag Manager container at the end. The answer should be you, on your own Google account, with the consultant added as a user you can remove.

How will you verify the numbers are right. If the answer does not involve reconciling against Stripe, Shopify, a booking system or the inbox, the verification is a screenshot.

What happens when the site changes. A theme update or a new booking flow can break event tracking silently, and it is worth knowing whether anyone would notice.

Will you tell me if I do not need this. A consultant who cannot describe a situation in which the free tools plus two hours of work are enough is not advising, they are selling.

Getting started

Run the twenty-minute check above and write down which of the seven fail. That list is the actual scope of the work, and it is usually shorter than people fear.

Send it to us with your site address and the systems that hold your revenue, and we will tell you within a day whether it is an audit, a full setup, or something you can fix yourself in an afternoon. The broader analytics and automation work we do starts from the same place: get the measurement right, then automate the report nobody has time to build by hand.

FAQ