Pedidos de terceiros antes do consentimento

Porque isto importa

Mesmo que os cookies estejam bloqueados, pedidos de terceiros podem ainda transmitir IP, identificadores ou metadados da página antes da escolha do utilizador. Isso continua a criar risco de conformidade.

Como verificar manualmente

1. Load the page in incognito and inspect third-party requests before any consent action.
2. Group requests by provider: analytics, ads, chat, video, fonts, tag manager, consent platform.
3. Check whether requests are essential or optional for baseline site functionality.

Causas típicas

• Third-party scripts load from the page template before the CMP decides.
• Optional widgets self-initialize on page load.
• Consent only blocks cookies but not network requests or remote script fetches.

Correção no GTM

1. Move optional vendor tags behind consent conditions instead of firing on all page views.
2. Audit custom HTML tags that pull remote scripts directly.
3. Separate essential operational tags from analytics and marketing vendors.

Correção em WordPress ou plugins CMP

1. Review theme, plugin, and page-builder integrations that inject third-party widgets globally.
2. Disable auto-embed or auto-load features for optional tools until consent is granted.
3. Retest pages after cache purge and plugin optimization layers are cleared.

Correção genérica para developers

1. Defer optional third-party scripts until consent is granted.
2. Lazy-load integrations on user action where possible.
3. Replace non-essential always-on embeds with click-to-load placeholders.

Como confirmar que a correção funciona

• Confirm that only essential third-party requests remain before consent.
• Accept optional consent and verify optional vendors load only afterward.
• Run a fresh scan and compare the third-party request inventory.