Checklist

Session replay and heatmaps before Accept: what to check

Run the free scan

Session replay records a playable visit. Heatmaps aggregate clicks and scrolls. Check what fires before Accept. A free US-baseline scan is not legal advice.

In brief

Session replay and heatmap tools often load early so they can catch the first seconds of a visit. A cookie audit shows whether those scripts, cookies, or beacons appeared before Accept. It does not decide whether counsel would allow that load. First-party wrappers still count for the timing test. ConsentProbe lists the findings. A free US-baseline scan is not an EU or California legal conclusion. This page is testing guidance, not legal advice.

This guide explains how to observe session replay, heatmap, and similar recording scripts that load before Accept. It is not legal advice, not a ruling that any vendor is permitted or forbidden before a choice, and not a GDPR, ePrivacy, or CPRA certificate. ConsentProbe reports are technical observations of what fired. They do not say what counsel would allow.

Last updated October 8, 2026. The before-Accept audit owns the full protocol. The first-party versus third-party guide owns the party labels. The pre-consent checklist owns the multi-step pass. This page covers replay and heatmap timing, including what each one records. The session replay versus heatmaps FAQ still covers which surface to check first.

Short answer

Session replay and heatmap tools often load early to catch the first seconds of a visit. A cookie audit answers whether those scripts, cookies, or beacons appeared before the visitor clicked Accept. It does not answer whether counsel would allow that load.

In a clean profile, load without clicking the banner, watch Network for recording or heatmap hosts, open Application, then Cookies and storage, for related IDs, and keep screenshots. A first-party wrapper on your own domain still counts as a before-Accept finding if it sets a recording ID early.

ConsentProbe can list those findings with request and cookie surfaces. For a side-by-side which-to-check-first FAQ, see session replay versus heatmaps. A free US-baseline scan is not an EU or California legal conclusion. ConsentProbe does not install a CMP. This page is testing guidance, not legal advice.

Session replay vs heatmaps: what each one records

Heatmaps aggregate click, scroll, and move positions. Session replay stores a per-visitor stream of DOM changes and events that can be played back. The browser sends the page structure with those events. That is more than a list of positions, and the recorder usually posts more than one beacon.

Run both checks on the same Fresh visit, then again after Reject. A heatmap host on Fresh does not show that replay stayed off. The audit records what fired. It does not decide permission.

Swipe to see more

Heatmaps and session replay on Fresh and after Reject.
CheckHeatmapsSession replay
What is capturedAggregated click, scroll, and move positionsA per-visitor DOM and event stream that can be played back
Typical network patternA script plus position beaconsA script plus an event stream, so more leaves the browser
Fresh, before AcceptHeatmap or UX hosts and position beaconsRecording hosts, session IDs, and event posts
After RejectWhether those hosts and beacons stopWhether the script, session ID, and event posts stop

Keep the two questions in different columns. The runtime test can fill the first and the third. Counsel fills the middle. In the note you hand engineering, write present before Accept. Leave permitted and lawful off the ticket unless a lawyer wrote them.

Swipe to see more

What a pre-Accept replay check can record, and what it leaves to counsel.
QuestionWho answers itWhat you capture
Did a session replay or heatmap script, cookie, or beacon appear before Accept?Runtime test or auditHost, cookie name, storage key, timestamp, and screenshot
Is that load permitted in this jurisdiction?Counsel or the compliance policyOutside what a ConsentProbe report claims
Was it first-party or third-party?The same runtime testDomain context, using the party-label guide for the definitions

Signals you can see

On Network, flag hosts or paths that look like session recording, heatmaps, or UX analytics. Hotjar, FullStory, and Microsoft Clarity are examples of that class. On two Shopify stores, FullStory kept recording after Reject. The names are examples only. This page does not rank vendors or tell you which script to block. On Shopify, confirm whether Clarity still records after Reject All.

On cookies and storage, flag IDs or session keys written before a choice, including copies on your own domain. A purpose label inside the CMP is a claim. Network timing and the cookie list are what this pass verifies. When you need the first-party versus third-party definitions, open that guide.

Five-step check before Accept

Stop after these five steps if you only need the replay and heatmap inventory. Open the before-Accept audit for the longer protocol, and the pre-consent checklist when you also want Reject and an accept baseline. A later Reject All comparison belongs on the Reject leftovers guide.

  1. Use a clean browser profile. Do not click Accept or Reject.
  2. Load the storefront once. Open Network and filter for recording, heatmap, or analytics-looking hosts.
  3. Open Application, then Cookies and storage. Flag related IDs on your domain and on third-party domains.
  4. Screenshot the network rows and the cookie list. Write one finding sentence per distinct vendor or ID.
  5. Optional: compare after Reject All if the claim is that recording stays off. Use the Reject leftovers guide for that depth.

When hand-sorting the hosts gets slow

Sorting replay and heatmap fan-out by hand is slow once themes and apps change. ConsentProbe runs on the URL and stores a labeled pre-consent Fresh inventory. Each finding stays tied to a request, a cookie, or a screenshot.

Use the free US-baseline visit when you want the report format. Use paid EU or California scenarios when those regions are the claims you will show. The free versus paid guide draws that line. ConsentProbe does not install a CMP and does not approve vendors for counsel.

FAQ

Do session replay and heatmaps both need a Fresh check?

Yes. Check both on the same Fresh visit. One cold category does not prove the other stayed off.

Where is the replay versus heatmaps comparison?

This page says what each one records and stays the combined before-Accept checklist. The session replay versus heatmaps FAQ covers which surface to check first.

Is session replay riskier than heatmaps for consent?

Replay usually sends a playable DOM and event stream. Heatmaps usually send aggregated positions. Compare hosts, cookies, and posts on Fresh and on Reject. A free US-baseline run is US technical evidence, not a GDPR or California legal conclusion.

Are heatmaps allowed before Accept?

Permission is a legal call. The audit answers whether they fired before Accept. It does not grant permission.

Do first-party replay cookies skip the timing test?

No. A recording ID on your own domain still counts if it appears before Accept. Party labels live on the first-party versus third-party guide.

Where is the full before-Accept protocol?

The before-Accept audit is the long protocol. The pre-consent checklist is the pass order. This page is the replay and heatmap slice.

Does a free US-baseline decide EU or California permission?

No. A free US-baseline scan shows report format. It is not an EU or California legal conclusion. See the free versus paid guide.

Is this legal advice?

No. These are technical observations. ConsentProbe does not replace counsel, and it does not install a CMP.

Limits of this page

This page tells you how to observe session replay and heatmap scripts, cookies, and beacons before Accept. It is not legal advice, not a vendor review, and not a certificate under GDPR, ePrivacy, CPRA, or any other rule. ConsentProbe reports stay tied to requests, cookies, and screenshots. A free US-baseline scan is not an EU or California legal conclusion.

Open the before-Accept audit for the full protocol, the party-label guide for first-party versus third-party, and the pre-consent checklist for the pass order.

Sources

These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.

Save a US-baseline technical record

After a DIY check, run a free US-baseline scan: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.

Session Replay vs Heatmaps Before Accept | ConsentProbe