Live tracking demo
This site is a demo of a data-warehouse-first marketing tracking and data solution by intellix.one — you do marketing, they do your data. Learn more at intellix.one →
A normal analytics setup sends every click to GA4 and the ad platforms and keeps it nowhere else. The day you need a number they never collected, or a definition changed after the fact, the answer is simply gone. These demos turn that around: every event ends up in your own BigQuery warehouse — raw, unsampled, with the visitor identity attached. GA4 and the ad tools keep running exactly as your team knows them. They just stop being the only place the data exists.
Nothing here is a slide. Every case is a real working site with real tracking on it. The walkthroughs run on their own domains and are shared privately — this page explains what each one demonstrates.
01 — The pattern
Four rules, applied identically to each case below — and identical to the way this gets set up on your own site. If you remember only one thing: your pages never call a tracking vendor directly, and nothing is collected somewhere you cannot get at it later.
one case, one site
Each case runs as a standalone site rather than a folder on a shared one, so cookies, identity and consent behave exactly the way they would on your real domain.
nothing inherited
Each case gets a fresh tracking setup built from one documented standard. No inherited legacy tags, so what fires on the page is exactly what is written down for the case.
export or first-party
The standard route ships GA4 data to BigQuery through Google's export. The advanced route collects first-party with i1, straight into your warehouse — same destination, different owner of the pipeline.
raw rows, kept
Every case writes into the same warehouse in the same shape: one row per event, unsampled, with no expiry you did not choose. Reports, audiences and CRM joins are queries on top of that.
02 — The cases
The same question — where do your numbers live — answered two ways: the standard stack most companies already run, and the self-hosted setup for teams that want to own the pipeline end to end. The case walkthroughs themselves are shared privately.
Every case states its two settings up front, because together they decide where your numbers come from:
The setup most companies start with: Google Tag Manager loads GA4, server-side tagging keeps the calls first-party, and the data lands in BigQuery through GA4's export. This case runs it on a real lead form, end to end — the baseline every other setup gets measured against.
The self-hosted tracking solution, for when you want to keep your data yourself: events are collected first-party, straight into your own warehouse — faster to serve, and with better identity stitching than a third-party pipeline. A tag manager becomes optional here; if you want one, i1 can even inject GTM for you.
Product, cart and purchase: revenue and item detail landing in the warehouse, not only in a reporting tool that rounds it off.
From anonymous visitor to known account: a trial funnel stitched end to end.
03 — What's running
This page tracks itself the way the cases do. Open your browser's network tab and you will find exactly what is described here — nothing is mocked for the demo.
first-party collector · web000.de
What you're looking at: a live check, running in your browser right now, that the first-party collector for this domain is answering. Green means the pipeline these demos describe is up while you read this.