1,387 sessions across eight sites, read side by side in one table

Who this was forUs. We run eight measured web properties across two campaign concepts, two languages, and three site types.

Eight properties, measured rather than assumed

All case studies

The drawing

The problem

We run two campaign concepts side by side, in two languages. You can't compare two concepts unless both are measured the same way. You can't tell a quiet site from a broken one without traffic data either.

What we built

Every property gets its own analytics stream at launch. A daily sync writes it into one traffic table, so all eight can be read side by side. Performance audits, search audits, page load timing, and uptime checks run across the estate too.

What it produced

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

1,387 sessions and 1,285 users across eight measured properties.
Engagement varies a lot. The marketing site engaged 43 of 98 sessions. The newest campaign site engaged 3 of 54.

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.

What runs now

The daily sync runs across all eight properties, and every new property joins the table on its launch day.

Your scenario

If you're launching more than one site, bind analytics on day one, so every site can be read against the others from its first visit. Reach out and tell us how many properties you're running.

Some of the links on this page are affiliate links.

Client names are always kept confidential at MMG, so they have been removed from this case study.

Published August 18, 2026

Last updated November 2, 2026