Opti-Behavior tracks front-end pages regardless of the theme or page builder that produced them, because it reads the rendered HTML the visitor actually sees. This article covers behavior with popular builders and how to keep the editor experience clean.
How compatibility works #
The tracking script runs on the public front end only. It is not loaded inside builder editors, so it never interferes with editing. Heatmaps and click tracking match elements by their rendered position and selectors, which works with any markup a builder outputs.
Tested builders and themes #
| Builder / theme | Tracking | Heatmaps | Notes |
|---|---|---|---|
| Gutenberg (block themes) | Yes | Yes | No configuration needed |
| Elementor | Yes | Yes | Script excluded from the Elementor editor automatically |
| Divi | Yes | Yes | Not loaded in the Divi Builder view |
| Oxygen | Yes | Yes | Works on rendered front end |
| Classic themes | Yes | Yes | No configuration needed |
Steps to verify a builder page is tracked #
- Open a page you built with your builder in a normal browser tab (not the editor).
- Go to WP Admin → Opti-Behavior → Dashboard and confirm the visit appears.
- Create a click heatmap for that URL and interact with the page to collect clicks.
Expected result #
Front-end visits to builder-made pages are recorded, and heatmaps render over the exact layout the visitor saw.
Troubleshooting #
- Heatmap looks misaligned: the builder may render different markup per device; use the matching desktop/mobile heatmap view.
- Dynamic popups not captured on the click map: elements injected after load are still clickable but may not appear in the static screenshot; see heatmap troubleshooting.
- No data on a builder page: confirm the page is a public URL and not gated behind a login.
FAQ #
Does the script load inside the builder editor? #
No. It runs only on the public front end, so editing is never affected.
Do I need a separate setup per builder? #
No. Tracking and heatmaps work the same across builders.
