Heap·Analyticsheap auto-capture on every wordpress site.
paste a Heap environment ID, save, and the SDK loads in `<head>` capturing every click, form submit, and page change automatically. define events retroactively from the Heap UI — no code changes, no `track()` calls, no theme edits.
free trial. no credit card. all 30 integrations included on every plan.
Heap layers inside every wordpress site.
Heap doesn't ship an official WordPress plugin. The standard install is a theme-pasted snippet — which gets lost on theme switches, hard to maintain across child themes, and has no validation if you paste the wrong env ID.
every interaction — captured before you ask.
Heap doesn't wait for `track('Signup Completed')`. it captures every click, form submit, scroll, and route change. you decide what counts as a conversion later, in the Heap UI, against historical data you didn't have to predict.
button.cta-primary/pricingpage_view/pricingform#newsletter/scroll_75/blog/why-wpa.docs-link/page_view/click on .cta-primary on /pricingpaste env ID. auto-capture lights up.
Yovale validates the numeric env ID at save. the MU-plugin loads the Heap SDK in `<head>` with auto-capture enabled, gated against analytics consent.
- 1Open Tracking → Analytics
Find Heap in the dashboard's tracking panel.
- 2Paste your environment ID
Copy from Heap → Account → Manage → Projects → Environments. format: 8–12 digit numeric.
- 3Toggle on, save
Open your site. Heap captures every click and form submit. Define events later in the Heap UI.
1234567890Heap issues this when you create an environment. format: 8–12 digit numeric.
Heap covers every interaction.
every click + submit + page view + scroll captured without `track()` calls.
define new events from the Heap UI — counts historical data, not just future events.
fires only after analytics consent. EU traffic stays compliant by default.
platform-layer install — switch themes anytime, Heap stays wired up.
questions before you switch hosts for Heap.
What does 'auto-capture' mean for retroactive analytics?
Heap captures every interaction by default. You define what counts as an event in the Heap UI later — meaning you don't have to predict your future analytics needs at instrument time.
Will Heap inflate my page weight?
Heap's SDK is around 50KB compressed. It loads async from `<head>`, so it doesn't block first paint. Compared to a typical WordPress analytics plugin that adds PHP overhead per request, the cost is lower overall.
Does Heap respect EU consent?
Yovale gates the SDK behind the analytics consent signal. If the visitor declined analytics cookies, Heap doesn't load. Heap's own privacy controls layer on top.
Can I run Heap with Mixpanel or Amplitude?
Yes — but they overlap heavily. Most teams pick one of the three for product analytics. Heap fits when you don't want to predefine events.
Will the page cache strip Heap?
No. The snippet is part of the cached HTML. Event capture happens client-side via the SDK.
tools that overlap with Heap on every WordPress site.
competitor product analytics — pre-defined events vs Heap's retroactive model.
another product analytics option — strong for cohorts and journeys.
open-source alternative with auto-capture + replay + flags.
free heatmaps + recordings to complement Heap's quantitative side.
Heap retroactive analytics on WordPress by day one.
free trial. no credit card. paste an env ID, save, and Heap captures everything for retroactive analysis.