All plugin profiles

WordPress plugin (cookiepro)

CookiePro for WordPress: setup and privacy checks

This page describes technical observations for one plugin. It is not legal advice, and it is not a compliance verdict.

What is CookiePro?

CookiePro is OneTrust's consent-management product. On a WordPress site, the consent deployment presents visitor choices and connects those choices with the scripts you configure it to control. A visible banner alone does not confirm that analytics, advertising, or embedded services wait for consent.

OneTrust's CookiePro update says CookiePro.com is now part of OneTrust.com. Existing customers can still access their CookiePro environment and billing in the CookiePro app. For account access or support, use the links on that official page. This independent guide is not the CookiePro login page or vendor support.

Product documentation reviewed October 30, 2026. The separate lab date below has not changed.

Sandbox lab observation

We activated this plugin alone on handl-sandbox, scanned the home page, then deactivated it.

This configured sandbox recorded Meta and HubSpot requests before consent on the date below. It does not establish that every CookiePro installation behaves this way, or that CookiePro itself loaded those services. Rejection and withdrawal need separate testing; these observations are not a current-release certification.

Test setup
Configured
Blocks tracking before consent (lab)
No
Lab verified
Aug 19, 2026

Vendors observed before consent in the lab

See all cookie banner tests

Results from scanned websites

Not enough scanned websites meet the minimum number of sites for this plugin yet. You can still view the test-site results above.

How to check CookiePro on WordPress

Use a staging site and synthetic submissions where possible. Save the current configuration before changing consent or tracking settings.

  1. Find the deployment owner. Check the WordPress plugin, theme header, code-snippet plugins, and tag manager. Record where the CookiePro script is inserted. Two integrations can load the same banner twice.
  2. Check the domain and published configuration. Match the live hostname and environment with the configuration in your account. Inspect the browser Network and Console panels for failed script requests or policy errors. A saved setting is not proof that the live page received it.
  3. Record a clean first visit. Use a fresh browser profile without extensions. Open Network before loading the page, then record requests and cookies before making any choice. Test a landing page, a form page, and checkout if applicable.
  4. Test choices separately. In separate fresh sessions, reject optional categories, accept only one category, and accept all. Compare what loads with the intended behavior for each category and region. A request alone does not prove a cookie was stored or a law was breached.
  5. Test changing your mind. Reopen the preference center, withdraw an optional category, and reload. Check that later events follow the new choice. Consent Mode signals and cookie storage need separate checks; denied consent does not necessarily mean zero network requests.
  6. Repeat after deployment. Purge the relevant WordPress and CDN caches after publishing changes. Retest logged out with production optimization enabled. Keep the tested URL, date, configuration, and results so a later change can be compared.

CookiePro troubleshooting guides

Compare CookiePro with another WordPress consent setup

Related fix guides

Open the leak fix guides for step-by-step checks that match what the scanner detects.

Browse leak fix guides

Scan your own site

Run a free Leak Finder scan. If this plugin’s files appear on the scanned page, the report can surface them with any named vendors.

Scan your site

Weekly Leak Watch

Leak Watch re-checks the same site weekly and emails you when the score or checks move.

Open Leak Watch