The issue you’re experiencing is standard behavior for cookie consent tools - when users reject or ignore consent, third-party analytics scripts like PostHog are properly blocked to maintain GDPR compliance.
Here’s how to fix this while still capturing essential page view data:
GTM Integration (Recommended)
Set up GTM with Consent Pro integration
Create the “Consent Mode Init” tag
Set up the “Analytics Cookies” trigger with event analytics-activated
Configure PostHog in GTM
Add PostHog as a tag in GTM (not directly in Webflow)
Set the trigger to “Analytics Cookies”
Add consent check: analytics_storage = granted
Direct Script Management Alternative
You could also try a simpler approach by moving the PostHog script to your site settings and adding consent attributes:
Add PostHog script to Site Settings → Custom Code → Footer
Add these attributes to the script tag:
<script type="fs-consent" fs-consent-categories="analytics">
// PostHog code here
</script>
This way, PostHog will only load when users consent to “Analytics” while essential page functionality remains unaffected.
Could you share your staging URL once implemented so we can verify the setup? If you need more specific help with implementation, @Support-Luis or @Support-Pedro can assist further.
We want to capture ‘Page views’ and ‘Clicks’ at all times, irrespective of ignore or reject on cookie consent. How do we structure Posthog script to do that?