Skip to main content

Cookie Consent: Intro

Tracking the visitors of your Heyflow Flow is a very effective way to optimize your flow and your conversion rates, or even remarket certain services to visitors after leaving your website. As the EU and other countries outside the EU passed strict data protection laws like the GDPR, collection of personal data underlies certain restrictions.

‌

While clickflows built with Heyflow are out-of-the-box GDPR-compliant, you need cookie consent of your users to collect personal data when integrating analytical tools or want to use remarketing campaigns.

💡 Google Ads needs visitor consent to use your conversion and remarketing data in the EU. Without a cookie banner, Google only receives limited data, even if GA4 still shows visits.

In this article, you'll learn about all possibilities of integrating a Cookie Consent to your heyflow:


Heyflow's Cookie Consent

It's never been easier (and more stylish) to be GDPR-compliant. With the Heyflow Cookie Consent enabled, tracking pixels (e.g. Meta, LinkedIn, TikTok) only load after the visitor gives consent. Google Tag Manager and Google tags load right away in Google Consent Mode with all consent types set to denied. They only use cookies and send full data once the visitor accepts.

Click here to learn more about our Cookie Consent.

Heyflow-Screenshot – Cookie-Zustimmungseinstellungen


Openli Integration

With our Openli integration (previously Legal Monster) you can easily add the provided Cookie Consent to your heyflow. Click here to learn more about our Openli integration.


Custom Integration via Code

If you already have a different Cookie Consent provider, don't worry. You can also integrate your Cookie Consent script via HTML or our Head Code section.

⭐ Adding your own cookie consent script via Head Code or HTML requires the Coding Bundle (included in Scale) or the legacy Business plan. See Customize your funnel with Head Code.

Example: Cookiebot by Usercentrix can be implemented via a script in the Head Code:


Cookie Consent & Embedded Flows

When embedding a flow on your website, please note:

  • Heyflow's built-in Cookie Consent will not be displayed in embedded flows.

  • If you use our Cookie Consent in an embedded flow, analytics integrations like GA4 or Meta Pixel won’t load correctly.

  • This is because the consent logic is handled on your website — not inside the embedded Heyflow.

What we recommend:

  • Use your website’s cookie solution (e.g. via a cookie banner or manager).

  • Conditionally load the embedded Heyflow only after consent is given for the relevant category (e.g. marketing for Meta Pixel).

  • Implement tracking via Google Tag Manager (GTM) using dataLayer events, which Heyflow pushes regardless of consent state.

❗ We currently don’t support external cookie tools controlling script loading inside Heyflow.

💡 Alternative: If you want to use Heyflow's built-in Cookie Consent, we recommend connecting a custom domain and using the flow in a standalone format.

Did this answer your question?