A broken conversion tag can quietly damage a healthy account. Smart Bidding learns from your conversion data, so bad data leads to bad bids. Google Ads data exclusions let you tell the system to ignore a stretch of unreliable data. This guide explains when to use them, how to choose the dates and what to expect once they are applied.
In this guide: Why Tracking Outages Hurt Smart Bidding | When to Use Google Ads Data Exclusions | How to Choose the Right Dates | What to Do After You Apply an Exclusion | Habits That Protect Your Data | Who Should Watch for Outages | A Simple Outage Routine | Frequently Asked Questions | Final Thoughts
Why Tracking Outages Hurt Smart Bidding
Automated bidding treats conversions and conversion values as the truth. If the tag stops firing, Google sees clicks with no results and may cut bids. If the tag fires twice, it sees inflated results and may raise bids too far.
Both mistakes cost money. The longer the bad data feeds the model, the longer the recovery. Our guide to Smart Bidding explains how these strategies learn, and why clean inputs matter so much.
When to Use Google Ads Data Exclusions
Google’s help page on data exclusions for conversion data outages describes the situations that qualify. They include:
- Conversion tracking that was broken for a period of time.
- A conversion tag placed incorrectly, which inflated or deflated your counts.
- A temporary inability to upload offline conversion data.
The page also says data exclusions are not supported in Hotel and Travel campaigns. For a planned event such as site maintenance, you can set the exclusion before it starts. Future-dated exclusions typically take effect within a day.
How to Choose the Right Dates
This is where most mistakes happen. Exclusion dates apply to clicks, not to conversions. A conversion that was recorded today may belong to a click from last week.
So you need to account for your conversion delay and exclude every day that had affected clicks. Google suggests aiming to exclude at least 90% of the clicks tied to the affected data.
A hypothetical example
Say an offline upload failed from the 15th to the 18th of a month, and your conversion delay is 5 days. Clicks from the 10th onward could be linked to conversions that never arrived. Google’s own example excludes the 10th through the 18th for this reason. The numbers here are hypothetical, so use your own delay.
Start and end times follow the time zone of the account. Exclusions can be applied at manager or sub-manager account level, which helps when one tag issue touched several accounts.
What to Do After You Apply an Exclusion
Apply the exclusion as soon as you find the problem. After that, expect some movement. Bids and spend may drop for a short time. Google notes that past-date exclusions usually settle within a few days. If a week or more of clicks was affected, the swings can last one to two conversion cycles.
- Check your targets. Adjust CPA or ROAS targets so they match the performance you want, and confirm budgets are at acceptable levels.
- Ease targets if spend drops. Google says lowering ROAS targets can help bids and spend recover.
- Restore targets later. Once the exclusion has taken full effect, bids adjust quickly. Raise ROAS targets back to your desired level to avoid overspending.
Habits That Protect Your Data
Google gives clear cautions. Do not use exclusions often or for long periods, because that can hurt Smart Bidding. Do not remove an exclusion after it is applied, since removal can cause unwanted swings.
Backfilling accurate conversion data is generally not recommended, because it can affect Search and Shopping bidding. If you set an exclusion, you may backfill for reporting only. Wait at least 5 days first, and keep the exclusion in place.
The better fix is to catch problems early. Review your conversion tracking after every site release, tag change or checkout update. Watch for sudden drops in conversion counts or a conversion rate that looks too good. A regular account audit should include a tracking check, so outages do not run for weeks.
Who Should Watch for Outages
Tracking problems often start with a change made by someone outside the ad team. A developer updates the checkout, a plugin is replaced or a consent banner is edited. Each of these can stop a tag from firing without any visible error.
Ask the people who maintain your site to tell you before they release changes that touch forms, checkout or thank-you pages. A short message in advance lets you test the tag straight after release, and it lets you set a future-dated exclusion if a gap is unavoidable. Daily checks of conversion counts take only a minute and often catch trouble within a day.
A Simple Outage Routine
- Record the first and last day the data looked wrong.
- Subtract your conversion delay from the start date to find the first affected click day.
- Apply the exclusion to cover those dates.
- Fix the tag or upload, and test it with a real conversion.
- Review bids, spend and targets daily until results settle.
Data exclusions protect the conversion data your bidding learns from, so check which actions count in our guide to primary vs secondary conversions.
Frequently Asked Questions
Can I use data exclusions for a short, planned outage?
Yes. Google says you can set an exclusion in advance for a known future event, such as maintenance, and it typically takes effect within a day.
Should I remove the exclusion once the data is fixed?
No. Google advises against removing an exclusion after it has been applied, because that can cause unwanted performance swings.
Do data exclusions work in every campaign type?
No. The help page says they are not supported in Hotel and Travel campaigns. Check the page for the current list of limits.
Final Thoughts
Google Ads data exclusions are a repair tool for real outages. Use them quickly once you spot the problem, cover every affected click day and give bidding a few days to settle. Then spend your effort on preventing the next break.
Want expert help with your account? See our Google Ads management service.