Every feature is designed to fix a specific Matomo heatmap capture issue.
Auto-detects and expands all scrollable areas so you capture the complete page, not just what's visible.
Automatically fixes background-attachment issues that cause parallax effects to render incorrectly in screenshots.
Take screenshots of heatmaps that have already ended or expired, preserving historical data analysis.
Capture heatmaps that have exceeded Matomo's sample rate limit, ensuring you can still document insights.
Fixes relative height elements that collapse or display incorrectly during screenshot capture, without manual CSS fixes.
One-click manual screen capture when you need precise control over timing and capture settings.
Automatically resolves images with relative paths to be loaded correctly.
Handles CORS issues related to fonts by embedding them as base64 strings.
Three simple steps to get started with Matomo heatmap helper.
Install Matomo Heatmap Helper from the Chrome Web Store.

Securely provide your Matomo API credentials to the extension.

Select the heatmap you want to capture and click the capture button.

Inspect the code yourself. Your data never leaves your browser. Zero tracking. Zero servers. Zero BS.
Star, fork, and contribute. The entire source code is available for inspection.
This extension comunicates solely with your Matomo instance.
Built by Matomo users, for Matomo users. Contribute, report issues, request features.
Common questions about the Matomo Heatmap Helper extension.
Currently, we support Chrome, Edge, and other Chromium-based browsers. Firefox support is coming soon.
Yes! The extension works with both Matomo Cloud and self-hosted Matomo instances. No configuration needed.
This extension only communicates with your Matomo instance. No data is sent to any other external servers or the developers.
We welcome all feedback! Open an issue on our GitHub repository. The extension is open source, so you can also submit pull requests.
No. This extension only works with matomo instances that have the Heatmap Plugin installed and enabled.
No. Your API URL and auth token are stored in chrome.storage.local, which is isolated by the browser and only accessible to the extension itself. Web pages cannot read extension storage, even when the extension's content script is active on that page.