Get started pages

Verify data is flowing

How to prove the SDK works using Installation Verify, Replays, Dashboard, network requests, and heartbeats.

What “verified” means

At least one of the following is true:

  1. In-app Installation → Verify shows live events (Page View, Click, Rage Click, …) and/or a live replay preview.
  2. Replays lists a new session you can open.
  3. Dashboard shows non-zero Visitors / Sessions / page activity for “today” (or your selected range).

If none are true after 2–3 minutes of using your app, treat install as not done.

Method A — In-app Verify step

  1. Open Installation (if still visible) or /projects/:id/get-started/sdk?step=verify.
  2. Keep your app open in another window.
  3. Click around your app (navigate, click buttons) for ~30 seconds.
  4. Watch the verify panel for live event types and the replay preview.

If the Installation link is gone, use Method B.

Method B — Replays + Dashboard

  1. Open your instrumented app (not only an iframe inside docs).
  2. Perform a short journey: home → another page → click something.
  3. Leave the tab open ~15–30s (heartbeats matter for “live” presence).
  4. In HumanBehavior: Replays → look for the newest row.
  5. Open it → confirm the player shows your UI.
  6. Open Dashboard → confirm KPI cards are not all empty for a sensible date range (try Today or Last 24 hours).
Replays after first session
Screenshots use a synthetic Docs Demo project, not customer data.

Method C — Browser network tab (developer proof)

  1. Open DevTools → Network.
  2. Filter for ingestion or your ingestion host.
  3. You should see requests such as:
    • /api/ingestion/events (after interact + the ~5s minimum-duration gate)
    • /api/ingestion/heartbeat (while the tab stays open)
    • possibly /api/ingestion/customEvent/batch, /errors, etc.
  4. You do not need /api/ingestion/init — the current SDK creates session/user ids locally and does not call init on startup.
  5. Status should be 2xx. 401/403 ⇒ wrong/missing key. Failed/blocked ⇒ ad blocker or wrong host.

Empty states you will see before data exists

Analytics pages often show a full-page empty state until the SDK is considered connected:

  • Title like No data yet / No replays yet / No users yet / No issues yet / No funnels yet
  • Primary button: Install Human Behavior
  • More optionsView demo, Book a call

That empty state is expected before a successful install. After data flows, it goes away.

Checklist if nothing appears

Work top to bottom — do not skip:

#CheckPass criteria
1API keySame project you are viewing; env var loaded (restart dev server)
2Init runsBreakpoint/log in client entry fires once in the browser
3Not SSR-onlyInit is in a client component / gatsby-browser / Nuxt client plugin
4Network 2xxIngestion requests succeed
5Ad blockerClean browser profile or reverse proxy
6Ingestion URLLocal apps point at ingestion (localhost:8000), not the Next dashboard port unless proxied
7Date rangeDashboard/Replays not filtered to an empty window
8Wait + refreshAllow ~1–2 minutes; hard refresh the product

Full matrix: I installed but see no data.