Which iubenda feature writes the policy and which handles a choice?
The Privacy and Cookie Policy Generator builds the document. Privacy Controls and Cookie Solution shows the banner and handles preferences. Configuring the policy alone leaves the browser behavior to your site.
Start with the services already on your site. Check that each relevant entry in the notice matches what the service actually does.
When does iubenda hold back a browser tag?
The banner needs an integration for scripts you intend to hold before a choice. iubenda documents automatic blocking, and its product guide treats prior blocking as a setup step.
Verify the behavior on the pages where the tags are loaded, including routes that behave differently. A banner or a scan report by itself cannot show what every visitor’s browser sent.
Which traffic number matters for iubenda?
The pricing page lists Essentials per site with 25,000 monthly pageviews included. Check how loads and reloads count, and confirm how your plan handles usage above the allowance.
iubenda describes extra charges on its pricing page and documents a paused-banner state when an allowance has been exceeded. If the banner is a dependency, confirm the rules for your account rather than budgeting from visitor counts.
What should you retain if you change tools?
Keep your own list of services, notice decisions and which tags each choice controls. iubenda’s plan FAQ says continued use of a paid policy is unavailable after the paid plan is not renewed.
Before replacing it, plan the replacement notice and how the preference control should behave after the switch.
How do you spot a mismatch before setup?
Draw a fictional workshop notice and an optional audience counter. Use no account or deployed page.
- Add the counter to your inventoryDescribe what it measures and mark its proposed preference category.
- Walk through a declineIf your diagram still shows the counter starting after decline, change the tag behavior you planned. Editing the notice alone cannot fix it.