Fingerprinting antes del consentimiento

Por qué es importante

Las APIs relacionadas con fingerprinting pueden crear una superficie de tracking incluso si las cookies están limitadas. Si esas señales se activan antes de la elección del usuario, el problema suele ser más difícil de detectar que el tracking basado en cookies.

Cómo verificarlo manualmente

1. Identify which script executes canvas, WebGL, font, or device-probing APIs before consent.
2. Check whether the signal comes from analytics, fraud tooling, ad tech, or a custom script.
3. Confirm whether the script is essential or optional for baseline site functionality.

Causas típicas

• Fraud, attribution, or analytics vendors initialize immediately on page load.
• Custom anti-bot logic runs before the CMP decides.
• A vendor SDK bundles fingerprinting behavior you did not explicitly configure.

Corrección en GTM

1. Move optional vendors that perform browser fingerprinting behind consent checks.
2. Review custom HTML tags and vendor templates for immediate initialization.
3. Separate strictly necessary fraud-prevention logic from optional analytics or advertising tooling.

Corrección en WordPress o plugins CMP

1. Review plugins for analytics, ads, AB testing, and anti-fraud features that inject scripts globally.
2. Disable optional optimization or attribution modules until consent is granted.
3. Retest after plugin updates because SDK behavior can change over time.

Corrección genérica para desarrolladores

1. Defer non-essential SDK initialization until consent is granted.
2. For necessary risk controls, minimize scope and document why the behavior is essential.
3. Remove or replace vendors that cannot be configured to respect consent.

Cómo confirmar que la corrección funciona

• Confirm fingerprinting-sensitive APIs no longer run before consent.
• Re-test after Accept to ensure optional vendors still work when consent is granted.
• Run a fresh scan and compare the fingerprinting evidence before and after the fix.