Tracking, Consent & Event Pipelines

In short

Everything between a user action and a trustworthy row in your warehouse — server-side containers, consent signalling, conversion APIs, deduplication and the GA4-to-BigQuery path.

4 pages

definitions

Consent state: a typed field on each event, not a switch on the pageThe pageview before the banner answer and the purchase after it are both correct, and they carry different consent values. That only works if consent travels per event.definition6 min
Event ID: the value that lets two systems agree a conversion happened onceThe same identifier, the same conversion, both transports, inside the platform's window. Four generation strategies, and the guarantee each one keeps or breaks.definition6 min
The exported event row: nested parameters and no session columnOne row per event, a repeated parameter struct with four typed slots, and a pseudonymous identifier that can be missing. Every figure a report shows is derived from this.definition6 min
The tagging server: a first-party endpoint that owns the payloadA tagging server is not a proxy. It parses one first-party event, adds and strips fields, and emits a vendor-shaped request per destination from your infrastructure.definition6 min

Working on something in this space?

Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.

Start the conversation