Check the availability of this feature and its frequencies in your plan.
The Scheduled Scanner lets the Tag Scanner run automatically, at the frequency you choose, keeping the Tags and cookies on your cookie banner always up to date. In this guide:
How to choose the scanner frequency;
What the frequency changes for consent;
Who receives the report from each scan;
How to track what changed in History of Changes.
Scanner frequency
In Tag Scanner > Scheduled Scanner, under Scanner frequency, choose an option:
Manual — the scanner runs only when you trigger it.
Weekly — repeats every 7 days.
Monthly — repeats once a month.
Every 45 days — repeats every 45 days.
Every 60 days — repeats every 60 days.
The scheduled scan starts counting from the day you save the setting.
Which frequency to choose
The longer intervals (every 45 or 60 days) are designed for teams that want to space out their tag and cookie scans. As a reference: weekly or monthly for sites with high service turnover (campaign pixels, new marketing tools, A/B tests); every 45 or 60 days for more stable sites that rarely add or swap services.
📢 Important: if you choose the manual scanner, we recommend running a new scan every three to six months. Tags and services may update their cookies, and periodic scanning keeps your cookie banner and Cookie Policy aligned with your site.
Remember that the scanner repeats within the chosen frequency, so you'll need to access the platform to check and validate the scan results (all identified Tags and their categories).
What this changes for consent
Whenever the scanner finds a new Tag, the previous consent no longer covers every service on the site, and the cookie banner is shown again to returning visitors — expected, correct behavior that keeps consent specific and informed. With longer intervals, new Tags are detected less often, so this new-Tag re-display trigger fires less frequently. In practice, for sites with few service changes, this can mean fewer consent re-collections over time.
This does not change AdOpt's default consent lifetime (60 days, adjustable on Pro plans and above under Disclaimer settings > AdOpt cookie lifetime). Scanner frequency only controls how often new Tags trigger a fresh request — not the base renewal window.
Report recipients
You choose who receives the report from each scheduled scan, disclaimer by disclaimer. Under Report recipients > Recipients, select the organization members who should receive it. By default, the Owner, the DPO, and whoever triggered the scan are notified. With recipient selection, a single organization can have banners with different people responsible for tag monitoring — IT on one banner, the DPO on another — without needing a separate organization per person.
Notification on each scan
After each scan, AdOpt emails the report recipients to let them know whether new Tags or cookies were identified since the previous scan. When there's something new, we recommend:
Open the platform;
Go to the History of Changes tab (under Tag Scanner) to compare what changed against the previous version;
Categorize the new Tags — remember that unknown Tags must be categorized before they appear on your cookie banner;
Save your changes.
This keeps your cookie banner and Cookie Policy aligned with your site.
History of Changes
The History of Changes tab (under Tag Scanner) keeps a versioned record of every saved scan of your cookie banner. It's where you track how your site's set of Tags and cookies has evolved over time — especially useful after you receive the notification from a new scan.
The screen shows the current version at the top and a table with:
Version — the version number (e.g., v15.0), created with each new saved read.
Date changed — when that version was recorded.
Tags — number of Tags identified in that version.
Cookies — number of cookies identified in that version.
Actions — opens that version's actions.
By comparing two versions, you can quickly spot whether new Tags or cookies appeared since the last read. If something new showed up, go back to the Tags Categorization tab, categorize the new Tags, and save.
Next steps
For the essential setup (scanning and categorizing your Tags), see the main Tag Scanner guide. For logged-in environments, the Authenticated Scanner; and to understand tag blocking, the Tag Blocking guide.