The Privacy Suite for WordPress

Cookie banner does not appear

Get compliant today in the European Union, United States, Canada, United Kingdom, Australia & South Africa with the only Privacy Suite for WordPress that offers a fully-featured plugin for Worldwide Compliance.

A frequently asked question by new Complianz users is ‘Why is my banner not showing on the front-end of my site?’. Quite the disappointment if you have just fully configured the Complianz wizard and beautifully styled your Complianz cookie banner. Luckily, the solution is often simple:

1. Check your Complianz dashboard

Complianz will configure your cookie banner after you completed the wizard for the first time, and the plugin confirmed that your site needs a cookie banner. You should see the following message:

“Your site needs a cookie banner, which has been enabled.”

If it says “your website does not require a cookie banner”, please check if you answered Yes on the question; Does your website use cookies? This question can be found in the wizard under -> Integrations.

2. Empty your site cache

If you are using a caching plugin, the old version of your site (without a cookie banner) is probably cached. Clear the cache(s) of these plugins and try again, if you use a CDN, please refresh this as well. While you’re at it, please use the below tip as well:

3. Visit your site in an incognito/private window

Just like your webserver can cache your site without our cookie banner, your browser cache can interfere as well! Using an incognito or private window (depending on the browser you are using) circumvents browser cache. With most browsers, you can use command + shift + N, or for Windows: control + shift + N to open a private window. It is generally a good idea to use trick while applying changes to a live site, to prevent looking at an ‘older’ version of your site.

4. (Premium) Are you visiting the site from a configured region?

This one is commonly overlooked by Premium users working from outside one of the supported regions. If you have enabled GeoIP (under Complianz -> Settings) and for example are configuring a site just for the CCPA/United States, you won’t see the cookie banner if you are working from Europe.

There are several ways to check how your banner looks in a different region:

  • Use a VPN
  • Use an application like Browserstack.
  • Temporarily disable GeoIP (Complianz -> Settings) and other regions (Wizard -> General -> Regions).

To check if you’re using the correct region if the above is applicable is open your browser console (ctrl/cmd + shift + i) for Chrome, and under Console, you will find three options:

1. Opt-in (EU, UK, and sometimes Canada)
2. Opt-out (USA, and sometimes Canada)
3. Other region, no cookie warning. (e.g. Mexico)

The one specified in your console, is the banner you should expect. With option 3, no banner will show.

5. (Premium) Make sure that your browser does not send DNT signals

While configuring the Complianz wizard, the plugin will ask you if you want to respect signals. If you have indicated that you wish to respect DNT signals, this means that the cookie banner will not be shown to you if you have configured your browser to send a do not track request. You can test if this is the cause of the issue by disabling this functionality in Complianz, or by (temporarily) switching of this setting in your browser. The setting is usually found in the privacy or cookies settings of your browser

6. Check your console for errors

If you still did not spot your cookie banner from the front-end of your site, there could be some other problem. You can investigate by right-clicking on your site (front-end) -> Inspect -> Console. If you see any errors in red, this could direct us to possible causes of the cookie banner problem. If you need help interpreting console errors, please contact support.

In 90% of the cases, the problem should be solved by now. Though you could identify the following errors in your console:

  • jQuery errors. Complianz needs jQuery, so if your theme does not enqueue jQuery, the banner will not appear.
  • Error with reCaptcha, or greCaptcha. Disabling the reCaptcha integration should do the trick. This is caused by a dependency issue in another plugin, theme, or compatibility issue. Please ask support for guidance.
  • 403 errors, indicating that our cookieconfig.js script gets blocked by a security setting in your security plugin or due to a server configuration. A known issue is with XSS rules, with All in One Security for Example.
  • 404 error, this might indicate an installation issue or server-side problem. Try reinstalling Complianz, as the files might not be installed properly the first time.
  • Nothing happening at all: if you don’t see functional cookies being allowed (“fire cmplz_event_functional), Complianz might not be activated at all, jQuery and/or javascript are not allowed.

7. Your site uses high z-index values

Some themes (or developers 😉 ) use very high z-index values. Z-index is used to indicate which element should appear above the other. There might be nothing wrong with your cookie banner, but if your site uses very high z-index values, the banner could be ‘hidden’ below other elements.  The default z-index of the Complianz cookie banner is 9999. There are two ways to solve this problem, or to test if z-index is indeed the problem:

    1. Lower z-indexes for other elements of your site (if you know how)
    2. Increase the z-index of the cookie banner. You can do this by enabling custom CSS via Complianz -> Cookie banner -> Enable custom CSS.
      You can paste the following CSS in the window that appears, and increase the value:


If your cookie banner still isn’t appearing, please contact support. We’re happy to help you solve the mystery!

7. You’re using GEO IP and IP Masking

When you’re using localhost or a server that is configured with strict privacy settings. It is likely IP addresses are masked, and changed server-side to a localhost IP. This means all users have the same IP, 127.0. 0.1. This will result in a console log explaining the region is not available and no cookie warning is enabled. This log is available in your browser console if you want to check.

If this is the case on localhost, we suggest enabling a default banner for “other regions” in the wizard, the very first section and question. If you’re on a production site, the privacy settings are actually preventing specific consent management and fall under legitimate interest. Disabling these settings requesting the actual IP addresses is necessary.

9. WordPress 5.5 and jQuery 3.0

WordPress 5.5 includes an upgrade to jQuery 3.0, which can cause trouble with your site if your theme is running an old version of jQuery. WordPress also dropped the migrate script that converted older jQuery versions. We have received reports from users where the cookie banner stopped appearing after upgrading to WordPress 5.5, because of this problem.

If you are using an older theme, you can load jQuery 3.5 by inserting this script (preferably in your footer.php):

<script src=""></script>

Please note that if your theme is running an old version of jQuery this could be a security issue as well, so it might be worth considering switching to a different theme.

If that doesn’t work, because you haven’t enqueued jQuery, please do the following:

 // include custom jQuery
function cmplz_include_custom_jquery() {
	wp_enqueue_script('jquery', '', array(), null, true);
add_action('wp_enqueue_scripts', 'cmplz_include_custom_jquery');

Recent articles

The Privacy Suite for WordPress
Get compliant today with the only Privacy Suite made for WordPress


Popular articles

LGPD Brazil and WordPress

The “Marco Civil” and the Brazilian General Data Protection Law (LGPD) In Complianz 5.4 we will add full support for the Civil Rights Framework for

Read More

Join our mailing list - 8 Tips & Tricks in your inbox over the next 8 weeks!