Campaign measurement operations
Campaign data-layer spec for cleaner readouts
A campaign report is only as trustworthy as the source trail captured before launch. If placement, creative, audience, destination, test cell, and outcome fields are missing or inconsistent, the final readout will invite stronger claims than the data can support.
Use this spec when a publisher, advertiser, agency, analyst, or measurement vendor needs one shared handoff for campaign reporting. It is not a tagging manual for one platform. It is the minimum evidence structure needed to keep delivery, traffic, lead quality, brand movement, and incrementality in their proper lanes.
The minimum source trail
The source trail should let a reader separate unlike contexts before the report becomes a story about performance.
| Field | What it should record | Why it matters |
|---|---|---|
| Campaign ID | A stable ID shared across trafficking, analytics, reporting, and billing. | Prevents one campaign from being split or merged differently across systems. |
| Placement ID | The page group, package, ad slot, size, and placement context eligible for delivery. | Separates inventory quality from campaign-wide averages. |
| Creative ID | Message, format, size, version, offer, language, and approval date. | Prevents a winning message from being confused with a better placement or destination. |
| Destination ID | Landing page, form path, destination action, and page version active during the flight. | Separates media response from page quality and conversion friction. |
| Audience rule | Eligibility, exclusion, targeting, suppression, retargeting, CRM, lookalike, or contextual rule. | Shows whether high response may reflect pre-existing intent or reachability. |
| Flight window | Start and end dates, timezone, pacing changes, paused periods, and makegood windows. | Prevents timing, seasonality, or outage effects from being hidden in a total. |
| Comparison cell | Holdout, matched market, prior period, business-as-usual baseline, or explicit no-comparison flag. | Keeps descriptive reporting separate from lift language. |
| Primary outcome | The one main event or survey measure selected before results are visible. | Reduces post-flight metric shopping. |
Required event fields
Every downstream event does not need every advertising field, but it should carry enough context to be joined back without guessing.
| Event layer | Required fields | Readout risk if missing |
|---|---|---|
| Ad delivery | Campaign ID, placement ID, creative ID, timestamp, device class, country or market, impression status, and measurable/viewable flags where available. | Served volume may be treated as comparable exposure. |
| Click or visit | Campaign ID, creative ID, destination ID, click timestamp, landing timestamp, referrer category, session ID, and URL parameter set. | Traffic quality may be credited to the wrong source or page. |
| Engaged session | Session ID, destination ID, engagement rule, time threshold, scroll or interaction threshold, and duplicate rule. | Low-quality visits may be reported as meaningful response. |
| Lead or signup | Event ID, source trail, form version, duplicate flag, qualification status, disqualification reason, and follow-up status when available. | Raw form fills may be treated as qualified demand. |
| Sale or pipeline step | Outcome ID, outcome source, value basis, conversion window, match method, unmatched count, and duplicate rule. | Matched outcomes may be overstated as incremental outcomes. |
| Survey response | Sample source, exposed/control flag, recruitment path, field date, question version, weighting status, and base size. | Survey movement may be generalized beyond the measured sample. |
Naming rules
Use stable IDs, not presentation labels.A name can change in a deck. An ID should survive trafficking, analytics, dashboard exports, and billing records.
Separate format, message, and destination.A single creative name should not hide size, offer, call to action, and landing page. Those fields answer different measurement questions.
Keep outcome words out of campaign names.Names such as "high-intent lead driver" encourage the report to assume what it still needs to test.
Version material changes.Creative swaps, landing-page edits, audience expansions, tracking changes, and paused delivery should create visible change notes.
Define missing values.Blank, unknown, not applicable, unavailable, filtered, and suppressed mean different things. Treating them as the same value can create fake precision.
Preflight QA
| Check before launch | Pass condition | Downgrade if missing |
|---|---|---|
| Can every placement be identified? | Each public ad slot or sponsorship unit has a reporting key, size set, and context label. | Report only package-level delivery, not placement winners. |
| Can creative be separated cleanly? | Each creative has a unique ID with message, size, destination, and version fields. | Do not call a message or format the winner. |
| Can traffic be tied to destination quality? | Landing page, form path, page version, and URL parameters are visible in analytics. | Do not treat visits or leads as a pure media effect. |
| Can audience selection be audited? | Eligibility, exclusions, prior behavior, and targeting rules are recorded before exposure. | Do not treat stronger audience response as media-caused lift. |
| Can outcomes be deduped? | Event IDs, duplicate rules, match windows, and unmatched counts are documented. | Report observed outcomes with quality caveats. |
| Can the comparison be protected? | Holdout, matched market, prior period, or no-comparison status is locked before results. | Use descriptive language, not causal language. |
Readout join map
A clean readout does not need to force every signal into one score. It should show which joins are strong enough for which claim.
| Report question | Join needed | Strongest supportable claim |
|---|---|---|
| Did the campaign run where planned? | Campaign, placement, creative, date, device, and market. | The campaign delivered in the planned contexts and windows. |
| Was exposure quality acceptable? | Eligible impressions, measurable impressions, viewable impressions, invalid-traffic filters, and frequency distribution. | The measured exposure quality met or missed the planned threshold. |
| Which traffic was useful? | Click, session, destination, engagement, and duplicate rules. | The campaign produced observed traffic quality under the stated definitions. |
| Which leads were useful? | Source trail, form version, duplicate status, qualification status, and follow-up status. | The campaign produced reported leads or qualified leads under the stated filter. |
| Which outcomes matched back? | Identity unit, match method, conversion window, unmatched records, duplicate rule, and outcome source. | Matched records showed observed outcomes under the join rule. |
| Did the campaign create lift? | Protected comparison, eligibility rules, assignment or matching method, outcome window, leakage check, and uncertainty. | The design estimates incremental effect inside the tested population and window. |
One-page handoff
The campaign owner should be able to send one handoff before launch that answers these questions:
- What decision will the readout inform, and what result would change that decision?
- Which campaign, placement, creative, destination, audience, and outcome IDs are final?
- Which fields must appear in delivery, analytics, lead, outcome, survey, or matchback exports?
- What comparison rule is protected before results are visible?
- What minimum delivery, sample, quality, and follow-up thresholds are needed before a slice is interpreted?
- Which outages, tracking changes, audience changes, or landing-page edits must be logged during the flight?
Pair with
Use the first-party signal readiness checklist, campaign tagging QA checklist, creative asset acceptance checklist, and landing page launch QA worksheet before this spec is finalized, then use this spec before the contextual package proof export template, private marketplace readout export sample, campaign reporting sample, and campaign readout QA checklist, alongside the campaign KPI dictionary, and during setup for the private marketplace campaign measurement checklist. For outcome joins, use the identity matchback checklist. When the decision needs causal evidence, write the incrementality test plan before launch.