Auto-blocking
Auto-blocking is a consent tool feature that recognizes tracking scripts and embeds as a page loads and holds them back until the visitor consents to their category, without the site owner marking each tag by hand.Prior consent means non-essential trackers must not run before the visitor chooses. The manual way is to mark each script with a neutral type and a category attribute, so the browser does not execute it until the consent tool swaps the type back; the guide on blocking scripts until consent shows that markup. Auto-blocking tries to do the same without edits, usually by watching the page for new script and iframe elements and comparing their sources with a list of known trackers.
It has limits worth knowing. The consent script has to load first, because a tag that is already in the HTML and runs before it cannot be stopped after the fact. Recognition depends on the list: a tracker it does not know, or one served from the site's own domain, passes through. And blocking a script does not remove cookies a previous visit already set. A cookie scanner run after setup is the way to check what still fires before consent.
Cookiequiet's auto-blocker holds scripts and iframes created by JavaScript, including those injected by tag managers and lazy loaders, from about 80 known trackers until consent, and trackers hard-coded in the HTML before its script need to be marked or moved, as the install guides explain. See prior consent for the legal side.