Customizing Autoblocking

Overview

Cookie Compliance comes preset with a list of Providers and URL Patterns organized by purpose category. URL Patterns allow the autoblocking feature to identify and hold any non-essential scripts or iFrames until a positive consent is recorded.

The preset list covers many common website services. If you do not see a provider in any category, you can add it with its URL patterns.

Checking Blocking in WordPress Admin

In WordPress admin, open Compliance > Overview tab. The Script blocking box shows whether blocking is on for your site.

The WordPress admin does not list providers or support adding, editing, or deleting them. To see and manage providers, open the Admin Portal and go to Autoblocking.

Managing Providers in the Admin Portal

Full provider management is done in the hu-manity.co portal at app.hu-manity.co → Autoblocking. Here you can:

• Add a provider — Click Add Provider, enter the provider name, and add its URL patterns.
• Edit a provider — Change its purpose category (paid plan; some providers are locked), add URL patterns, or remove patterns you added. Saved patterns cannot be edited. The name and URL can be changed only on providers you created.
• Recategorize a provider — Move a provider between purpose categories. Requires a paid plan. Recategorizing a tracking service into Basic Operations lets it load before consent; that is possible but not recommended under GDPR and similar regulations. See the reCAPTCHA example below.
• Delete a provider — Remove a provider and its URL patterns entirely.

Quick Reference: Where to Do What

Example: Recategorizing reCAPTCHA

Google reCAPTCHA is one of Google’s tracking services, so by default it sits in the content-personalisation category and is held back until the visitor accepts that category.

Accepting cookies does not fix the page you are already on. Form plugins set up their reCAPTCHA support while the page is loading, so the visitor needs to already have a cookie choice recorded when the page loads. A visitor who accepts and then immediately submits, without the page reloading, will still see it fail. This is why the problem can look intermittent.

There are three ways to resolve it.

Option 1: Use A Captcha That Does Not Track Visitors (Recommended)

A privacy-friendlier captcha (for example Friendly Captcha, or another provider that does not depend on Google cookies to score the visitor) with native form-plugin support is the cleanest fix: the form can work for every visitor without moving Google reCAPTCHA into Basic Operations. Confirm the provider’s own tracking claims before you treat it as consent-exempt. Your form then works for every visitor and the Google reCAPTCHA question goes away.

Option 2: Recategorize reCAPTCHA As Essential

This makes the form work for every visitor immediately. The trade-off is that reCAPTCHA will then load, and set Google’s cookies, before the visitor has consented — which is why we don’t recommend it under GDPR and similar regulations. It is a valid choice and it is yours to make; we would just rather it wasn’t an unintended one. Changing a provider’s category requires a paid plan — on the free plan the category setting is shown but cannot be changed, so Option 1 or Option 3 is the route there.

Step 1: Update the category in the portal

1. Open the portal at app.hu-manity.co → Autoblocking.
2. On the card for the category reCAPTCHA is currently in, expand Providers List.
3. Find Google ReCAPTCHA, open the three-dot menu on its row and choose Edit. Take care not to use Edit Category on the card itself — that edits the category’s own name and description, not which category a provider belongs to.
4. Set the category to Basic Operations and Save.
5. Click Publish Now.

Step 2: Let your site pick up the change

Publishing updates your account, but your site also has to fetch the new configuration. Which of these applies depends on how Cookie Compliance is installed — you only need one.

• On WordPress: in your WordPress admin, open the Cookie Compliance menu (labelled Compliance, or Privacy on older plugin versions) and click Pull latest settings. The plugin also refreshes on its own every 12 hours, so this just makes it immediate. If your site uses a page cache or a CDN, clear it afterwards so visitors are not served the previous configuration.
• Installed directly with a script (not WordPress): go to Integrations in the portal left-hand menu, copy the script shown there, and replace the existing Cookie Compliance script on your site. On a direct installation the category change travels inside that snippet, so the site will not pick it up until the snippet is replaced.

Option 3: Keep reCAPTCHA Gated, But Reload After Consent

In the portal under Configuration → Behavior there is a Reloading setting: “Enable this to reload the page once a consent is recorded.” With it switched on, a visitor who accepts gets a fresh page load, and the form then works normally — with reCAPTCHA still held back until consent. The limit worth being clear about is that visitors who decline still will not be able to submit, so for a form you want every visitor to reach, Option 1 is the better fit. Option 2 is possible but not recommended under GDPR and similar regulations. Reloading works on both engines.