Campaign reporting
Campaign status-window closeout register template
A status-window decision is only useful if the closed, preliminary, excluded, and next-review rows stay attached to the final readout. A closeout register turns delayed outcome maturity into a reusable evidence record.
Use this register after the status-window checklist has named the delayed evidence lanes. It is built for contextual display, sponsorship, lead generation, matched-outcome, survey-supported, and private marketplace campaigns where lead status, matchback, attribution, sales follow-up, or survey fields close on different clocks.
What the register preserves
The register is the durable row set behind the closeout note. It lets a reader reopen the final language and see which evidence was mature, which rows were excluded, and what still needs review.
| Closeout problem | How it appears | Register control |
|---|---|---|
| Final words outrun final fields | The readout says outcomes are final while lead status, matchback, or survey fields are still filling in. | Require one row per status window with the maturity threshold and accepted review date. |
| Excluded rows disappear | Incomplete, invalid, low-volume, reversed, or off-scope rows are removed from charts without a durable note. | Store excluded row labels beside the allowed claim and the reason for exclusion. |
| Different clocks get pooled | Seven-day attributed outcomes, 30-day conversions, sales follow-up, and survey fielding are treated as one final date. | Separate the window type, start trigger, end rule, and next review for every evidence lane. |
| Comparison limits get lost | A mature descriptive outcome is later repeated as lift because the counterfactual limit was not carried forward. | Keep the comparison rule, unavailable claim, and next-test requirement in the same export row. |
| Next flight inherits uncertainty | The same missing status or repair condition returns because the closeout row never reached the next brief. | Assign a follow-up owner, next review date, and carry-forward action before the record is archived. |
Minimum register fields
A closeout register should be narrow enough to maintain, but specific enough to prevent claim drift. These fields are the minimum useful set.
Closeout ID
A stable ID that connects the campaign, package, window type, review date, and readout version.
Window type
Lead status, sales follow-up, identity matchback, attribution lag, survey fielding, reversal cleanup, or comparison readiness.
Eligible scope
The package, placement, creative, device, destination, audience, outcome, or comparison rows covered by the window.
Start trigger
The event that starts the clock, such as impression, click, form submit, assignment, purchase date, fielding date, or campaign close.
End rule
The elapsed-days rule, calendar date, final system run, fielding close, or accepted status threshold.
Maturity threshold
The coverage, match completion, sample, duplicate review, outcome-status, or comparison rule needed for final language.
Closeout state
Final, final with exclusions, preliminary, not comparable, retest required, causal test required, or hold.
Included and excluded rows
The rows used in the final sentence and the rows removed because they were missing, invalid, low volume, unresolved, or off-scope.
Claim boundary
The final allowed claim, the stronger unavailable claim, and the next evidence needed before wording can change.
Export column set
Use stable column names when the register moves into a workbook, dashboard, or campaign record. Put claim boundaries beside evidence fields so the row cannot be reused without its limits.
| Column | Sample value | Why it matters | Do not use it to claim |
|---|---|---|---|
| closeout_id | status-2026-q3-guide-lead-01 | Connects the status row to the readout, memo, archive, and follow-up tracker. | That the row is final without checking closeout_state. |
| window_type | lead_status | Separates lead review from attribution, matchback, survey, or comparison clocks. | That all outcome fields mature at the same pace. |
| eligible_scope | verified guide placements; desktop and tablet forms | Names the rows allowed into the final sentence. | That mobile, pooled, or off-scope rows reached the same status. |
| start_trigger | form_submit_date | Shows when the window begins for each row. | That a campaign end date is always the right clock. |
| end_rule | 14 days after form submit | Defines when status can be reviewed as mature. | That earlier meetings make status final. |
| maturity_threshold | 80% accepted status coverage | Creates an explicit gate before final language. | That partial coverage supports all-row lead-quality claims. |
| evidence_snapshot | 82% status coverage; 7 duplicate rows removed | Preserves the review facts behind the state label. | That volume alone proves quality or lift. |
| excluded_rows | mobile destination repair row; missing source field rows | Keeps excluded evidence visible for the next flight. | That exclusions are failures, wins, or irrelevant. |
| closeout_state | final with exclusions | Controls whether the row can use final or preliminary wording. | That every related evidence lane is final. |
| final_allowed_claim | Included rows reached accepted lead-status coverage. | Gives the readout a copy-safe sentence. | Incrementality, all-inventory quality, or unrestricted renewal. |
| unavailable_claim | The campaign produced qualified leads across all devices. | Names the stronger sentence that remains unsupported. | That the stronger claim is merely pending approval. |
| next_review_date | 2026-07-15 | Turns preliminary and carried-forward rows into a real follow-up moment. | That unresolved status can be ignored after the readout. |
Sample register rows
These rows show structure only. They do not describe a real advertiser, publisher, platform, or campaign.
| Closeout ID | Window | Eligible scope | Threshold | State | Excluded rows | Next review | Allowed claim |
|---|---|---|---|---|---|---|---|
| status-guide-lead-01 | Lead status | Guide-package form submissions from verified desktop and tablet rows. | 80% accepted status coverage. | Final with exclusions | Mobile repair row and records without source fields. | Before next launch. | Included rows reached accepted lead-status coverage. |
| status-context-match-02 | Identity matchback | Eligible source-coded visitors joined to CRM outcomes. | Final match run, duplicate rule, and unmatched count recorded. | Final | Rows below privacy or minimum-count thresholds. | At renewal archive. | Matched outcomes were observed for eligible rows under the stated match limits. |
| status-readiness-sales-03 | Sales follow-up | Qualified visit rows routed to follow-up queue. | Disposition complete for each included row. | Preliminary | Rows not yet contacted. | 21 days after assignment. | Traffic response is visible; sales-readiness language is not final. |
| status-reporting-survey-04 | Survey fielding | Exposed and comparison respondents from the same flight. | Final sample, balance, and uncertainty fields accepted. | Retest required | Underfilled comparison cell. | Next measurement brief. | Survey movement is directional and does not support renewal by itself. |
| status-package-compare-05 | Comparison readiness | Renewed package rows with prior-period baseline only. | Matched baseline or holdout defined before lift wording. | Causal test required | No rows excluded; comparison remains descriptive. | Before next test plan. | Observed response is final; incremental impact is not established. |
State-to-action rules
The closeout state should tell the team what happens next. A register that only records dates will not protect the final claim.
| Closeout state | Register action | Readout wording | Carry forward |
|---|---|---|---|
| Final | Lock the evidence snapshot, reviewer, and allowed claim. | Use final descriptive language for the eligible scope. | Archive the row with no open issue unless next testing is required. |
| Final with exclusions | Keep excluded rows beside the final sentence. | Use final language only for included rows. | Move excluded rows into the next brief or archive condition. |
| Preliminary | Set the next review date and missing evidence field. | Use early-read wording with no final outcome claim. | Track owner and due date until the window closes. |
| Not comparable | Split the affected rows or keep them out of pooled totals. | Describe each row separately or avoid the pooled conclusion. | Carry a reporting-grain repair into the next flight. |
| Retest required | Record the minimum delivery, status, or balance rule that failed. | Use directional language and avoid budget-shift wording. | Write the retest requirement into the next measurement brief. |
| Causal test required | Preserve the descriptive outcome and the missing counterfactual. | Use observed-response language only. | Open a holdout, matched baseline, or test-plan requirement. |
| Hold | Flag the row as decision-blocking and name the missing field. | Narrow the readout or defer final language. | Do not approve the next decision until the blocker is resolved. |
Register closeout note
End each register update with a short note that can be moved into the readout, memo, archive, or follow-up tracker without upgrading the evidence.
Recommended structureCloseout row [closeout ID] covers [eligible scope] for [window type]. The window opened on [start trigger] and closes under [end rule]. The maturity threshold was [met, missed, or partially met] based on [evidence snapshot]. Include [included rows] and exclude [excluded rows] from final wording. The allowed claim is [bounded sentence]. The unavailable claim remains [stronger sentence] until [next evidence requirement] is complete. Review again on [next review date].
Register QA checklist
- Does every delayed evidence lane have a closeout ID, window type, eligible scope, start trigger, end rule, threshold, and reviewer?
- Are included rows and excluded rows visible beside the final allowed claim?
- Does each preliminary, not comparable, retest, causal-test, or hold row have a next review date?
- Is the unavailable stronger claim written clearly enough to prevent accidental reuse?
- Can the row move into the renewal memo, evidence archive, and follow-up tracker without losing the comparison rule?
Pair with
Use this register after the campaign status-window closeout checklist and before the campaign renewal evidence archive. Pair it with the private marketplace readout export sample for row-level reporting structure, the private marketplace reporting field dictionary for stable column names, the campaign readout QA checklist before final report language, the campaign reporting worksheet for meeting notes, the campaign issue log and renewal register when weak lanes need owners, the campaign renewal memo template for final action language, the campaign renewal follow-up tracker when preliminary rows move into the next flight, the private marketplace renewal scorecard when closeout rows affect renewal, the outcome quality scorecard for lead and matchback interpretation, the attribution window and conversion lag checklist for credited outcomes, the identity matchback checklist for joined outcomes, and the incrementality test plan template when mature descriptive evidence still needs causal support.