Table of Contents
47% of users expect pages to load in under two seconds. But slapping a heavy cookie consent banner onto your site often ruins that metric instantly.
Handling compliance on standard websites is annoying enough. Doing it on a client-side routed application is a completely different technical nightmare. When you search for how to handle cookie consent on single page applications, you’ll quickly realize standard plugins don’t cut it. They break. They fail to track route changes. They leave you legally exposed.
Key Takeaways
- Unoptimized cookie scripts can increase Largest Contentful Paint (LCP) by up to 1.5 seconds on SPAs.
- In 2023, GDPR fines reached a record €2.1 billion, making compliance failures highly expensive.
- Google Consent Mode v2 became strictly mandatory in March 2024 for all EEA and UK traffic.
- Roughly 40% of standard consent plugins fail to re-trigger during standard SPA route changes.
- Elementor Editor Pro users need native History API interceptors to prevent banner flashing.
- Cookiez remains the top performer for WordPress SPAs in 2026 due to its native route listening.
The privacy field changed massively over the last few years. The Digital Markets Act (DMA) explicitly identifies gatekeepers like Google and Meta. These companies now demand verified consent signals from third-party websites before they’ll process any user data for ad personalization. If you don’t send those signals, your tracking simply stops working.
This creates a massive headache for modern web architecture. Single Page Applications (SPAs) load a single HTML document. They update the body content dynamically via JavaScript as the user navigates. The page doesn’t actually reload. So, what happens to your compliance tools?
- The Load Event Fails – Standard plugins bind their logic to the
DOMContentLoadedevent. In an SPA, that fires exactly once. - Scripts Escape Control – When a user navigates to a new view, new components might inject unapproved scripts. The consent manager doesn’t see them.
- Consent Mode Desyncs – Google Consent Mode v2 requires precise state updates. If the CMP doesn’t detect the route change, it sends stale consent states to your tags.
You can’t just install a basic banner and hope for the best. You need a tool built specifically for virtual DOMs and client-side routing.
1. Cookiez: The Number One Solution for Modern SPAs
We’ll start with the heavy hitter. Cookiez dominates the market in 2026 for a very specific reason: it intercepts the History API directly. It doesn’t wait for page reloads. It actively watches the browser’s address bar for changes.
This is a premium WordPress plugin engineered strictly for speed and bulletproof compliance. When you’re running a heavy frontend, you don’t want your privacy suite dragging down the main thread. Cookiez prevents this by using ultra-lightweight vanilla JavaScript that patches directly into standard SPA routing events.
Key Features:
- Native Google Consent Mode v2 integration built right into the core.
- Automatic script blocking for over 50 common third-party services.
- Custom SPA event listeners that trigger instantly on React, Vue, or Elementor route changes.
- Local data storage to prevent external API latency.
Pricing: Licenses start at $49/year for a single site.
Pros:
- Exceptionally fast execution time won’t hurt your Core Web Vitals.
- No external server pings required to load the banner UI.
- Flawless integration with Elementor Editor Pro environments.
Cons:
- No free tier exists for hobbyists.
- The advanced route-listening features require reading the documentation carefully.
Verdict: Cookiez is the absolute best choice for performance-focused developers who need guaranteed compliance without sacrificing load speed.
2. Cookiebot by Usercentrics
Let’s shift gears to cloud automation. Cookiebot takes a completely different approach to the problem. Instead of relying on manual configuration, it acts like a search engine bot.
This platform runs a monthly automated scan across your entire domain. It finds every single cookie, tracker, and beacon hidden in your source code. Then, it automatically updates your public-facing cookie declaration. For massive enterprise sites with dozens of content editors adding random embeds, this automation is a lifesaver.
Key Features:
- Headless browser scanning that crawls up to 10,000 subpages automatically.
- Geo-targeting to display different banner strictness based on user location.
- Cross-domain consent sharing for complex corporate architectures.
- Automated categorization of newly discovered trackers.
Pricing: There’s a free tier if your site has fewer than 50 subpages. Premium plans start at €12/month.
Pros:
- Total “set-it-and-forget-it” peace of mind.
- Highly accurate legal documentation generation.
- Massive database of known tracking technologies.
Cons:
- The cloud-loaded script is heavy and known to impact LCP scores.
- Costs scale aggressively as your page count grows.
Verdict: Choose Cookiebot if you manage massive corporate sites and prioritize automated legal safety over raw frontend performance.
3. Complianz: The Privacy Suite for WordPress
Sometimes you need more than just a popup. You need a complete legal shield. Complianz currently powers over 700,000 active WordPress installations, making it a massive player in the space. The global Consent Management Platform (CMP) market is projected to reach $2.3 billion by 2030, and Complianz is grabbing a huge chunk of that by offering a full suite of legal documents.
The setup process feels like an interview with a lawyer. The wizard asks you specific questions about your business, your visitors, and your data habits. It then generates custom Privacy Policies, Impressum pages, and cookie banners tailored perfectly to your region.
Key Features:
- Wizard-driven generation of legally binding privacy documents.
- Deep integration with the official WP Consent API.
- Built-in A/B testing to optimize banner conversion rates.
- Automatic placeholder generation for blocked video iframes.
Pricing: Premium starts at $59/year for one website.
Pros:
- Replaces the need for expensive legal counsel for basic compliance.
- The setup wizard catches edge cases you’d normally miss.
- Excellent handling of blocked content placeholders.
Cons:
- The sheer volume of settings feels overwhelming initially.
- The default styling requires CSS tweaking to look modern.
Verdict: Complianz is ideal for agencies that want to hand off a fully documented, legally sound website to their clients.
4. Borlabs Cookie 3.0
If you’re operating within the DACH region (Germany, Austria, Switzerland), you already know about Borlabs. German privacy enforcement is notoriously strict. Borlabs Cookie 3.0 was rebuilt from the ground up to handle SPA state management while maintaining a “Privacy by Design” architecture.
Unlike cloud solutions, Borlabs keeps everything local. It doesn’t ping external servers to load your banner. It writes consent logs straight to your own database. This localized approach makes it practically immune to certain types of strict EU data auditing.
Key Features:
- Aggressive content blockers for YouTube, Google Maps, and social feeds.
- 100% local storage of all consent transaction logs.
- Advanced script execution control specifically engineered for SPA lifecycles.
- Custom widget injection for user preference centers.
Pricing: Licenses begin at €39/year.
Pros:
- Zero external cloud dependencies.
- The content blocker UI is visually excellent out of the box.
- Highly respected by European privacy auditors.
Cons:
- The interface is highly technical and intimidating.
- Setting up custom script blockers requires writing actual JavaScript.
Verdict: Borlabs is the undisputed champion for sites facing strict European scrutiny that need local data storage.
5. OneTrust PreferenceChoice
Look, sometimes a simple plugin isn’t enough. When you’re managing a massive global brand with dozens of SPAs, mobile apps, and connected devices, you call OneTrust. This is the enterprise standard.
OneTrust PreferenceChoice isn’t just a banner. It’s a colossal platform for managing risk, vendor lifecycles, and user privacy across multiple platforms. If a user denies cookies on your React native app, OneTrust synchronizes that denial to their session on your web SPA. It’s incredibly powerful, and incredibly complex.
Key Features:
- Universal consent synchronization across all device types.
- Deep, native integration with enterprise MarTech stacks (Salesforce, Adobe).
- Granular reporting and audit trailing for legal defense.
- Custom API endpoints for headless architectures.
Pricing: Enterprise contracts usually start around $500/month, scaling wildly based on traffic.
Pros:
- Unmatched feature depth for cross-platform tracking.
- Backed by a massive legal research team.
- Handles complex data subject access requests (DSARs).
Cons:
- Prohibitively expensive for anyone outside the Fortune 500.
- Implementation usually requires a dedicated dev team.
Verdict: OneTrust is the only logical choice for massive international corporations with complex cross-domain tracking needs.
6. CookieYes
Let’s step back into the field of the accessible. CookieYes recently surpassed 1.2 million active installations. It hit this milestone by finding the perfect middle ground between cloud power and user simplicity.
It uses a centralized cloud dashboard. You manage your consent settings on their website, and the changes instantly push down to your SPA via a lightweight embed script. This makes managing a portfolio of ten different websites incredibly easy, as you don’t have to log into ten different WordPress dashboards.
Key Features:
- Automatic translation support for over 30 languages.
- A visual customizer for banner styling that requires no CSS knowledge.
- Cloud-based consent log exports for rapid auditing.
- Pre-built templates for GDPR, CCPA, and LGPD.
Pricing: There’s a decent free tier. Premium unlocks at $10/month.
Pros:
- The cloud dashboard makes multi-site management a breeze.
- Installation takes less than two minutes.
- The user interface is exceptionally clean.
Cons:
- If their cloud goes down, your banner won’t load.
- Route change detection sometimes requires manual API triggers.
Verdict: CookieYes is fantastic for small agencies managing multiple client sites who want a centralized control panel.
7. Usercentrics (Browser SDK)
What if you’re building a completely custom frontend? Standard embed codes usually conflict with modern component lifecycles. That’s where the Usercentrics Browser SDK shines. This is a developer-first approach.
Instead of giving you a pre-built UI that you’ve to override, Usercentrics provides raw data and functions. You build the banner UI yourself using React, Vue, or native Elementor components, and you wire the buttons up to their SDK. This guarantees the consent banner perfectly matches your design system.
Key Features:
- Headless UI architecture for total design freedom.
- Full support for the IAB TCF 2.2 framework.
- Direct state management hooks for SPA routers.
- Granular control over specific script execution timing.
Pricing: Custom quotes based entirely on monthly session volume.
Pros:
- Zero styling conflicts with your existing CSS.
- Perfect performance optimization since you control the render cycle.
- Massive flexibility for custom routing logic.
Cons:
- Requires significant custom JavaScript development.
- Maintenance overhead increases.
Verdict: The Usercentrics SDK is essential for development teams building heavily customized web applications from scratch.
8. Termly
While European laws dominate the conversation, the United States has its own mess of regulations. Under the CPRA, intentional violations can trigger fines up to $7,500 per incident. If your SPA gets heavy traffic, those fines scale rapidly.
Termly focuses heavily on the American legal framework. It simplifies compliance by bundling a suite of legal generators with a competent consent manager. Data shows that 70% of consumers trust brands more when they’re transparent about data usage. Termly makes that transparency very easy to implement.
Key Features:
- Auto-updating cookie policies based on regular site scans.
- Specific “Do Not Sell My Personal Information” link generation for CCPA.
- Simple, centralized dashboard for legal text management.
- Identity verification flows for user data requests.
Pricing: Basic features are free. Pro plans cost $15/month.
Pros:
- Excellent coverage for US-based state laws (CCPA, VCDPA, CPA).
- Very affordable for small businesses.
- Policy texts are written by actual attorneys.
Cons:
- The banner customization options are rigidly limited.
- SPA support requires manual setup of their callback functions.
Verdict: Termly is a solid, budget-friendly choice for US-based businesses prioritizing CCPA compliance.
9. Quantcast Choice
Publishers rely on advertising to survive. The ad industry relies on the Transparency and Consent Framework (TCF) to serve personalized ads legally. Quantcast Choice was built specifically for this ecosystem.
This CMP is massively popular among news sites and content hubs. It guarantees that verified consent signals pass perfectly to Google AdSense, Prebid, and other programmatic networks. Best of all, they offer it entirely for free to most users.
Key Features:
- Complete integration with IAB TCF 2.2 standards.
- Detailed vendor management lists for ad networks.
- Cross-device consent sharing for logged-in users.
- Monetization analytics dashboard.
Pricing: Completely Free for the standard tier.
Pros:
- The price point is unbeatable.
- Protects ad revenue by ensuring TCF signals are flawless.
- Highly reliable cloud infrastructure.
Cons:
- The user interface is heavily skewed toward ad tech, making it confusing for simple sites.
- The frontend banner is quite bulky.
Verdict: Quantcast Choice is mandatory for ad-supported publishers who depend on programmatic monetization.
10. Didomi
We’ll round out the list with a premium European option. Didomi treats consent not as a legal burden, but as a brand advantage. Websites that implement clear, beautiful consent UI see a 15% higher opt-in rate.
Didomi focuses obsessively on the user experience. Instead of an annoying banner, they offer elegant “Preference Centers” where users can fine-tune exactly what data they share. It’s a high-end product designed for brands that want to project trust.
Key Features:
- Support for dozens of global regulations simultaneously (GDPR, Law 25, CPRA).
- Beautiful, highly customizable preference centers.
- Advanced A/B testing to maximize opt-in rates.
- Deep integrations with CRM platforms like HubSpot.
Pricing: Custom enterprise pricing only.
Pros:
- The absolute best UI/UX in the industry.
- White-glove customer support and onboarding.
- Excellent developer documentation for SPA routing.
Cons:
- The cost is prohibitive for small projects.
- Setup requires dedicated project management.
Verdict: Didomi is perfect for luxury brands and high-end services that refuse to compromise on visual design and trust.
Comparison Table: Top SPA Cookie Consent Tools
Deciding which tool fits your stack requires looking at the raw specs. Here’s a direct comparison of how the top contenders handle the realities of modern web development in 2026.
| Platform | Pricing Base | Native SPA Routing | Consent Mode v2 | Best For |
|---|---|---|---|---|
| Cookiez | $49/year | Yes (Automated) | Native | Elementor/WP SPAs |
| Cookiebot | €12/month | Manual Hooks | Native | Automated Audits |
| Complianz | $59/year | Manual Hooks | Plugin Integration | Legal Document Gen |
| Borlabs | €39/year | Yes (Local Logic) | Native | Strict EU Compliance |
| Usercentrics | Custom | Yes (via SDK) | Native | Custom React/Vue |
Buyer’s Guide: What to Look for in an SPA Consent Platform
Don’t just install the first plugin you find. Evaluating these platforms requires understanding how they interact with your specific technology stack.
The biggest trap developers fall into is ignoring the History API. When a user clicks a link in your Elementor Editor Pro-powered SPA, the URL changes, but the browser doesn’t reload. If your CMP doesn’t watch for those specific pushState events, it won’t re-evaluate the scripts on the new page. You’ll end up firing unconsented tracking pixels, which completely defeats the purpose of the banner.
“Integrating consent in an SPA requires thinking about state management, not just DOM injection. If your consent manager doesn’t understand your routing lifecycles, you aren’t actually compliant. You’re just drawing a box on the screen.”
Itamar Haim, SEO Team Lead at Elementor. A digital strategist merging SEO, AEO/GEO, and web development.
You also need to heavily scrutinize performance benchmarks. Script size matters. Every kilobyte you add to the `
` blocks the main thread. Test the CMP’s impact on your Core Web Vitals before committing. A good tool shouldn’t add more than 50 milliseconds to your execution time.- Evaluate the Router Hook – Does the tool provide specific code snippets for React Router or Vue Router?
- Check the LCP Impact – Run a Lighthouse test before and after installation.
- Verify Consent Mode – Ensure the tool updates the
dataLayerstates dynamically on route changes. - Test the Fallbacks – What happens to your Elementor embedded videos if the consent API fails?
Honestly, we’ve seen too many sites ruin their UX with heavy banners. Pick a tool that respects your architecture.
Frequently Asked Questions
How do I trigger a re-scan on route changes?
Most advanced CMPs provide a manual JavaScript trigger (like Cookiez.reinit() or Cookiebot.run()). You must place this function call inside your application’s primary route change listener so it fires every time the view updates.
Is Google Consent Mode v2 mandatory for all sites?
If you collect data from users in the EEA or UK and send it to any Google service (Ads, Analytics), yes. It became strictly mandatory in March 2024 to maintain remarketing and personalized advertising capabilities.
Can I use Elementor Popups for cookie consent?
You can use the popup builder for the visual design, but you must connect the buttons to a proper Consent Management API. A visual popup alone doesn’t block background scripts or update the Google dataLayer correctly.
How does caching affect SPA cookie banners?
Aggressive page caching can serve outdated consent states. Always ensure your CMP executes strictly on the client side via JavaScript, bypassing the server-side cache entirely to read the user’s live local storage.
What is the TCF 2.2 framework?
The Transparency and Consent Framework is a standardized system created by the IAB Europe. It allows publishers to legally pass user consent signals down the chain to third-party advertising vendors in real-time.
How do I block YouTube embeds before consent?
You need a tool with an active content blocker. It intercepts the iframe rendering, replaces it with a static placeholder image, and only injects the actual YouTube source URL after the user explicitly accepts marketing cookies.
Do I need a CMP if I only use essential cookies?
If your SPA strictly uses technical cookies (like login sessions or shopping cart states) and uses zero analytics or marketing trackers, you generally don’t need a consent banner under GDPR. However, a privacy policy is still legally required.
Looking for fresh content?
By entering your email, you agree to receive Elementor emails, including marketing emails,
and agree to our Terms & Conditions and Privacy Policy.