Reloading

What it is

Reloading is an optional behavior that refreshes the current page immediately after consent is saved. It’s designed for sites where server-side cookies or tags are injected only on first render (e.g., PHP/SSR templates), so newly-allowed services can initialize cleanly once consent exists.

When you need it

• Your analytics/ads load from server-rendered templates and won’t start just because the banner unblocked them client-side.
• You rely on server-side cookies (set by PHP/Node, reverse proxy, CDN edge workers) that should be written only after the visitor consents.
• Some plugins/themes only print scripts at page load, not dynamically on consent events.

If your tags are fully client-side and tied to Cookie Compliance events/consent modes, you usually don’t need Reloading.

How it works (end-to-end)

1. Visitor selects choices and clicks Save (or your custom label).
2. Cookie Compliance stores consent (and logs it in the app when plan limits allow).

3. If Reloading is enabled, the banner triggers a location reload of the current page.

   On reload, your site renders with consent already present, so server-side code can:

   • print the correct scripts/SDKs,
   • set server-side cookies allowed by the chosen Access Level/Purposes,
   • receive updated Consent Mode signals (Google / Microsoft / Facebook) from the first post-consent render.