FAQs

Why is the require banner interaction grey overlay missing on certain pages?

The CMP suppresses the require banner interaction overlay (grey background) when the current page URL matches a URL configured within the banner or preference center content.

The CMP evaluates URLs configured from the following locations:

• Template Cookie Policy Link field
• Template Imprint Link field
• Custom anchor (<a>) tags added to the Title and Description field

This behavior is by design. URLs configured within banner or preference center content are typically intended to direct users to privacy-related disclosures and legal notices, such as Privacy Policies, Cookie Policies, Terms of Use, or similar notices. Users must be able to access and review this transparency and disclosure information before making a consent decision. Providing access to these resources prior to consent supports informed consent practices and improves transparency. When a user navigates to a configured disclosure URL, the CMP suppresses the require banner interaction overlay to ensure the content remains accessible.

Why might a 'Not Given' consent receipt not be recorded when a user closes the final website tab or browser without interacting with the CMP?

When a user visits the site for the first time and does not interact with the CMP or refresh the page before closing the browser or final website tab, a 'Not Given' consent receipt is submitted through the browser’s navigator.sendBeacon() API as the page is dismissed.

The sendBeacon() API asynchronously queues the request for transmission without delaying page dismissal. A true return value indicates that the browser successfully queued the request for transfer. It does not confirm that the OneTrust server received or processed the request. See here for more information.

When the final website tab or browser is closed, the browser may terminate the page or process before the page lifecycle event completes or the beacon request is transmitted. Delaying the closure of the tab or browser gives the browser additional time to transmit the queued request, which can increase the likelihood of successful delivery. However, the additional time does not guarantee that the request will be received or processed by the server. Consequently, the 'Not Given' consent receipt may not be submitted consistently.