You can now set up and connect Sigmize to your site from within WordPress, through a self-serve onboarding flow powered by ZipWP.
See Your Test Performance on the WordPress Dashboard New
A new dashboard widget in WordPress gives you an at-a-glance summary of this site’s testing, right where you already work.
The widget shows how many experiments you have, your total impressions, your conversion rate, and which tests are currently running. You get the headline numbers without opening Sigmize, so you can keep an eye on performance as part of your normal WordPress routine.
Example
Check your conversion rate from the WordPress dashboard.
See which experiments are running right now without opening Sigmize.
Track total impressions across your tests at a glance.
Catch a running test that needs attention sooner.
This keeps your key testing numbers in view wherever you spend your time.
Improvements
WordPress 7.1 Compatibility Improved
Sigmize is now fully compatible with WordPress 7.1.
You can update to the latest version of WordPress and keep running your experiments without any issues. Everything the plugin does, from serving your tests to recording results, works as expected on 7.1.
Example
Update to WordPress 7.1 with your experiments running as normal.
Stay on the latest WordPress without waiting on the plugin.
This keeps Sigmize working smoothly as WordPress moves forward.
Heatmap background images are now captured by a real browser on our servers instead of being rebuilt inside your visitor’s browser.
The old approach reconstructed your page from the visitor’s side, which often produced backgrounds that did not match the live page. Background images could drop out, centred and viewport-based layouts could shift, and content that loads as you scroll frequently came through blank. Server-side capture takes an actual screenshot of the page, so heatmap backgrounds now look like the page your visitors saw. Each heatmap version also keeps its own image, so archived versions stay frozen with the background they were recorded against instead of picking up a newer one. If our servers cannot reach a page, for example a page behind a login, capture falls back to the visitor’s browser as before.
Example
See heatmap backgrounds that match your live page, including background images and gradients.
Get accurate backgrounds on centred or full-width layouts.
Capture sections that only load once a visitor scrolls down.
Review an archived heatmap version and still see the page as it looked at the time.
This makes heatmaps far more trustworthy to read, since the clicks and scroll data now sit on top of an accurate picture of your page.
Disabled Cookie Consent Is Now Honoured Improved
Turning cookie consent off now genuinely turns it off across tracking.
Previously, if a workspace had selected a consent management platform such as Cookiebot and then switched cookie consent off, the tracking script kept waiting for a consent signal that could never arrive. A/B tests still displayed normally, so tracking looked healthy, while conversions, heatmap events, and session replays were silently recording nothing. Workspaces using a custom banner had a worse version of the same problem: the banner kept reappearing on every page load and could not be accepted or dismissed.
Switching consent off now takes effect immediately. Tracking runs without waiting for consent, any custom banner stops showing, and previously stored consent data is cleared from the visitor’s browser. The change is also pushed to connected WordPress sites so their settings stay in sync.
Example
Switch cookie consent off and have conversions start recording right away.
Stop a stale consent banner from reappearing on every page load.
Keep collecting heatmaps and session replays after removing a consent tool from your site.
Rely on your connected WordPress site reflecting the change automatically.
Note: your tracking script is cached for around five minutes, so allow a few minutes for the change to reach your site.
Sigmize is now available in 22 languages, making it easier for teams around the world to use the platform in their preferred language.
You can switch your language at any time using the Language Switcher in the header or by navigating to Profile → Interface Language. Once selected, your preference is saved to your account and automatically follows you across browsers and devices.
Every major area of the platform is translated, including dashboards, experiments, heatmaps, session replays, reports, settings, and more.
Supported languages:
English
Spanish
French
German
Portuguese
Portuguese (Brazil)
Italian
Dutch
Swedish
Polish
Czech
Greek
Russian
Turkish
Arabic
Hebrew
Japanese
Korean
Simplified Chinese
Indonesian
Vietnamese
Thai
Example
Work in your preferred language without changing browser settings.
Teams in different regions can each use Sigmize in their own language.
Your selected language automatically syncs across all devices after signing in.
Switch languages anytime from your profile without affecting your experiments or workspace.
Additionally, Arabic and Hebrew now include proper Right-to-Left (RTL) support, providing a natural and optimized experience for RTL language users.
This content is blocked because it requires YouTube cookies.
New Features
Product-Specific Conversion Tracking for eCommerce Goals New
You can now track conversions for specific products or product variations when using eCommerce experiment goals.
Previously, if you configured an eCommerce goal (such as WooCommerce Order Completed), every purchase made after visiting the experiment was counted as a conversion, regardless of the product purchased.
Now you can specify one or more Product IDs or Product Variation IDs. Only purchases of those selected products will be counted as experiment conversions.
Example
Track conversions only for your Premium Plan product.
Measure the performance of a landing page promoting a specific course.
Test different product pages and only count purchases of the featured product.
Exclude unrelated purchases from affecting your experiment results.
This gives you much more accurate conversion data for product-focused A/B tests.
Mobile, Tablet & Desktop Heatmap ScreenshotsNew
Heatmaps now support Desktop, Tablet, and Mobile screenshots.
Screenshots are automatically generated based on the visitor’s device. Instead of viewing only desktop interactions, you can now analyze user behavior separately across all major device types.
You can also delete an existing screenshot and regenerate it whenever needed.
Example
Compare how users interact with your page on desktop versus mobile.
Identify mobile usability issues separately from desktop.
Analyze tablet-specific engagement patterns.
Refresh screenshots after making design updates.
This provides a much more complete understanding of user behavior across different devices.
Improvements
Recapture Heatmap Screenshot Improved
We’ve added a Recapture Screenshot button for every supported device inside Heatmaps.
If a screenshot hasn’t been generated or needs to be refreshed, simply click Recapture Screenshot. The page opens in your browser and automatically captures a fresh screenshot for that Heatmap version.
Example
Generate screenshots for newly synced page versions.
Refresh outdated screenshots after page updates.
Quickly regenerate missing screenshots without creating a new experiment.
Variant URL Display in Heatmaps Improved
The Variant URL is now displayed directly inside each Heatmap.
You can easily copy the URL whenever needed for verification, debugging, or sharing with your team.
Heatmap Version DetailsImproved
Each Heatmap version now displays its recording date range alongside the selected device type under the Variant heading.
This makes it easier to understand exactly when a Heatmap version collected visitor data.
Subscription renewals, upgrades/switches, and resubscribe orders will no longer be counted as conversions for Order Completed (Revenue) goals or custom revenue events.
Only initial or one-time purchases are counted as experiment conversions.
This content is blocked because it requires YouTube cookies.
Heatmap Versioning New
You can now create multiple versions of Heatmaps inside Sigmize.
Previously, if you updated a variant page after running an experiment, you had to create an entirely new experiment to analyze user behavior on the updated version.
Now, whenever you update a page used in an experiment (such as adding new sections, buttons, layouts, or content), click Sync Page inside Heatmaps.
Once synced, any new visitors landing on that updated page will automatically generate heatmap data under a new Heatmap version, while preserving historical heatmap data from previous versions.
This allows you to continuously optimize the same experiment without losing historical insights.
Example
Create an experiment and generate Heatmap Version 1
Add a new CTA button and redesign the hero section on the variant page
Click Sync Page inside Heatmaps
New visitors automatically generate Heatmap Version 2
Compare how users interacted before and after the page update
Additional use cases:
Measure the impact of UI changes without creating duplicate experiments
Track how engagement changes across page iterations
Preserve historical behavior while collecting fresh insights
Continue optimization cycles within the same experiment
This makes experimentation faster and helps teams iterate confidently without restarting analysis from scratch.
This content is blocked because it requires YouTube cookies.
New Features
Visitor Limits for Experiments New
You can now set individual visitor limits for each experiment in Sigmize. This allows you to control how many visitors a specific experiment can consume from your overall account visitor quota.
Instead of one experiment consuming most of your available traffic, you can allocate visitor limits strategically across multiple experiments.
Example
Your account has a limit of 500 visitors
Allocate 100 visitors to Experiment A
Allocate 50 visitors to Experiment B
Allocate 200 visitors to Experiment C
Each experiment will stop consuming visitors once its allocated limit is reached, helping you distribute traffic more effectively and ensuring one experiment doesn’t exhaust your entire account quota.
This gives you better control over experiment planning, traffic allocation, and testing priorities.
Improvements
Optimized Session Recording Playback Improved
We’ve significantly improved session recording performance for longer recordings.
Previously, long session recordings (such as 30-minute recordings or longer) could fail to load and display fatal errors during playback.
This content is blocked because it requires YouTube cookies.
New Features
New CMP – Complianz New
We’ve added support for Complianz inside Settings → Privacy & Legal, giving you a seamless way to manage user consent and stay compliant.
How this helps you
Automatically handle cookie consent without complex setup
Ensure tracking and experiments respect user consent preferences
Stay aligned with privacy regulations like GDPR
Example use case
You’re running an A/B test on your landing page:
A visitor sees the consent banner powered by Complianz
If they accept → your experiment tracking starts normally
If they decline → tracking is paused, keeping you compliant
This ensures your data is both accurate and legally compliant.
New Legal & Privacy Hub (Transparency & Compliance in One Place) New
We’ve introduced a dedicated Legal & Privacy page where you can easily access and manage compliance-related information.
What you can do here:
View Privacy Policy → Understand how your data is collected and used
Check Sub-processors → See which third-party services handle data
Request a DPA (Data Processing Addendum)
A DPA helps ensure your business complies with regulations like GDPR when handling user data.
Example use case
If you’re working with EU customers → You can request a DPA for compliance
If you’re evaluating tools → You can review sub-processors for transparency
DPAs are typically required for businesses handling regulated data. Most hobby or free users won’t need this.
̌Bug Fixes
Cloned Experiments Missing Editor Data FIXED
Cloning experiments with element-based variations now work correctly. Previously, cloned experiments didn’t load properly in the visual editor, preventing updates.
Result: You can now clone experiments and immediately edit variations without any missing data issues.
Unable to Delete Expired Invitations FIXED
Resolved an issue where deleting expired invitations showed the error: “Cannot cancel a non-pending invitation.”
Result: Expired invitations can now be removed smoothly without errors.
This content is blocked because it requires YouTube cookies.
New Features
Two-Factor Authentication (2FA) New
Add an extra layer of security to your account with 2FA. You can enable, disable, and regenerate recovery codes directly from your settings.
Example
Each time you log in, you’ll receive a verification code on your email or on the authenticator app—ensuring that even if someone has your password, they cannot access your account without the code.
CSV Export for Detailed Analytics New
You can now export Detailed Analytics reports as CSV files for deeper analysis in tools like Excel or Google Sheets.
Example
Download experiment data with rows for each variation and columns for Total, Count, and Percentage—making it easy to compare A/B test performance and share insights with your team.
Session Recordings — Filters & Sorting New
Quickly find the most relevant session replays using advanced filtering and sorting options.
Example
Filter sessions where users dropped off on a checkout page
Sort recordings by duration or activity to identify high-engagement sessions
Focus only on sessions that matter most to your analysis
Multi-Site WordPress Support New
Sigmize now supports WordPress Multisite (network) installations, allowing you to seamlessly connect and manage multiple sites within a single WordPress network. This ensures consistent data syncing and unified experiment tracking across all subsites.
Example
Run and analyze A/B tests across all subsites in your WordPress Multisite network from one place—without needing to configure each site separately or worry about inconsistent data syncing.
Sigmize MCP Server New
Sigmize now supports Model Context Protocol (MCP), allowing AI tools and automation systems to connect directly to your account using secure API keys with custom permissions.
Example
Use AI assistants to fetch analytics data instantly
Automate A/B test creation and monitoring
Manage experiments programmatically without manual intervention
Improvements
More Accurate Conversion Tracking Improved
Conversion tracking is now more reliable, ensuring real user actions like purchases and form submissions are no longer flagged as bot traffic.
Benefit: Get accurate experiment results and make better data-driven decisions without misleading metrics.
Enhanced Account Security Improved
Multiple security improvements have been implemented across the platform to strengthen account protection.
Benefit: A safer and more secure experience while managing your experiments and data.
