Marketing, Advertising & AdTech// topic
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.
13 pages
diagnostics
- A slice of events lands before the visitor has answered the bannerEvents arriving with an absent consent field are not a compliance abstraction. They are a race between two scripts, and the race has a rate you can measure this afternoon.diagnostic11 min
- Conversions started counting twice the week server-side sending was switched onA step change in reported conversions on the rollout date with flat order volume means deduplication failed. Five candidates, and one report that names which.diagnostic10 min
- The ad account reports a third more conversions than the warehouse, every single monthFour causes, ranked. Two are defects you can fix and two are definitional differences you can only document — and an exact match is not one of the available outcomes.diagnostic10 min
- The click identifier is missing on half the conversions that need oneAn import rejected for a missing click identifier is a capture problem, not a platform problem. Three counts per entry path tell you which hop is eating the parameter.diagnostic10 min
- The same weekly visitors keep being counted as first-time usersA new-user rate near total users is identifier churn, and the expiry attribute is not the lever. Where the identifier gets written from decides how long it survives.diagnostic10 min
- The tagging server's cost is growing faster than the traffic it servesA hosting curve steeper than the sessions curve means the multiplier moved, not the traffic. Measure requests per session and outbound calls per inbound hit before changing anything.diagnostic10 min
- Yesterday's totals change once the daily export replaces the intraday tableA model built at 08:00 and rebuilt at 14:00 disagreeing is not a pipeline bug. It is a provisional table being read as final, and a partition audit tells you which days are settled.diagnostic10 min
definitions
- Click identifiers: the URL parameters that let a server-sent conversion find the ad that caused itA campaign tag describes where traffic came from. A click identifier is the key that joins a sale back to a specific click — and only one of the two is load-bearing.definition8 min
- 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 data layer: a versioned contract between the people who ship the site and the people who measure itA data layer is an interface two teams depend on. Undocumented, it is an API with no owner and no version — which is why tracking dies at every front-end rewrite.definition8 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
Other topics in Marketing, Advertising & AdTech
See allWorking 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