Get started4 min read

Verify your install

Mrkr checks for your first pageview automatically. If you'd rather watch it happen live, data-debug logs every request the tracker makes.

Automatic verification

The Install page in your dashboard polls in the background for the first sign of traffic. As soon as a session lands, the page updates itself, no reload required.

Note

This only requires one real pageview from your site: you don't need to click anything or take any extra step beyond loading a page.

See it happening: data-debug="1"

Add data-debug="1" to your script tag temporarily and open your browser's console:

html
<script defer src="https://mrkr.app/tracker.js" data-site="YOUR_SITE_ID" data-debug="1"></script>

With it on, the tracker logs the server's response to your first pageview (including whether session replay is enabled for the site), and, if replay is on, every step of starting a recording: whether the sample-rate dice roll included this session, and confirmation once capture begins. Remove the attribute once you've confirmed things work; it's a debugging aid, not something to ship permanently.

Note

One warning is printed regardless of data-debug: if session replay is enabled but the rrweb capture script fails to load (blocked by a CSP, 404, network issue), the tracker always logs a console.warn with the URL it tried to fetch.

What counts as "verified"

The dashboard looks for at least one session recorded in the last hour. A session is created the moment a pageview from a real browser (not a bot, not an excluded path) reaches the collect endpoint, so a single successful pageview is enough.

Nothing showing up? Check these first

  • Wrong domain. The site you tested from doesn't match the domain configured for this site id (including localhost or a staging subdomain). Events from an unrecognized origin are silently dropped rather than counted. Test from the real domain, or update the site's domain in settings first.
  • The script never loaded. Check your page's network tab for a request to tracker.js: a typo in the src, a Content-Security-Policy blocking the host, or the tag living outside <head> will all prevent it from running.
  • The path is excluded. If you've added excluded paths in settings, a matching page is dropped before it's tracked at all: check your pattern list.
  • You're testing with browser automation. Selenium, Puppeteer, and Playwright set navigator.webdriver = true by default, which is one of the strongest bot signals Mrkr checks. Those sessions are intentionally never counted.
  • An ad blocker is active. Some blocklists match tracker.js or /api/collect by name. If this is a recurring problem for your audience, the managed proxy serves the tracker from your own domain instead.
  • Wrong site id. Double check the data-site value against the one shown on your dashboard's Install page: a stray character means events go to a site id that doesn't exist and are rejected.