Perth Analytics Consultant

It moves tag execution from the visitor's browser to a container running on a subdomain of your own domain. That recovers a share of the measurement otherwise lost to ad blockers and browser tracking prevention, allows first-party cookies with a longer useful life, reduces the number of third-party scripts slowing your pages, and gives you a single place to control what data each vendor receives. It is an improvement in capture, not a way to see everything - anyone promising the latter is overselling it.

A full server container is not always the answer, and I will say so during the diagnostic. It earns its keep when you are spending enough on paid media that a gap between what converted and what got counted would change how you allocate budget, or when a meaningful share of your audience is on Safari or using content blockers. Below that there is a middle step: serving the tag first-party through a tag gateway, which recovers part of what is lost without a container to run or pay for. It carries no conversion APIs and no payload rules - those still need the container - but it is a fraction of the work, and this site runs that way, so you can see the shape of it before you buy it. The diagnostic measures the gap on your own data first and says which of the three you need, because fixing the GA4 implementation itself usually returns more than adding infrastructure to a setup that was not measuring the right events to begin with.

A container is billed by event volume, so it scales with your traffic instead of with a plan tier. The gateway route carries no event-based hosting bill at all - it runs on the Cloudflare zone your site already sits behind. I quote it separately from the build and size it to your actual volume, so the ongoing commitment is visible before you agree to anything. If you want a figure before we talk, send me your monthly session count and I will give you one.

A container migration runs in parallel: the existing setup keeps reporting while the new one is validated beside it, and the changeover happens only once the two reconcile. A gateway cutover is a smaller thing - it changes where the tag is served from, not what runs the tags - so it is proved out on a staging container first and reversed by restoring the previous snippet. Either way, no reporting gap, and a documented rollback if one is needed.

Yes, and it is a common arrangement. The agency keeps campaign strategy and delivery; I own the measurement infrastructure underneath it. I also work as the technical partner for Perth agencies delivering this for their own clients.

It gives you more control over personal information, not less, because the fields leaving your infrastructure pass through rules you set rather than through whatever a vendor tag collects by default. I build with the Privacy Act 1988 and the Australian Privacy Principles in mind, configure Consent Mode v2 for visitors covered by GDPR or UK GDPR, and hash identifiers before they reach any advertising platform. What I do not do is give legal advice: compliance is a question for your own adviser, and I would rather work with them than around them.

A diagnostic is typically a week or two. A GA4 remediation runs a few weeks. A full server-side deployment with conversion APIs and validation against a full reporting cycle usually runs six to ten weeks, most of which is validation rather than build.