The fortnight of setup, done before lunch.
Most reporting tools assume your measurement already exists. This one builds it — GA4, Google Tag Manager and Search Console — and then checks the tag is really on the page.
The onboarding that stalls before it starts
New client. The reporting cannot begin because GA4 was set up by someone who left, the tag is on some templates and not others, and nobody can find who verified Search Console three agencies ago.
So the first fortnight goes on access requests and a tagging audit, and the client wonders what they are paying for. Multiply that by every account you take on.
Position 11 discovers what exists, creates what does not, and then does the part everyone skips: fetches the live site and checks the tag actually serves.
How it works
Discover
Asks Google what you can already reach and shows you a list. No hunting for a ten-digit customer ID, no transcribing property numbers.
Provision
Creates a GA4 account and property, a GTM container, and a verified Search Console property — whichever of them is missing.
Verify
Search Console prefers the Analytics method, so a live GA4 tag verifies the property with no DNS record and nothing for the client to do.
Prove
Fetches the site and reports which Google tags it genuinely serves. Provisioning can create everything and still never reach the page.
What you actually get
Ranked by the money at stake, not by how alarming the number looks. This is the output, not a mock-up of one.
Example findings
The detail that matters
Why a GTM container, not just a GA4 tag
A container is the difference between “change a tag” being a config change and being a developer ticket. Across seventy sites that distinction is the whole operating model.
Idempotent by design
Run it as often as you like. A client that already has a property or container is left alone, and an existing one matching the client name is adopted rather than duplicated.
The whole book at once
One client, or every client you manage, with a dry run first so you can see exactly what would be created before anything is.
Order matters, and it is handled
GA4 runs before Search Console on purpose: a live GA4 tag unlocks the Analytics verification method, which removes the DNS step entirely for most sites.
Domain properties, never URL prefixes
Search Console is consolidated onto domain properties so data cannot silently split across www and non-www, or http and https.
Tag verification is not assumed
The site is fetched and read. A container that was created but never installed is the most common reason a new account reports nothing.
What this doesn’t do
Provisioning can only create what your own Google access allows — if the OAuth account cannot administer an Analytics account, nothing here conjures one. DNS-based Search Console verification also needs a record at your registrar, which nobody can place on your behalf. Where an automated route is unavailable, you get told exactly what to do rather than a silent failure.
Reasonable questions
What if I already have GA4 and GTM?
Then nothing is created. Discovery lists what exists and you choose; provisioning only fills gaps.
Can it do this for every client at once?
Not from the dashboard yet: today it runs one account at a time, from each account’s setup page.
Does it put the tag on my site?
It creates the container and tells you the snippet. Installing it is yours, because writing to a client site is not something a reporting tool should do uninvited — but it will then check the tag is live and tell you if it is not.
What if Search Console cannot verify automatically?
It falls back to a DNS TXT token and reports it for you to place. Most sites never reach that step, because a live GA4 tag verifies them without it.