dtv.dev/live demo

Consent-first measurement, live

You decide what we measure.

This page measures itself and shows you every step in plain language: where you came from, what waits for your consent, and what is actually sent to our server.

Arrive like a real visitor

reload this page the way an ad click would

This visit’s URL

Ad platforms append exactly these — each button simulates that with a fresh . Organic search and AI-assistant arrivals are recognised by their referrer, which a same-site button can’t fake.

  1. 1Ad click arrives
  2. 2Captured in this tab
  3. 3Your consent choice
  4. 4What we remember
  5. 5Conversion

This tab

temporary — forgotten when the tab closes

This browser

what survives after you leave

Sent to our server

first-party endpoint · click an event for the raw data

No events yet…

Where your data travels

every event on this page pulses through this pipeline — click a stage to learn what it does
This visit what just happened → what happens next
    instant ~ms ~ms ~seconds on schedule Your browser where you are dtv.dev/data same-origin proxy Tagging server server-side GTM Pub/Sub message bus BigQuery data warehouse Dataform scheduled models
    In the payload leaving your browser right now

    Pulse colour = what the event carries: full payload incl. click ID · stripped — no click IDs · session-only, ephemeral ID. Downstream hop timing is representative.

    How it works

    the same pipeline, annotated — dotted terms explain themselves
    1. Your browser starts locked down. defaults everything to “denied” before a single tag loads, and where you came from — campaign, referrer, — is buffered inside this tab only. Your decides what may leave.
    2. dtv.dev/data keeps everything : events go to our own domain, never to a tracking domain. A small edge worker forwards them onward — your browser only ever talks to dtv.dev.
    3. The tagging server is in action: one server we control reads your consent state on every hit, sets the only when you allowed analytics, and is the only party ad platforms ever hear from.
    4. Pub/Sub queues every event on a reliable message bus. If anything downstream stumbles, events wait in line instead of being lost.
    5. BigQuery receives the raw events within seconds — each one self-describing which consent tier applied, so your choice stays auditable all the way into the warehouse.
    6. Dataform runs scheduled models that turn raw events into , touchpoints and reporting — consent-aware from the first ad click to the final chart.