Live tracking demos

The warehouse is the record.
The tools read from it.

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 is collected on your own domain and written straight into 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 below is a working page with real tracking on it, and you can watch the events fire while you click.

Open the live case How the demos are built

01 — The pattern

How every case here is built

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.

  1. 1

    Its own web address

    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.

  2. 2

    Its own clean tag setup

    one container per case

    A fresh Google Tag Manager container built from one documented standard. No inherited legacy tags, so what fires on the page is exactly what is written down for the case.

  3. 3

    One trigger, both destinations

    warehouse + GA4

    The page only announces what happened. The container passes that to your warehouse and to GA4 in the same instant, under the same consent — so the two can never quietly drift apart.

  4. 4

    One warehouse behind all of it

    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

Pick the one that looks like your business

One business model per case. The question each of them answers is different — a lead, an order, a booking, a signup — while the pipeline underneath stays the same.

Every case states its two settings up front, because together they decide where your numbers come from:

  • Collector who owns the entry point on the page — your tag manager (GTM-first), or the tracking script itself with no tag manager in the path (i1-first).
  • Analysis which dataset the numbers are quoted from — your warehouse (i1), GA4, or a defined merge of both.
Live now

Lead generation

Start here. A real lead form, a live stream that shows every tracking event the moment it fires, and a cookie panel showing which identifiers a page can and cannot read. It walks you through how a lead travels from the form into your warehouse — and into GA4 at the same time.

  • Collector GTM-first
  • Analysis i1
Shows you
lead tracking, visitor identity, GA4 side by side
Tag manager
GTM-MQRVGH9M
Open the walkthrough →
Demo · walkthrough coming

Online shop

Catalog, cart and checkout, clickable today. The walkthrough being built on it takes the e-commerce question: every step from product view to purchase, with revenue and item detail landing in your warehouse instead of only in a reporting tool that rounds it off.

  • Collector to be defined
  • Analysis to be defined
Will show
product, cart and purchase events with revenue
Tag manager
own container, set up when the case goes live
Open the demo →
Demo · walkthrough coming

Beauty & booking

A service portfolio and an appointment flow, clickable today. The walkthrough being built on it takes the booking question: counting the appointment as the conversion, and connecting the booking someone made online to the visit that actually happened in the studio.

  • Collector to be defined
  • Analysis to be defined
Will show
bookings as conversions, online tied to offline
Tag manager
own container, set up when the case goes live
Open the demo →
Demo · walkthrough coming

B2B SaaS signup

Pricing, trial signup and a product preview, clickable today. This one is deliberately the counter-example: its walkthrough runs without a tag manager at all, to show that the warehouse setup does not depend on one — which matters when a container is blocked, cluttered, or simply not yours to change.

  • Collector i1-first planned
  • Analysis i1 planned
Will show
trial funnel, anonymous visitor to known account
Tag manager
none — the tracking script collects directly
Open the demo →

03 — What's running

No mystery stack

These are the real identifiers behind the page you are on right now. Open your browser's network tab and you will find exactly them — nothing is mocked for the demo.

This page
Tag manager container GTM-PT8Z4WCS, served from gtm.web000.de — our own address, not a shared vendor one.
Each case
Its own container, named on the card above. The cases share nothing except the collector and the warehouse.
Collector
cct.web000.de — the endpoint that receives the events. It sits on this domain, which is what makes the visitor identity first-party and durable.
Warehouse
BigQuery: one raw row per event, unsampled, kept for as long as you decide — in your account, not ours.
Page source
Announces what happened and nothing more. Every tracking change here is a container change, never a code release.
Demo behaviour
The flows are real, the business behind them is not: no order is placed, no lead is stored, no email is sent. The tracking is the point.
Checking the collector… cct.web000.de/script/v1/cct.js

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.