Place Custom Loader cookie only after Cookie Bot user consent

Hello,

The cookie used by the Custom Loader Power-Up gets set regardless of user consent.
Because of AVG/GDPR Regulations we need to be able to set it after user consent.
We use the CookieBot CMP integration in GTM.

We’ve tried all ChatGPT suggested options (custom HTML scripts) but to no effect.
The cookie keeps being set without consent, eventhough strictly speaking it is just a Marketing purpose cookie, not an essential one.

Hope someone can help figuring this out.

Thanks!

@Frank_Litjens custom loader will not set the master cookie, it will look for it when loading but is not responsible for setting it. Therefore there’s nothing you can do from container or Stape side to change this

Hi Dan, thanks!
So the cookie being set without consent is something that can not be controlled in any way. Do I understand that correctly?

In that sense,
Does that make it a critical/essential cookie, like JSESSION for example, under GDPR/AVG?

Thank you

@Frank_Litjens short answer is I don’t know.

Cookie Keeper restores your cookies based on the master id, which in your case is cookie named ‘fp_cookie’. Cookie Keeper does not set the fp_cookie though, an only attempts to get it’s value.

So you want to understand first and foremost, where that fp_cookie is coming from.

Well, we have looked truly everywhere this cookie could come from and it is not set by the server or our gaming platform.

We needed it to setup Stape and codewise it only shows up in the Custom Loader script and its settings within Stape.

So we truly don’t know any other place it could come from, but we do need it to be set only after user consent through Cookiebot.

Hope you can help us out.
Thank you.

@Frank_Litjens I repeat, custom loader does not set the cookie in question. It only grabs it’s value, if it was setting it - a) it would be demonstrable, and it isn’t b) Cookie Keeper would loose it’s core value, because master cookies needs to be such ones that passes all ITP checks.

You can replace fp_cookie with anything else in your loader and it will not affect the presence of ‘fp_cookie’