Event Schema
Schema Doc
Working document · yours to extendLive walkthrough included
ProjectCadence ·Project engagement
A measurement substrate the bidding model can actually optimize against.
Server-side GA4, Meta CAPI, Google Enhanced Conversions, and a compliant consent layer. Closes with a live, version-controlled Event Schema your downstream layers read directly.
Inside the Dynamic Infra layer of the Dynamic Ad operating system. Run as a wedge, or with the full stack.
Buyer trigger
Slot · The Inheriting Measurement EngineerSignal · Active
The Inheriting Measurement EngineerThe CAPI a contractor shipped 18 months ago has decayed. Match quality is sliding, schema ownership is unclear, and the next consent rule lands before the team can triage. The build is the documented substrate the operation runs on.
Signals firing the engagement
Match quality has decayed across the last two quarters and the schema is undocumented
Server-side and client-side conversions disagree by double digits, no reconciliation in flight
A regulated-market launch is pending and Consent Mode v2 coverage has not been verified
Event Schema. The version-controlled substrate every layer above reads.
A documented, version-controlled event schema with server-side instrumentation across GA4, Meta CAPI, and Google Enhanced Conversions, plus a Consent Mode v2 layer that complies without starving the bidding model.
How the build runs.
Write access · documented cadence · operator-led
Phase 01 · Intake
Conversion model and access
Conversion model confirmed against your stack. Existing schema and Gap-Map (where one exists) ingested. Write access provisioned across GTM, server container, ad-platform manager, and the warehouse where applicable.
Phase 02 · Schema
Event schema design
Every event the bidding model depends on is specified end-to-end. Payloads, dedup keys, match-key enrichment, and platform-destination mapping are documented before a single tag is built.
Phase 03 · Build
Server-side instrumentation
Server containers stood up. CAPI, Enhanced Conversions, and server-side GA4 instrumented end-to-end. Consent Mode v2 layer configured. Parity, dedup, and modeled-conversion preservation verified per event.
Phase 04 · Handoff
Documentation and walkthrough
Schema document signed off and version-controlled in your repo. Live walkthrough with engineering and analytics. Monitoring rules and runbook attached so the next engineer extends the substrate, not rebuilds it.
Questions buyers ask before scoping Signal Infrastructure.
Do I need a Signal Audit before the implementation?
Not strictly. Many buyers run the audit first because the Gap-Map becomes a precise scope document. If your team already has a clear inventory of leaks and the conversion model is documented, the build can start at intake without a prior audit.
Will this work alongside our existing GTM setup?
Yes. Server containers run alongside your existing client-side container. Where client tags are degraded, deduplication and parity rules ensure the server-side path is the source of truth without double-counting at the platform.
How is Consent Mode v2 handled for opted-out users?
Consent state is captured server-side, identifiable parameters are suppressed for opted-out users, and Google and Meta receive modeled-conversion signals where the policy allows. The bidding models continue to optimise without ingesting identifiable data.
What does handoff actually include?
A version-controlled Event Schema document committed to your repo, monitoring rules covering match quality and parity drift, a runbook for the next platform update, and a live walkthrough with engineering and analytics. Your team owns the substrate after handoff.
Scope the Signal Infrastructure. Event Schema at handoff.
Integrated scopeEngineered cadenceEvent Schema on handoff
After the projectConversion Infrastructure.Forms and routing are the next leak. Conversion Infrastructure closes them against the same schema this build documents.Other engagements under Dynamic Infra
Each is sold standalone or stacks with the others into a single foundational build.