Sharper Heatmap Backgrounds & Correct Cookie Consent Handling

Improvements

Server-Side Heatmap Background Capture Improved

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 Team
July 30, 2026

Sigmize is Now Available in 22 Languages

New Features

Multi-Language Platform Support New

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.

Sigmize Team
July 16, 2026

Multi-Device Heatmaps & Product-Specific Conversion Tracking

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.

Improved WooCommerce Subscription Conversion TrackingImproved

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.

Sigmize Team
June 25, 2026

Heatmap Versioning

New Features

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.