Skip to main content

Monitoring quickstart

Turn on Monitoring, add the script, and confirm it's reporting — in four steps.

On this page

Set up monitoring

  1. Create a site key

    Sign in and open your domain — or add one if you haven't yet — then open Monitoring in the sidebar and click Enable monitoring. That creates your site key and shows the snippet to install, already carrying the key.

    Monitoring is available on the free Monitor plan — no card required.

  2. Add the script

    HTML
    <script src="https://accessible.so/a11y/loader.js" data-site-key="acc_rum_YOUR_SITE_KEY" async></script>

    Paste it into every page's <head>, or just before </body> — either works. Replace acc_rum_YOUR_SITE_KEY with the real key from your dashboard; the Install snippet on the same card already carries it.

    Building on a specific platform? See Install for platform-specific steps.

  3. Check it's working

    Open a page with ?a11y_debug=1 appended to the URL. That forces sampling for the rest of the tab's session and turns on console.debug output from the collector (set the console to show verbose messages), so you can watch it run without waiting for the configured sample rate to pick your visit.

    Test it on the live domain the site key belongs to — a new site's Allowed hosts default to that domain and its www. variant, and a beacon from any other host is silently dropped. Add the host you're testing on to Allowed hosts if it isn't one of those. See Debugging for what to look for in the console and the network tab.

  4. See results

    Back on the Monitoring page, "Waiting for the first data from your site…" changes to your monitoring data as soon as visitors load pages carrying the script: what they hit, sessions per day, and new pages they reached.

Note

Your site key is public by design. It's embedded in the script tag on your own page, so anyone who loads your site can read it — there's nothing to keep secret. If it ends up somewhere you'd rather it wasn't, rotate it from your domain's settings page (see Configuration).