Docs

Set up AskAnalytics

Everything here fits on one page, because the setup is genuinely one line of code.

Install

Add your site in the dashboard, then paste this snippet anywhere on your pages — the <head> is conventional, but any placement works:

<script async src="https://api.askanalytics.io/r.js"></script>

The script is keyed to your domain, so there is no site ID to manage. It loads asynchronously and sets no cookies. Once it is live, recording starts on its own — there is nothing to configure per campaign, and the same snippet works on Shopify, Webflow, WordPress, or anything else that renders HTML.

What gets recorded

Sessions that arrive from paid ads are always recorded. The recorder identifies paid arrivals from the click identifiers and campaign parameters ad platforms attach to their landing URLs — Google Ads, Meta, Microsoft, LinkedIn, TikTok, and others — and keeps them separated from the rest of your traffic.

You can also point the recorder at chosen conversion pages — a lead form, the checkout, your signup flow — so sessions on the pages where money is won or lost get recorded whatever brought the visitor. Set them under a site's Setup page in your dashboard. Outside the pages you choose, direct and organic visits stay unrecorded, which keeps your data and your bill scoped to the sessions that matter to you.

A recorded session captures what the visitor experienced: page structure, scrolling, clicks, form interactions, and errors. Every session is then read by AI and given a verdict, and the replay plus a plain-language transcript are available in the dashboard. Sessions judged to be bots are flagged and kept out of your audit numbers.

The morning digest

Each morning you receive an email summarising what yesterday’s recorded sessions did: verdicts by campaign, friction flags with linked replays, and any traffic that was never human. The digest goes to your account email; agencies can send white-label digests to clients from their own workspaces.

First-party serving

Optionally, serve the recorder from a subdomain of your own site so adblockers see first-party traffic and the sessions they normally hide still get recorded. In Setup, choose a subdomain (pick a neutral name — blockers target words like “analytics” and “track”), add the DNS record shown, and the snippet switches to your domain automatically once the certificate issues:

<script async src="https://data.yourdomain.com/r.js"></script>

Billing

Usage pricing is $9.99 per domain per month plus 5¢ per recorded session, whether that session came from an ad click or from a conversion page you chose to watch — the cost tracks what you record rather than your total traffic. Agencies can go flat at $499 per month with a million sessions and unlimited domains and client workspaces included. Cancel anytime; details on the pricing page.