Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cookies are being set before consent #135

Closed
ShannonTrust opened this issue Aug 8, 2024 · 7 comments
Closed

Cookies are being set before consent #135

ShannonTrust opened this issue Aug 8, 2024 · 7 comments
Assignees
Labels
bug Something isn't working sla

Comments

@ShannonTrust
Copy link
Collaborator

Please select the priority level by adding one of the following labels to this issue?

Priority-3 (Normal e.g. Functionality is not working for a subset of users)

Describe the bug and the expected behaviour.

We've had our monthly report from Cookiebot and it's come back again saying cookies are being set for users before they can consent. Cookiebot is a bit of a minefield for me so I have no idea where to make the changes. Would you be able to look into this, please?

Steps To Reproduce

This is the report for the full details:
Cookie scan report August 2024.pdf

Screenshots or a link to a Loom Recording

No response

What browsers are you seeing the problem on?

No response

Anything else?

No response

@ShannonTrust ShannonTrust added bug Something isn't working sla labels Aug 8, 2024
@cyberteenie
Copy link
Member

@ShannonTrust - we will have a look and get back to you on this! Thanks for flagging

@AbdelhalimOJ
Copy link
Collaborator

AbdelhalimOJ commented Aug 27, 2024

Progress Status:

  • Ensure Proper Script Order: Make sure the Cookiebot script is the very first script to load on your website. This might involve adjusting the order of scripts in your website’s section.
  • Classify Unclassified Cookies: Log in to your Cookiebot account and manually classify any unclassified cookies. This involves providing a purpose description and categorizing them correctly.
  • not applicable - Handle Server-Side Cookies: If there are any server-side cookies being set, you will need to modify your server-side code to delay setting these cookies until after user consent has been granted.
  • not applicable - Review Google Tag Manager Configuration: Check your GTM setup and ensure that all tags are configured to respect the Cookiebot consent mode. This can typically be done by configuring triggers in GTM that check for Cookiebot consent values before allowing tags to fire.

@AbdelhalimOJ
Copy link
Collaborator

AbdelhalimOJ commented Sep 1, 2024

@ShannonTrust To continue working on this issue, I need access to your Google Tag Manager account. Please invite me at [email protected] to your GTM account.

CC @cyberteenie

@ShannonTrust
Copy link
Collaborator Author

That's all done @AbdelhalimOJ

@AbdelhalimOJ
Copy link
Collaborator

Thanks @ShannonTrust I will follow up on this

@AbdelhalimOJ
Copy link
Collaborator

AbdelhalimOJ commented Sep 4, 2024

Update

It turns out that the GTM is empty, and you're only using Google Analytics to collect user data. So, I made sure the GA script loads only after the user consents and interacts with the Cookiebot banner.

Since our site is hosted on Webflow and is a marketing website without backend cookies, we can skip the step related to server-side cookies. Webflow doesn’t usually set backend cookies unless third-party scripts are used.

Our main priority is ensuring third-party cookies, like Google Analytics, are set only after user consent, which is now managed through Cookiebot.

I believe this will fully resolve the issue.

@ShannonTrust @cyberteenie

@ShannonTrust
Copy link
Collaborator Author

Thanks so much for looking into this for us @AbdelhalimOJ. I'll close the issue, but I'll continue to keep an eye on the Cookiebot reports to make sure nothing else comes up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working sla
Projects
None yet
Development

No branches or pull requests

4 participants