cookies-analytics

GDPR-compliant GA4 setup delays script loading until users grant consent through a banner. This Skill provides a reusable consent component, stores user choice in localStorage, and injects GA4 dynamically only after explicit approval, ensuring analytics tracks only consented traffic.

Loading GA4 before consent violates GDPR by tracking users without permission. Delaying GA4 injection until after consent respects privacy regulations and gives users control over whether their behavior is monitored, reducing compliance risk.

Yes. This Skill provides a ready-to-use consent banner component that presents essential vs. all-consent options, integrates into your app layout, and wires GA4 loading to the user's choice, eliminating manual consent management.

Consent decisions are stored in browser localStorage as persistent state. This allows your app to remember user preferences across sessions and conditionally load GA4 on return visits without re-prompting.

Link your consent banner and GA4 setup to formal privacy documentation (e.g., a Datenschutz page). This Skill includes guidance on connecting consent references to your data policy, creating a complete audit trail for regulatory compliance.

Yes. Store your Google Analytics ID as an environment variable rather than hardcoding it. This keeps sensitive configuration out of version control and enables dynamic script injection tied to consent state.