This integration shows a cookie consent banner and keeps third party scripts switched off until a visitor agrees. It is self contained: the banner and the stored choice are ours, with no third party plugin involved.
#Is this the right tool for you
Read this before the settings, because the answer decides whether the rest of the page is relevant.
This is a light solution for ordinary sites. It is built for a site with a countable number of external scripts: analytics, and perhaps one or two trackers.
The large consent platforms are built for a different job. They cover as many cases as possible for any site in the world, and that is why they are heavy: installing one typically brings its own script bundle, its own tracking of your consent events, its own admin interface and its own styling, all to render a bar at the bottom of the page. Page speed pays for that coverage, and a small site gets nothing back for it.
So if you run Google Analytics and a small tracker, use the built in integration instead of installing a separate consent plugin.
Where ours is not enough: complex analytics stacks, several ad networks, a requirement to keep a consent log, or certified compliance in a specific jurisdiction. Then you need a specialized product, and that is a normal outcome.
The banner is styled by the theme, so it looks like part of the site.
It takes its colors, type and shapes from your theme instead of carrying a design of its own. A consent bar is often the one element on a site that visibly came from somewhere else, and this one does not.
We provide a tool, not legal advice.
What you are obliged to show visitors, and what counts as valid consent, is decided by your jurisdiction, not by a setting in a theme. The GDPR text itself is public and readable, and for anything beyond an ordinary site the question belongs to a lawyer.
#The banner
The appearance settings are ordinary: width, heading, message text and whether to show the cookie icon.
Buttons: accept all, decline (keeping only what is necessary), and customize. The last two can be switched off if you do not want them.
There are three categories and they are fixed: necessary, analytics, marketing. You can rewrite the name and description of each in your own words, which is what a visitor reads in the settings window.
Necessary cannot be switched off. Explain why in its description, because that is a visitor's first question.
How long a choice lasts is a setting: after the period you set, the visitor is asked again.
#Consent-Gated Scripts does the blocking
On its own the banner blocks nothing. The Consent-Gated Scripts list is what holds scripts back.
Every third party script is added to this list and assigned to a category. Scripts in analytics and marketing wait for consent; necessary ones run immediately.
Each entry holds a name, so the list stays readable to you, the script itself, where it loads, and its consent category.
A script can be entered two ways: a full URL to a file, or the code itself. Paste the code on its own, with no surrounding script tag. Leaving the tag in is the most common mistake here.
One worked example covers the pattern: add Google Analytics, choose the analytics category, save, and test.
A script added anywhere else on the site is not blocked by the banner.
A tag in a template, in another plugin, or in a custom code field runs regardless of what the visitor chose, so consent is requested and the script fires anyway. That is worse than having no banner at all, because the site looks compliant and is not. Everything that has to wait for consent goes in this list and nowhere else.
#Testing before launch
Developer preview shows the banner on every page load, but only to administrators. Visitors keep seeing their saved choice.
It is a configuration tool. Switch it off before the site goes live.
A short check to finish: decline everything and confirm analytics did not fire, then accept and confirm it did.
This integration is licensed with the theme, not on its own.
Integrations are premium functionality for customers running a Pro license of one of our themes. They are written against our themes and expect them, and we cannot support or take responsibility for what one does inside somebody else's theme. See how theme integrations work.
#Common questions
Does this make my site GDPR compliant?
No tool can make that claim on its own. This one gives you consent handling and script blocking. Whether your specific setup complies is a legal question about your site, your visitors and your jurisdiction.
Do I need this if I have no analytics?
If nothing on your site sets third party cookies, there is nothing to consent to. Check what your plugins load before concluding that, though: embeds and fonts often reach outside without anybody deciding they should.
Can I add my own category?
No. The three are fixed. What you can write is their names and descriptions, in your visitors' language.
Where is the visitor's choice stored?
In their own browser, on your domain. It is not sent anywhere or shared with us.
Can I restyle the banner?
It follows the theme, which is the point of it. Anything beyond that is ordinary custom CSS, and the CSS you write is yours to maintain.
A script runs before consent is given
It is almost certainly not in the Consent-Gated Scripts list, because that list is the only thing that holds a script back.
Find where the script is actually added, whether that is a template, another plugin or a custom code field. Remove it from there, and add it to the list with a category instead.
#Still stuck
Open a support ticket and say what you tried and where it stopped. Your product, your domain, a screenshot and the exact message you saw are usually enough to settle it in one reply.
Last updated
