Cookiebot and Runner
Runner writes, versions, serves and records the visitor notice itself, and checks each listed site's main address on a schedule for what is actually running. Change the organization policy once and every property follows, while a site can still set its own collection level and notice, marked as an override.
What it is usually bought for
Change one visitor notice and update every site
The job, on its own page: Change one visitor notice and update every siteBuilt into Runner
- One update reaches every site through the embed already in place
- A scheduled check of each listed site's main address, with a review queue for what is running but not declared
- A preference centre visitors can return to
- Every choice kept with the version they saw
Worth knowing
The scheduled check reads a site's markup and headers on a few pages — it does not run the page, so a tag a tag manager loads at runtime is only governed once you declare it, and a site you have not listed is not checked at all. The ad industry's TCF string is built in but stays off until Runner's own CMP registration with IAB Europe is complete.
When to keep Cookiebot
- If Cookiebot does this job well for you today, keep it. Nothing on this page asks you to move.
- Runner stops where the bound above says it stops, and a tool you already run may cover exactly that.
Use what already works
List the services already running on each site so the visitor's choice can govern Runner's collector and the processors you declare. The scheduled check shows what it found beside that list; a person confirms a finding before the notice changes. Existing tag and analytics tools can stay in place.
CookiebotOneTrustOsano
Trademarks of their owners. No affiliation or endorsement.