Google Analytics: what is and isn't supported
One optional measurement ID, nothing else
There is one field for a GA4 measurement ID, and no tag manager slot or custom script field beside it. Leave that field blank and published pages carry no third-party analytics code of any kind.
The built-in numbers do not depend on that tag. We serve your pages, so we can count what we served. That removes a whole class of problems where a browser tag is blocked, or deferred, or never fires while the numbers quietly drift.
It also means the built-in numbers have no consent state to reason about. That counting collects nothing that would need permission, so nothing is lost there when permission is withheld.
What you can see instead
The Analytics page shows how many microsites you have generated, published and edited over time. It shows page views on your live sites, leads captured per site, and the conversion rate between them. Filter to a single site, or to a 7, 30 or 90 day window.
A view is counted when a real page load is served, and requests for images, styles and scripts are not counted. Views are totals, not journeys attached to a person.
What Google Analytics would tell you that this does not
The honest version of this page lists the losses too, so here they are.
- No traffic source or channel breakdown inside the platform.
- No session paths, scroll depth or event funnels.
- No demographic or interest reports.
- No cross-domain view of one person moving between your main site and a microsite.
- No custom events beyond the page view and the lead.
Why the trade holds up
Leave the measurement ID blank and you get back a page with nothing third-party on it. It is lighter, the built-in counting creates no consent banner duty for you, and there is no data deal to explain to your own customers.
You also keep the page's structure exactly as written. A microsite is individually built to answer a question. The capsule at the top is written so an answer engine could quote it alone — meaning the AI answers in ChatGPT and Google. Every version clears the compliance gate before publishing.
And the decision that matters stays in front of you. Which pages get read, which sites capture inquiries, and which need rewriting to be genuinely useful. Views, leads and the rate between them answer that, with no borrowed JavaScript.
Updated October 2026
Frequently asked questions
Can I connect Google Analytics to my microsite?
Yes. Add your GA4 measurement ID on the build form or the Edit screen. On sites that show a cookie banner the tag loads only after a visitor accepts, and the built-in analytics screen keeps working alongside it.
Is there a field for a GA4 measurement ID?
Yes. Paste your GA4 measurement ID on the build form or the Edit screen and every page loads it; on sites that show a cookie banner it loads only after a visitor accepts.
How are page views counted?
They are counted on the server when a real page load is served, and asset requests are not counted as views.
Can I see conversion rate per site?
Yes. The Analytics page shows leads divided by page views for each site and for your account, over the range you pick.
See it built for your business
Every plan starts with a 15-day free trial — build a site in conversation and watch it pass the compliance gate before you decide.
See plans — from $99/moBuild it compliant from day one
Every page is checked before it goes live, by checks that draw on Google Search Essentials and on our own quality rules.
Start your 15-day free trial →Check a site you already have
Free: is your site safe with Google? Get an SEO + compliance score.
Try the Microsite Compliance Grader →