Troubleshooting European and US state regulations messages

Check the "Referrer-Policy" set on the site. The only supported values are "strict-origin-when-cross-origin" (the default referrer policy), "origin", "origin-when-cross-origin", or "unsafe-url". If you are setting any other value, such as "same-origin", messages will be unable to serve.

Check the site’s GPT tagging.

• The GPT tag must be added to your site’s code.

• The GPT tag added to your site's code must include the "async" attribute.

Check the site’s non-Google code and/or tagging. 

• Messages cannot be displayed in an iFrame.

• Site must not be running scripts that modify various standard JavaScript functions (for example, overriding functions related to arrays or JSON.stringify) that our scripts rely on.

• Site must not be trying to do any special handling or manipulation of the FCCDCF cookie.

Check if another third-party CMP is also set up for European regulations on the same site

• We will not load the "__tcfapi" in cases where there's an existing API on the page.

Check the configured internal protocol of the site. Messages will only serve on "https" sites.

In addition to blocking ads, ad blocking extensions may occasionally block user messages, including European regulations messages. Read more about troubleshooting blocked user messages.

If you are an MCM Parent or Child publisher, review the MCM-specific setup guidance within the  User messages and Multiple Customer Management (MCM) article.

Check the "Referrer-Policy" set on the site. The only supported values are "strict-origin-when-cross-origin" (the default referrer policy), "origin", "origin-when-cross-origin", or "unsafe-url". If you are setting any other value, such as "same-origin", messages will be unable to serve.

Check the site’s GPT tagging.

• The GPT tag must be added to your site’s code.

• The GPT tag added to your site's code must include the "async" attribute.

Check the site’s non-Google code and/or tagging. 

• Site must not be running scripts that modify various standard JavaScript functions (for example, overriding functions related to arrays or JSON.stringify) that our scripts rely on.

Check the configured internal protocol of the site. Messages will only serve on "https" sites.

Check if you have ad blocking enabled on the web/mobile web page and, if so, temporarily disable it during your testing. In addition to blocking ads, ad blocking extensions may occasionally block user messages, including US state regulations messages. Read more about troubleshooting blocked user messages.

Check if you’re using a VPN or some other tool for geographic spoofing to a US state in scope of the message. Our geographic detection is sophisticated enough to often detect if you’re not actually in scope of applicable state regulations and then not serve the published US state regulations message.

If you are an MCM Parent or Child publisher, review the MCM-specific setup guidance within the User messages and Multiple Customer Management (MCM) article.