"HTTP Consent Cookies are not reaching Consent Studio"

HTTP Consent Cookies are not reaching Consent Studio is an urgent recommendation in Consent Studio Monitoring. Active recommendations show on the Start page of your domain's dashboard and on the Recommendations page (Monitoring dropdown in the top bar). Collaborators on the domain may also receive it by email.

What this recommendation means

You have switched on HTTP Consent Cookies via a CDN worker, but consent requests on your domain do not reach Consent Studio. The recommendation says, for example:

"HTTP Consent Cookies are switched on for your site, but your CDN is not forwarding consent requests to Consent Studio. Your visitors' choices are not recorded in your consent log, and returning visitors may be asked for consent again."

During a scan, Monitoring calls the consent address on your domain (https://yourdomain/consent-studio/ssc) and checks whether the answer comes from Consent Studio. When it doesn't, the recommendation names the exact address that failed.

Why you're seeing it

The address returns "404 Not Found"

No worker answers on this address. Usually the Cloudflare Worker is not deployed (yet), or it has no route for /consent-studio/ssc on this domain.

The address returns one of your own web pages

The request reaches your website instead of the worker. The worker route does not cover this exact address, for example because the route is set on a different hostname (with or without "www.") than the one your banner runs on.

The worker forwards for a different domain

The worker is running and forwards requests to Consent Studio, but for a domain that does not match this site. Check that the worker route is set on the same domain your banner is installed on.

How to resolve it

Choose one of these two options.

Option 1: fix the worker

1. Make sure the Cloudflare Worker is deployed and has a route that covers yourdomain/consent-studio/ssc*. The full setup is in How to configure HTTP Consent Cookies (CDN). The CDN configuration guide button on the recommendation opens the same guide.

2. Click Manage HTTP Consent Cookies on the recommendation to open the HTTP Consent Cookies page, and use Test Worker to check the result.

The recommendation closes by itself after the next completed scan that reaches Consent Studio through the worker. Monitoring remembers the last check result for up to an hour, so a scan started right after your fix can still show the old result.

Option 2: switch HTTP Consent Cookies off

If the worker isn't ready yet, open the HTTP Consent Cookies page, switch off Enable HTTP Consent Cookies via a CDN Worker and click Save & Publish. The recommendation then closes right away. Linked subdomains that use this domain's setting are covered as well. You can switch HTTP Consent Cookies on again later via the setup wizard on the same page.

Common questions

What happens if my firewall blocks the check?

If the address answers with an error such as "403 Forbidden", a server error or a timeout, Monitoring can't tell whether the worker works. It then keeps the previous result instead of raising or closing the recommendation.

This domain is a linked subdomain. Which address is checked?

A linked subdomain uses the worker address of its parent domain, so that address is checked.

Can I dismiss it?

Yes, but it comes back after 7 days if the problem is still there.

Still unsure? Contact us and include your domain.