Meet Mio

If you run marketing for a hotel, a holiday park or a restaurant group, you often find yourself with GA4 open in one tab and Google Ads in another. Search Console, the booking systems, and the CRM tools fill the rest...

Mio is what we built to replace that. It's the reporting and insight platform we build for our clients. Your web, search, paid, email and booking data sit in one place, they agree with each other, and they stay that way.

What you actually see

When you log in, the pages will look familiar: web performance, search, paid media, email, bookings. There is also some clever forecasting around demand, ad spend, seasonality - but we won't get into that, yet.

The key element of what makes Mio different is that every page reads from the same place, built from your own data, cleaned the same way and on the same calendar. It's built entirely on data you already own. You connect your own Google account and choose which GA4 property, Search Console site and Ads account to share.

This series is about what it took to make that true. It runs in five posts, in the order the data travels. First, where it starts. Then how it gets in, how it's made to mean something and how every client's data is kept apart. Last, what you can do once all of that is in place. This first post is about the problem, because the problem is the reason the rest exists.

Six good products that don't talk to each other

The goal with Mio was always to connect the whole business together. From a marketing point of view there were a lot of data silos and no way to see across them.

You've got the Google suite: GA4, Google Ads, Search Console. You've got a booking system, which for most of our clients is Mews. You've got email sitting in Mailchimp or Klaviyo, behavioural tracking in Clarity and payments in Stripe. Every one of those is a good product, and every one was built to be the centre of your world. So none of them interact with each other. If you want an actual business overview you have to piece it together yourself, and that's really hard.

The numbers don't agree, and none of them are wrong

It's harder than it looks, as well, because the numbers don't agree even after you've stitched them. Google and Meta will both claim the same booking. Their attribution windows are different and neither is wrong. Google Ads restates its own recent history as conversions land late, so a number you screenshotted on Tuesday is a different number on Friday. GA4 only keeps event-level data for fourteen months, and Search Console keeps sixteen. Search Console also withholds rare queries entirely. That means query-level totals can never sum to site-level totals, no matter what you do. That's not a bug you can chase down. That's just how the product works.

Here's how that plays out. Say Google Ads tells you paid search drove 40 bookings last month, Meta says it drove 25, and GA4 credits 30 to organic search. Your booking system recorded 80 in total. Add up the channels and you've had more bookings from marketing than you had bookings. Nobody's lying. Each tool is counting by its own rules, and none of them can see the others.

So you end up in a situation where each platform is internally correct and the set of them is incoherent.

A number on its own can't answer anything

The bigger issue is that a metric on its own doesn't really mean much. Conversions from paid search tell you nothing without what they cost. Cost tells you nothing without what the booking was actually worth six months later, after the stay and after cancellations. None of that tells you anything without knowing whether email or organic touched the same guest first. The number isn't wrong. It just can't answer anything on its own.

Take the most basic question a marketing budget has: is paid search worth it? To answer it honestly you need clicks and cost from Google Ads and sessions from GA4. You need bookings and their value from the booking system, and the cancellations that came after. And you need to know whether that guest had already opened an email or found you organically first. That's four systems for one question, and each one counts days, money and people slightly differently.

That's the problem. It isn't reporting, and it isn't dashboards. You can't see the bigger picture because the pieces are in six different boxes and they're cut to different shapes.

Where Mio starts

So Mio doesn't start with dashboards. It starts by bringing every one of those sources into one place and keeping an untouched copy of everything. Then comes the slow work of making them agree: one definition of a day, of revenue and of a session, used everywhere. The dashboards come last, and they're the easy bit.

The rest of this series walks through that work. Next: how the data actually gets in, and why the pieces that bring it in are designed to do almost nothing.