A GA4 property that was created and never configured tells you how many people arrived and almost nothing else. The value is in the layer above it: a Tag Manager container that fires meaningful events, conversions defined against your real funnel, and a dashboard that answers the two or three questions you actually ask every month. That is what we set up, and we set it up so it keeps working when the site changes.
← All technologies
— Google Analytics 4
Numbers you can act on.
GA4 and Tag Manager configured as one system, with events that match how your site actually converts — not the default report set nobody opens twice.
What we set up in GA4
01
GA4 & Tag Manager together
One property, one container, one data layer — configured as a pair rather than two tools fighting each other.
02
Events that mean something
Form submissions, calls, downloads, scroll depth and outbound clicks, named consistently so reports stay readable.
03
Conversions & e-commerce
Goals mapped to your funnel, and full purchase tracking on a shop, including items, value and refunds.
04
Consent & Search Console
Consent Mode wired to your cookie banner, and Search Console linked so query data sits beside behaviour data.
Why GA4 with Level UI
- Events named to a convention, so reports survive the next redesign
- Consent Mode configured — GDPR-aware, not analytics-off
- Conversions defined against your funnel, not GA4’s defaults
- A dashboard with the metrics you asked for on one screen
- Handover documentation, so the setup is not a black box
— FAQ
Frequently asked questions
Want analytics that answer something?
Tell us the questions you need answered every month and we will build the tracking backwards from them.