Verify recording works

After you paste the snippet, you should see your first session land within 30 seconds. Here's how to confirm, and what to check if nothing shows up.

The 30-second check

1. Load any page on your site with the tag installed. Don't use an incognito window if you have ad-block extensions, some aggressive blockers strip third-party requests.
2. Move your mouse, click something, scroll. Replayful only records once it sees real activity.
3. In Replayful, open the project and refresh the Sessions tab. Your session should be at the top.

Nothing's showing

Open your browser's DevTools → Network tab and look for requests to app.replayful.co/api/ingest/sessions. They should return 200 OK. If you see no requests at all, the tracker script never loaded. If you see them failing with 401 / 403, the data-sitekey is wrong or the domain isn't allowlisted on the project.

Common causes

The script isn't loading

Open view-source: on your site (in Chrome / Firefox) and search for replayful. If the tag isn't there, it was never injected, check that you saved the file and pushed the change.

An ad-blocker is blocking it

Some content blockers categorise session-replay tools as analytics. Try the verification in a clean browser profile with no extensions. End users with blockers will be invisible to Replayful, that's usually fine for product research.

Wrong site key

Open the project's Install tab again and confirm the data-site attribute matches the one shown there. Site keys are unique per project; pasting a staging key on production (or vice versa) is the most common mistake.

Domain mismatch

The project's registered domain must match the page's host (or the www.variant). Subdomains aren't covered, they need their own project. If you're testing on localhost, register a project with domain localhost.

Content Security Policy

If your site has a strict script-src CSP, add app.replayful.coto the allowlist. You'll see a console error in DevTools telling you exactly what was blocked.