Integrations
Google Analytics and tracking
Add Google Analytics, Tag Manager, Meta or Plausible once and have them track your website, QR ordering, menu apps and bookings.
Start here: you already have analytics
Every Mavos business gets built-in analytics with no setup at all. It runs on your website, your QR ordering menus, your forms, your bookings, and your digital receipts — and it keeps working whether or not you ever connect an outside tool.
The built-in analytics records page and menu views, which products customers look at, items added to the cart, how far customers get through checkout, the booking funnel, and completed orders with revenue. You'll find it under Analytics on your website and under Insights for ordering and forms.
Connecting Google or Meta on top of that is about marketing: matching your ad spend and campaigns to what customers actually did.
Connect your tracking once
Go to Settings → Analytics. Enter any of these — you can use as many as you like at the same time, they don't conflict:
| Tool | What you enter | Where to find it |
|---|---|---|
| Google Analytics | Measurement ID, G-XXXXXXX | Google Analytics → Admin → Data Streams → Web |
| Google Tag Manager | Container ID, GTM-XXXXXXX | Tag Manager → Workspace → container ID, top right |
| Meta | Pixel ID (15–16 digits) | Events Manager → Data Sources |
| Plausible | Your site domain | The domain you added in Plausible |
| Google Ads | Conversion ID, AW-XXXXXXX | Google Ads → Goals → Conversions |
Save, and that's it — the same setup applies to your website, your QR ordering menus, and your menu apps together.
Different settings for one location
Multi-venue businesses can override the company settings for a single location. On the same page, pick the location and enter its own IDs.
A location override replaces the company settings for that location rather than topping them up. So if you give one venue its own Google Analytics ID, enter its Meta pixel and any other IDs on that same screen too — anything left blank there is off for that venue, not inherited. Choose Remove override to put the location back on the company settings.
Different settings for one website
If you run more than one website and want them reporting separately, open that website's own Settings → Analytics and set an ID there. A website-level ID replaces the company one for that tool only — so a site with its own Google Analytics property still uses your company-wide Meta pixel.
Google Tag Manager needs your own domain
Tag Manager works on every surface, but only when your site is on your own custom domain (like order.mycafe.com).
The reason is straightforward: Tag Manager lets you run code you write yourself, and we don't allow customer-written code on a shared mavos.com.au web address, because that address is shared with other businesses and with your own Mavos login. On a domain you own, that risk is yours to manage and Tag Manager runs normally.
Google Analytics, Meta and Plausible work everywhere, custom domain or not — with those you're supplying a setting, not code.
See Custom domains to connect one. It's free and takes a few minutes.
What gets tracked
Once connected, these flow through automatically. You don't have to configure any of them.
| What the customer did | Google Analytics | Meta | Plausible |
|---|---|---|---|
| Viewed a page or menu | ✓ | ✓ | ✓ |
| Viewed a product | view_item | ViewContent | Product View |
| Added to cart | add_to_cart | AddToCart | Add To Cart |
| Started checkout | begin_checkout | InitiateCheckout | Checkout Start |
| Viewed booking slots | view_item | ViewContent | Slot View |
| Chose a booking slot | select_item | — | Slot Select |
| Completed an order | purchase + revenue | Purchase + value | Purchase + revenue |
| Confirmed a booking | purchase + revenue | Purchase | Booking Confirmed |
| Refunded | refund | — | Refund |
| Submitted a form | generate_lead | Lead | Form Submit |
Why your revenue figures will be accurate
Completed orders are sent to Google and Meta from our servers, not from the customer's browser.
That matters more than it sounds. Browser-sent purchase tracking is lost whenever a customer has an ad blocker, closes the tab quickly, or drops off wifi at the worst moment — and it fails silently, so your reported revenue is quietly lower than your real revenue. Sending from our servers means the figures come from the same records as your Mavos reports, and refunds are reported too.
Nothing to set up for Google Analytics — it works from your Measurement ID alone. If you also want it for Meta, or want the most complete Google Analytics data, add the optional API secrets on the same settings page.
Cookie consent
Leave Ask visitors for consent first switched on unless you've been advised otherwise.
When it's on, visitors see a banner, and Google and Meta tags start in a restricted mode that sets no advertising cookies. If a visitor accepts, tracking switches on fully. If they decline, it stays restricted.
Your built-in Mavos analytics is privacy-first and always runs, so you keep a complete picture of your own traffic either way.
If you advertise in the UK or EU, be aware Google requires this consent signalling for ad personalisation and remarketing — it's on by default here.
Getting the most out of it
Use your own domain for ordering. If your website is mycafe.com and ordering is order.mycafe.com, they share a root domain and a customer's visit is tracked as one journey. Send customers to the default Mavos ordering address instead and it counts as a brand-new visit from an unknown source, which quietly destroys your campaign reporting.
Tag every campaign link. Add UTM parameters so Google can group the traffic:
https://mycafe.com/?utm_source=instagram&utm_medium=social&utm_campaign=spring-menu
Use them on social posts, email, paid ads, and printed QR codes. A QR code on a table tent is just a link — give each placement its own utm_source and you'll learn which ones actually drive scans.
Mark your key events. In Google Analytics, go to Admin → Events and mark purchase as a key event. Campaign performance then reads in terms of real sales rather than page views.
Troubleshooting
I saved an ID but no data appears. Check you're looking at the published, live site rather than a preview link — tracking is switched off on previews by design. Then check whether you accepted the cookie banner; declining limits what Google receives.
My ID won't save.
Each tool has a strict format: G- then capitals and numbers, GTM- then capitals and numbers, AW- then digits, and a Meta pixel ID is 15 or 16 digits. Lowercase letters, spaces and stray characters are rejected on purpose.
I saved a Tag Manager ID and nothing loads. Tag Manager needs your own custom domain — see above. Google Analytics, Meta and Plausible work without one.
Orders show in Mavos but not in Google Analytics. Order tracking is sent from our servers shortly after payment, so allow a few minutes. If it still doesn't appear, check the Measurement ID is correct and that the property isn't filtering internal traffic.
My campaign traffic shows as "direct" or "unassigned". Either the link had no UTM parameters, or customers crossed from your website to a different ordering domain. Connecting a custom domain on the same root as your website fixes the second cause.
Still stuck? Contact support and we'll take a look with you.