One script tag, no cookie by default.

The script is served from https://cdn.tapll.com/v0/u.js, has no dependencies and weighs under 5 KB gzipped. It reports to the same project as your app, so a site and the app it advertises sit in one panel with a switcher for the platform.

Start for freeRead the docs

What you get. Once Website script is connected.

  • Traffic

    Visitors, visits, page views, bounce rate, visit duration and pages per visit, each against the previous period.

  • Where people come from

    Channels (direct, search, social, email, paid, referral), referrers and UTM campaigns, plus top, entry and exit pages, browsers, systems, devices and countries.

  • Live and interactions

    Visitors on the site right now, single-page navigation, outbound links, downloads, and clicks tagged with `data-tapll-event`.

  • Features from code

    Custom events and feature funnels (discovery → adoption → success), declared with `tapll.feature()` exactly as in the app.

What it needs.

  • One `<script defer src="…/u.js" data-key="av_…">` in the `<head>` of every page, with the project’s client write key (public by design).
  • Optionally the site’s domains, so a copied snippet on another host is refused.
  • For ad blockers, optionally a proxy through your own domain, with `data-api` pointing at it.

Add the website script in the docs

What Tapll keeps, and what it does not.

  • The path of each page, never the query string or the fragment; UTM parameters are read from the landing URL.
  • In strict anonymous mode, nothing in the browser: the visitor is a server-side hash with a daily salt, and the IP address is truncated before it is stored.
  • In product analytics, an anonymous id and the session in localStorage, optionally behind Tapll’s consent banner or your own consent tool.
  • Bots are filtered out before they reach the numbers.

Questions about Website script.

Do I need a cookie banner?

Not in strict anonymous mode, the default: the script stores nothing in the browser. In product analytics the script stores an id, and whether that needs consent is your call. Tapll’s banner is optional and off by default: `data-consent="banner"` shows it with Accept and Decline given equal weight, and nothing is stored or sent until the visitor answers. This is how the product works, not legal advice.

Why does a returning visitor count again?

Without a cookie a visitor is recognised for one UTC day only, so someone who returns on three days counts three times in a multi-day window. The panel says so under the number. Product analytics recognises people across visits.

Does it measure Web Vitals or JavaScript errors?

No. Tapll does not report Web Vitals, JavaScript errors, session replays or heatmaps, and there is no npm package or framework plugin: the tag is the whole install.

Will an ad blocker hide my visitors?

Some blockers stop third-party analytics hosts. The docs show how to proxy the script and the endpoint through your own domain.

Other integrations.

See who is on your app and site right now. No analyst, no query building.

Start for free