Pro Plan10 minutesintermediate

Troubleshooting Recordings

Fix common session replay and heatmap issues - missing recordings, visual glitches, performance problems, and data accuracy.

session-replaytroubleshootingheatmapsissues
Last updated: January 15, 2025
Pro Plan

Solve common session replay and heatmap issues with this troubleshooting guide.

No Recordings Appearing

Check Recording Status

First, verify recording is enabled:

  1. Go to your domain dashboard → Sessions tab
  2. Confirm "Enable Recording" is on
  3. Check for any error messages

Verify Tracking Script

Ensure the script is installed:

  1. View page source
  2. Search for "zenovay"
  3. Verify script loads without errors

Check Console for Errors

Open browser console:

  1. Right-click → Inspect
  2. Go to Console tab
  3. Look for Zenovay errors

Common errors:

ErrorSolution
Script not foundReinstall tracking code
CORS errorCheck domain configuration
Blocked by CSPUpdate Content Security Policy
Network errorCheck internet/firewall

Plan Limits

Verify your plan includes session replay (Pro plan or higher) and that recordings are within the retention period:

PlanRetention
Pro60 days
Scale120 days
Enterprise180 days

If using consent:

  • Verify consent is being given
  • Check consent integration
  • Test with consent granted

Recordings Not Playing

Loading Issues

If playback won't start:

  1. Refresh the page

    • Clear cache if needed
  2. Check internet connection

    • Try different network
  3. Try different browser

    • Chrome recommended
  4. Disable extensions

    • Ad blockers may interfere

Playback Errors

If you see error messages:

ErrorSolution
"Failed to load"Session may be corrupted
"Session expired"Beyond retention period
"Access denied"Check permissions
"Invalid session"Contact support

Browser Requirements

Ensure browser supports:

  • WebGL
  • Modern JavaScript
  • Sufficient memory

Visual Glitches

Missing Content

If elements appear blank:

CauseSolution
Privacy maskingCheck mask settings
Dynamic contentMay load differently
Third-party contentCannot capture cross-origin
Lazy loadingMay not capture before load

Incorrect Styling

If styling looks wrong:

  1. Font substitution

    • Custom fonts may not load
    • Fallback fonts used
  2. CSS differences

    • Some dynamic CSS may differ
    • Check for CSS-in-JS issues
  3. Responsive issues

    • Viewport may differ
    • Breakpoint differences

Missing Images

Images may not appear if:

  • Served from different domain
  • Protected by authentication
  • No longer available

Layout Shifts

If layout doesn't match:

  • Dynamic content changes
  • A/B test variants
  • Time-based content

Heatmap Issues

Empty Heatmap

If heatmap shows no data:

  1. Check session count

    • Need sufficient data
    • View in correct date range
  2. Verify page URL

    • Exact match required
    • Check for query parameters
  3. Check device filter

    • Mobile/desktop selected?
    • Matches traffic type?

Inaccurate Click Data

If clicks seem off:

IssueCause
Clicks on wrong elementsViewport differences
Clustered incorrectlyResponsive layout changes
Missing clicksSampling or limits

Scroll Data Missing

If scroll heatmap empty:

  • Verify scroll events captured
  • Check page length
  • Confirm JavaScript running

Performance Issues

Slow Playback

If playback is choppy:

  1. Reduce playback speed

    • Try 0.5x or 1x
  2. Close other tabs

    • Free up memory
  3. Check network speed

    • Buffering may occur
  4. Try a different browser

    • Chrome often fastest

High Resource Usage

If consuming too much CPU/memory:

  1. Skip to relevant sections

    • Don't play entire session
  2. Close event panel

    • Reduces rendering
  3. Disable animations

    • In settings if available

Site Performance Impact

If recording affects your site:

  1. Check script version

    • Update to latest
  2. Reduce recording scope

    • Exclude heavy pages
    • Limit to key pages
  3. Monitor metrics

    • Check Core Web Vitals
    • Compare with recording off

Data Accuracy Issues

Session Count Mismatch

If counts don't match analytics:

ReasonExplanation
SamplingMay sample on high traffic
ConsentNot all users consented
Ad blockersBlock recording script
Page typesSome pages excluded

Duration Differences

If duration seems wrong:

  • Idle time may be skipped
  • Tab switching affects timing
  • Background tabs may pause

Click Count Variance

Click counts may differ from analytics:

  • Heatmaps may sample
  • Different click definitions
  • Viewport/element matching

Configuration Issues

Masking Too Aggressive

If too much is masked:

  1. Review mask selectors
  2. Test with less restrictive rules
  3. Use specific selectors

Masking Not Working

If sensitive data visible:

  1. Check selector syntax

    • Test in browser console
  2. Verify configuration loaded

    • Before page renders
  3. Use data attributes

    • More reliable than CSS classes

Excluded Pages Recording

If excluded pages appear:

  1. Check URL pattern
  2. Verify wildcards correct
  3. Test pattern matching

Integration Issues

If not integrating properly:

  1. Check timing

    • Consent before recording
  2. Verify events

    • Consent signals firing
  3. Test manually

    • Grant consent, check recording

Single Page Apps

SPA-specific issues:

IssueSolution
Page changes not capturedEnsure SPA mode enabled
Duplicate sessionsCheck session handling
Missing navigationVerify route change tracking

Third-Party Scripts

Conflicts with other tools:

  1. Check for script conflicts
  2. Verify load order
  3. Test in isolation

Data Recovery

Lost Sessions

Unfortunately:

  • Deleted sessions cannot be recovered
  • Expired sessions are permanently removed
  • Export before retention ends

Corrupted Sessions

If sessions appear corrupted:

  • May be partial upload
  • Network interruption during capture
  • Contact support with session ID

Getting Help

Information to Provide

When contacting support:

  1. Session ID (if specific session)
  2. Page URL affected
  3. Browser and version
  4. Error messages
  5. Steps to reproduce
  6. Screenshots/recordings

Support Channels

Debug Mode

Enable debug logging by adding data-debug to your script tag:

<script defer
  src="https://api.zenovay.com/z.js"
  data-tracking-code="YOUR_TRACKING_CODE"
  data-debug="true">
</script>

Check console for detailed logs.

Preventive Measures

Regular Testing

Test recording periodically:

  • After site updates
  • After tracking changes
  • After consent updates

Monitoring

Set up alerts for:

  • Recording count drops
  • Error rate increases
  • Performance changes

Documentation

Keep records of:

  • Configuration changes
  • Exclusion rules
  • Known issues

Next Steps

Was this article helpful?