A data exclusion is a Google Ads setting that tells Smart Bidding to ignore conversion data from a specific date range, because the data from that period is wrong. You use it when conversion tracking broke or misreported, so the bidding system does not learn from figures that never reflected reality.
How a data exclusion works
Smart Bidding sets bids by learning from past clicks and conversions. If tracking stops recording conversions for four days, the system sees clicks with no results and concludes those searches stopped working. It then lowers bids, sometimes sharply. If tracking double-counts, it sees inflated results and bids up.
A data exclusion removes that period from the system’s learning. You create one in the Tools menu under the bid strategy advanced controls, choose the start and end date and time, and pick which campaigns or campaign types it applies to. Exclusions can cover dates in the past, so you can add one after discovering a problem, though the sooner the better.
It changes only what Smart Bidding learns from. Your reports still show the period as it was recorded, and it does not restore the missing conversions. It is also different from a seasonality adjustment, which tells the system to expect a short-term change in conversion rate, such as a flash sale, rather than ignore data.
Why it matters
Tracking breaks more often than most businesses realise. A website redesign drops the Google tag from the thank-you page, a cookie banner update blocks tags by mistake, or a form plugin change stops the confirmation page loading. For an account on target CPA or Maximise Conversions, a week of zero recorded conversions can undo months of learning and push bids down just as the fix goes in.
Adding an exclusion protects the account from that damage. For a UK business spending a few thousand pounds a month, it can be the difference between a quiet recovery and several weeks of lower enquiries while the system relearns.
Common mistakes
- Using exclusions for periods that were simply poor, such as a slow August, which hides genuine information from the system.
- Not noticing the outage for weeks, so the exclusion is added after the damage is done.
- Excluding a much wider range than the problem covered, throwing away good data.
- Applying the exclusion to all campaigns when only one conversion action or site section was affected.
- Using exclusions often enough that Smart Bidding has too little clean history to work with.
How to act on it
Watch conversion volumes daily or set an alert, so an outage is caught within a day or two. When one happens, fix the tracking first and confirm it works with a test conversion; my walkthrough on how to check your conversion tracking works covers the tests. Then add a data exclusion covering the exact start and end of the broken period, applied only to the affected campaigns.
Be precise about timing. If the tag disappeared when a new site went live at 2pm on a Tuesday and was restored at 10am the following Monday, use those times rather than whole days, so the clean data either side is kept. Bear in mind conversion lag too: conversions from clicks before the outage may still have been lost if they were due to happen during it.
Keep a note of every exclusion in your change log so later performance reviews make sense. Spotting tracking failures early and protecting bidding from them is routine in my Google Ads account management.