IA Cookie Consent Pro
Everything you need to install, configure and manage cookie preferences on your WordPress website.
01 Getting started
IA Cookie Consent Pro is a self-hosted WordPress plugin for presenting visitor consent choices, configuring optional scripts and maintaining a reviewable cookie inventory.
Before installing
- WordPress 6.2 or newer and PHP 7.4 or newer (declared minimums; not every combination has been tested).
- Administrator access and a recent site backup.
- Your IA Webspace account and licence key for updates and support.
Download and install
- Sign in to the IA Webspace account used for your purchase.
- Open My Account → Orders, select the completed order and use the authorised download link. A registered customer account is required.
- In your WordPress dashboard, open Plugins → Add New Plugin → Upload Plugin.
- Upload the ZIP file without extracting it, select Install Now, then Activate.
- Open Settings → IA Cookie Consent Pro and configure the banner and policy links.
- Open Settings → IA Cookie Licence and activate your licence key.
02 Banner & preferences
Configure your banner under Settings → IA Cookie Consent Pro. Choose one of five layouts: full-width bottom, top, bottom-left, bottom-right or centred. Adjust colours, headings, explanatory text, button labels, policy links and consent lifetime.
Consent categories
- Necessary: Always active.
- Preferences: Optional functional choices.
- Analytics: Optional measurement services.
- Marketing: Optional advertising and external content services.
New visitors start with optional categories disabled. They can accept all, reject optional categories or choose individually.
Allow visitors to reopen settings
Enable the floating Cookie Settings control, add a footer link to #iaccp-cookie-settings, or use this WordPress shortcode:
Cookie Settings
Change the Consent policy version when appropriate to request fresh choices after material changes to your policy or providers.
03 Script controls
Define optional script URLs and selected WordPress script handles for Preferences, Analytics and Marketing. A WordPress script handle is its registration identifier, which may differ from the JavaScript filename.
- Identify the script, provider and purpose.
- Assign it to the correct optional consent category.
- Save the rule and test in the browser's Network panel before granting consent.
- Grant the category, reload and check loading again.
- Withdraw consent and verify the script no longer runs on a subsequent page load.
The separate WP Consent API plugin can share choices with participating plugins. Sharing consent is not the same as automatically blocking third-party scripts.
04 Cookie scanner
While logged in as an administrator, visit a website page and select Scan cookies on this page from the WordPress admin toolbar. Open Settings → IA Cookie Inventory to review the results.
The inventory records observed cookie names, suggested classifications, page paths and detection history. It does not collect cookie values.
- Scan representative pages such as home, contact, shop and checkout.
- Review suggested categories against the provider's documentation.
- Manually adjust incorrect categories; overrides remain after subsequent scans.
- Verify the results with browser developer tools.
05 Consent-controlled embeds
Use the supported shortcode to display a privacy-friendly placeholder for selected YouTube, Vimeo or Google Maps embeds until the required consent category is granted.
🔒External content is blockedTo protect your privacy, this embedded content will load only after you allow the relevant optional cookies.
Replace VIDEO_ID with your video's identifier. Test the placeholder, loading after permission and removal after withdrawal.
06 Licensing & updates
The standard licence covers one WordPress website and provides 12 months of updates and technical support from licence issuance. It does not automatically renew.
Activate and manage your licence
- Open Settings → IA Cookie Licence.
- Paste your private licence key and choose Activate licence.
- Use Verify licence to refresh its status.
- Use Deactivate licence before moving the installation to another website, where possible.
Eligible plugin updates appear in WordPress → Dashboard → Updates. Back up your site before updating.
Uninstall and data retention
Uninstalling retains settings, licence state and cookie inventory by default. Administrators seeking full local removal may configure IACCP_DELETE_DATA_ON_UNINSTALL as true in wp-config.php before uninstalling. Deactivate the licence first where possible.
07 Troubleshooting
The banner isn't appearing
Confirm the consent interface is enabled, check whether another consent plugin is active, and clear page or asset caches. Test in a fresh private browser window.
The Cookie Settings link doesn't work
Use the anchor #iaccp-cookie-settings, the shortcode Cookie Settings, or enable the floating settings button.
An optional script loads before consent
Verify the correct WordPress script handle or URL, check for scripts injected outside WordPress, and review JavaScript optimisation settings. Some providers need their own consent integration.
Checkout or payment elements aren't working
Remove optional blocking rules for payment and security scripts, clear optimisation caches and retest safely. Avoid classifying essential checkout functionality as Marketing or Analytics.
My licence isn't activating
Check the exact key, website URL, HTTPS connectivity and remaining site activations. Do not share the full key in a public support message.
Need more help?
Contact IA Webspace via iawebspace.com. Include the plugin, WordPress and PHP versions plus redacted screenshots or logs. Never send passwords, licence keys or download tokens.
08 Important limitations
IA Cookie Consent Pro is a technical consent-management tool. It is not a GDPR certification or guarantee of legal compliance. Website owners remain responsible for identifying relevant services, reviewing consent purposes, preparing appropriate notices and checking legal requirements.
- Blocking applies to configured scripts and supported integrations, not all possible trackers.
- Browser-based scanning is not comprehensive.
- Previously executed scripts cannot be undone retrospectively.
- Saved custom text may not automatically switch languages.
- Third-party plugin, payment gateway and accessibility compatibility varies by installation.
- Automated licence-expiry behaviour and the full WCAG/RTL matrix have not been exhaustively verified.
Before launch, test consent choices, configured scripts, embeds and essential checkout flows on your own website.