Who this was forUs. We run nine web properties across two campaign concepts, two languages, and three site types.
Campaign sites were going live with no analytics attached. You can't compare two concepts if neither one is measured. You can't even tell a quiet site from a broken one.
Every property gets its own analytics stream at launch. A daily sync writes it into one traffic table, so all nine can be read side by side. Performance audits, search audits, page load timing, and uptime checks run across the estate too.
Or that was the plan. One property never got bound.
| Property | Sessions | Page views | Engaged sessions |
|---|---|---|---|
| Campaign site 1 | 258 | 491 | 57 |
| Campaign site 2 | 252 | 411 | 40 |
| Campaign site 3 | 238 | 314 | 31 |
| Campaign site 4 | 232 | 310 | 29 |
| Product site | 128 | 198 | 26 |
| Campaign site 5 | 127 | 166 | 19 |
| Marketing site | 98 | 252 | 43 |
| Campaign site 6 | 54 | 56 | 3 |
| Store site | no data |
These are small numbers, and we're printing them as counts, not percentages that would flatter them. At this volume no concept can be called the winner yet. That's the honest read.
The daily sync runs across all eight bound properties. The ninth stays invisible until it's bound.
If you're launching more than one site, bind analytics on day one. The site you forget is the one you'll never be able to judge. Reach out and tell us how many properties you're running.
Related tools: Netlify, Surfer, Amplitude, Programmatic SEO Planner, SEO Content Engine Pack
Client names are always kept confidential at MMG, so they have been removed from this case study.
Published August 18, 2026
Last updated September 7, 2026