Skip to content

FAQ

Does it block Google Analytics and the Meta Pixel?

Section titled “Does it block Google Analytics and the Meta Pixel?”

Tags added by Pixel Tracking wait for consent on their own. Google tags read Google Consent Mode, which this plugin sets. For a script you pasted by hand, change it to type="text/plain" and add data-brl-consent with the category, and it waits too. With Cookie Consent Pro, the known Google and Meta scripts are held automatically. See Blocking scripts.

Yes. The page is the same for every visitor, so LiteSpeed, WP Rocket, Cloudflare and others can cache it. The visitor’s choice is read and applied in the browser.

Opt-in, if you sell to anyone in the EU or the EEA. Opt-out and Notice only let tracking start before the visitor chooses, which is not valid consent there. The Behaviour tab warns you if you pick one of them.

Hide from administrators is on by default. Open the site in a private window, or sign out. Also check that Show the consent banner is on (Behaviour tab), and that you have not already answered in this browser.

A small cookie button stays on every page and reopens the choices. On phones it can wait for the end of the page, so it never covers a buy button. You can also place [brl_consent_preferences] anywhere, for example in the footer.

Raise the Policy version on the Behaviour tab and save. Every visitor is asked again on their next page.

180 days by default. Change it with Cookie lifetime (days) on the Behaviour tab.

Every text is editable on the Texts tab, and six languages come ready: English, Romanian, German, French, Italian and Spanish. The admin screens translate through the usual WordPress language packs; Romanian is included. With Cookie Consent Pro, WPML and Polylang get every banner text as a translatable string.

Put [brl_privacy_request] on your privacy page. A visitor enters their email and asks for a copy of their data or for it to be erased. The request goes into WordPress’s own Tools > Export Personal Data or Tools > Erase Personal Data, and WordPress emails the visitor a confirmation link. Nothing happens until they click it.

The form needs JavaScript. To limit abuse, one address can send two requests an hour, one connection ten, and past a site-wide ceiling of thirty an hour the request is kept for you and you get one email about it. Unconfirmed requests made through the form are deleted after 30 days.

No. The free plugin talks to no external service. The visitor’s choice is kept in one first-party cookie, brl_consent, with the categories allowed, the policy version and the time of the choice. The data request form keeps a short-lived hash of the address and the connection for one hour, never the address itself.

Cookie Consent Pro adds one call: its licence check with brainrune.com.

Yes. Cookie Consent works on any WordPress site. The Hold WooCommerce order attribution switch shows only when WooCommerce is active.

No. It runs on its own. If you also use Pixel Tracking, the two find each other with nothing to connect, and the Dashboard checks that Pixel Tracking waits for the answer.

Section titled “I have Pixel Tracking Pro. Do I need Cookie Consent Pro?”

No. A Pixel Tracking Pro licence turns on Cookie Consent Pro on the same sites. A Cookie Consent Pro licence alone is for sites that only need the banner and the blocking.

Is a site behind Cloudflare or a proxy handled?

Section titled “Is a site behind Cloudflare or a proxy handled?”

Yes, for the request limits on the data request form. Behind Cloudflare and a local proxy the visitor is read from Cloudflare’s header, and CF-Connecting-IP is trusted only when the request comes from Cloudflare’s own ranges. Other trusted proxies are set with the brl_consent_trusted_proxies filter.