Practical framework / 5 MIN READ
Respond to a conversion-data outage with a bounded incident plan
Repair collection, identify the affected click population and evaluate supported bidding protections.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A tracking outage can feed incorrect signals into automated bidding while leaving real customer behavior unchanged. The response should preserve evidence, protect the campaign and distinguish data repair from reporting interpretation.
What you will leave with: Prepare an outage packet with scope, timing, supported intervention and verification steps.
Use this when
- A conversion tag stopped firing after a release.
- An import failure causes missing or incorrect conversion values.
This is incident planning for authorized operators, not a blanket recommendation to exclude disappointing performance.
Confirm the measurement incident
Compare the suspected break with independent operational evidence and recent releases. Establish whether outcomes stopped occurring, stopped being recorded or stopped reaching the advertising platform. Those conditions require different responses.
Record the first known bad timestamp, last known good timestamp, affected actions, devices and campaigns. Preserve logs and current settings. Avoid changing targets immediately to compensate for a number that may be wrong; first identify the measurement failure and any urgent spend or customer risk.
Check the supported protective tool
Google describes data exclusions as an advanced way to reduce the impact of incorrect conversion data on eligible Smart Bidding strategies. It specifies click-based scope and distinguishes bidding-data treatment from reporting. Check the current campaign support and recovery restrictions with the implementation owner.
The relevant click period can extend beyond the apparent outage because outcomes arrive after interactions. Use observed conversion delay to frame that period. Do not apply an account-wide exclusion when evidence supports only a narrow action or device issue without examining the consequences.
Separate repair, protection and historical reporting
Assign an owner to restore the underlying tag or import. Separately decide, with authorization, whether the supported bidding intervention is appropriate. Finally decide what can be corrected or annotated in historical reports. These tasks have different effects and should not be treated as one repair button.
Follow current provider guidance before backfilling, removing exclusions or resubmitting records. A plausible recovery step can interact with optimization. Never invent conversions to make the graph smooth, and never exclude valid low performance merely because it is inconvenient.
Verify recovery and close the incident
Test legitimate outcomes through the repaired path and confirm they reach the intended destination with correct values. Monitor delivery and mature results while preserving the incident annotation. A tool intended to reduce disruption cannot guarantee no performance fluctuation.
Document the cause, scope, intervention and verification evidence. Add a focused detection check so the same failure is noticed sooner. Close the incident only when the responsible owners agree that collection is restored and any remaining analytical limitations are clear.
Make the reasoning concrete.
A hypothetical retailer removes a conversion tag during a website release. Orders continue in the store system, but advertising conversions fall to nearly zero. The failure affects mobile checkout for two days, with some purchases linked to earlier clicks.
Treat the drop as real demand loss
Opening: Raise or lower targets based on the broken report.
Hypothesis: The campaign’s visible signal has changed.
Risk: The operational orders indicate a measurement incident.
Use a scoped response
Opening: Repair the tag and assess the affected click period for a supported intervention.
Hypothesis: This addresses both collection and bidding-data consequences.
Risk: The exact window and recovery steps require current platform guidance.
Protect the campaign through an approved incident plan, then verify real outcomes end to end and annotate the affected reporting period.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Evidence
What proves this is incorrect measurement?
Scope
Which actions, devices and campaigns are affected?
Clock
Which clicks could receive the missing outcomes?
Intervention
What supported protection is authorized?
Recovery
How will collection and reporting limits be verified?
Watch for the wrong conclusion.
- Using exclusions to hide genuine poor results.
- Confusing bidding protection with deleted report data.
- Ignoring conversion delay when defining scope.
- Backfilling or removing protections without checking documented consequences.
Your next action
Create a conversion-outage runbook that assigns separate owners for collection repair, bidding protection and reporting correction.
Sources & scope
Frameworks, worksheets and hypothetical examples are original editorial synthesis. Linked primary sources support only the stated concepts. Source checking is not an independent audit of effectiveness. No named human author or reviewer is claimed.
- Google Ads Help: About data exclusions →Primary platform documentation · Supports: Describes an advanced Smart Bidding response to incorrect conversion data, click-based scope and the distinction from reporting. Availability and recovery restrictions require current review.