🍪 What ResultsAiX Consent Is: Cookie Banner, Script Blocking And Consent Log

ResultsAiX Consent is a WordPress plugin that asks your visitors which cookies they are happy with, holds tracking scripts back until they answer, and keeps a record of every answer. You use it so that the pixels, analytics and embedded videos on your site wait for a yes instead of running the moment a page loads.

Its guiding idea is simple: block first, ask second. The banner is only half the job. The other half is making sure nothing optional runs before the visitor has decided, and keeping proof of what they decided.

Where to find it:

After you activate the plugin, a new item called AiX Consent appears in your WordPress admin menu. It opens on the Dashboard tab, with nine more tabs across the top: Banner, Cookies, Blocking, Consent log, Policies, Training, Resources, Settings and Diagnostics.

What your visitors see:

A first-time visitor sees a banner with your wording and three buttons: Accept all, Reject all and Choose cookies. Accept and Reject are drawn exactly the same way, so neither one is pushed. Choose cookies opens a panel with five groups of cookies, a switch for each optional group, and the list of cookies in each group.

Here is the banner on yoursite.com, the made-up pottery studio used throughout these docs. The embedded video above it is held back too, with a placeholder and a button in its place.

What the plugin does for you:

• Shows a cookie banner in your colours, as a box in a corner, a bar across the page, or a box in the middle.
• Offers a choices panel with five cookie groups: Strictly necessary, Preferences, Analytics, Marketing and Unclassified.
• Holds matching scripts back on the server, so the browser does not fetch them, and puts them back the moment the visitor agrees to their group.
• Replaces embedded videos and maps with a placeholder the same size, with a button that turns on just that group.
• Sends Google Consent Mode v2 signals, with every signal starting as denied.
• Scans your own pages, names the tracking services it finds, and offers you the cookies each one is known to set.
• Rescans every week with Tracker Watch and emails you when a new tracking service appears.
• Keeps a consent log you can filter and download as a CSV file, with a one-way fingerprint in place of the IP address.
• Shows the banner in ten languages, picked by the visitor's browser.
• Treats a Global Privacy Control or Do Not Track signal as a refusal.
• Builds a cookie policy page, a Do Not Sell or Share page and a data request page.

The Dashboard at a glance:

Once the banner is live, the Dashboard tells you in one line how many tracking services are being held until a visitor says yes, and five tiles show the last 30 days: Answers, Accepted something, Rejected everything, Cookies declared and Services held.

How the parts fit together:

1. The scanner on the Cookies tab reads your pages and finds the services on them.
2. Your cookie declaration on the Cookies tab lists every cookie, in its group, with who sets it, how long it lasts and what it does.
3. The rules on the Blocking tab decide which scripts wait, and for which group.
4. The banner on the Banner tab asks the visitor, and the choices panel shows them your declaration.
5. Each answer is written to the Consent log, with the wording version that was on screen at the time.
6. The Policies tab turns your declaration into a cookie policy page that always matches it.

A real example:

Juniper Lane Pottery runs yoursite.com. Its pages carry Google Analytics, a Meta (Facebook) Pixel, Hotjar, a Mailchimp signup script, a YouTube video, a Vimeo video on the Classes page, a Google map on the Visit Us page and Stripe on the Shop page. After one press of Set me up and switch it on, the banner is live, Stripe keeps working because payments are never blocked by default, and the analytics, pixel and videos wait until each visitor chooses.

Software, not legal advice:

ResultsAiX Consent is software. It asks, it holds scripts back and it records what each visitor chose. It does not give legal advice, and the Dashboard checklist says so in its own words: it covers what a plugin can actually see.

How it handles scripts added later:

Blocking works on the page your server sends. A script that another script writes into the page after it loads is best governed inside your tag manager through Consent Mode, which this plugin sets up for you. The scanner reads the HTML of your pages, and for cookies that only appear once a script runs, it uses its built-in list of what each service sets.

Good to know:

• On a fresh install the banner is switched off, so nothing changes on your public site until you choose to switch it on.
• The plugin needs WordPress 5.8 or later and PHP 7.4 or later.
• The banner, blocking and consent log run for every visitor, on cached pages too.

Next steps:

Start with Installing The Plugin And Activating Your Licence Key, then follow Five Minute Quick Start With Set Me Up. For a tour of every screen, see The Admin Tabs Explained: Dashboard, Banner, Cookies, Blocking And More.