takt

FAQ & troubleshooting

The most frequent questions, and how to diagnose a measurement problem.

I don’t see any data

In order, check:

  1. You’re testing locally. localhost and private IPs are excluded by default. Test on a public domain, or disable the guardrail (data-exclude-localhost="false").
  2. Do Not Track is on in your browser. Disable it, or test in another browser.
  3. You opted out. Check localStorage.getItem('takt_ignore') — if it’s '1', run localStorage.removeItem('takt_ignore') (or optIn() in npm).
  4. The data-domain doesn’t match the one in your dashboard. Events arrive but are attached to another site.
  5. The script doesn’t load. Network tab → look for takt.js (status 200) then the POSTs to /api/event.
Quick test from the console: window.takt('debug_test'). If you see a POST /api/event go out, the integration works.

Can an ad blocker prevent measurement?

Yes. Some lists block analytics scripts. Since Takt uses neither cookies nor personal data, you can self-host the script or serve it from your own domain via data-endpoint to reduce blocking.

My SPA only counts one pageview

init() (and the snippet) track navigation via the History API (pushState/popstate), which covers nearly all routers. Since the name pageview is reserved, the global window.takt('pageview') is ignored: there’s nothing to wire up on the snippet side.

In an npm integration, if you need to force a pageview (exotic router), use the dedicated function:

import { pageview } from '@vskstudio/takt-core'

pageview()

Takt sets no cookie and processes no personal data, which avoids the banner in most cases. Always check your legal situation: you remain responsible for your site’s compliance.

Does the script slow down my pages?

No. It weighs ≤ 1 kB gzip, loads with defer (never blocking) and runs no heavy work. No measurable impact on Largest Contentful Paint.

Can I pin a version?

Yes, in the CDN URL: @vskstudio/[email protected]/dist/takt.js. Recommended in production to avoid any surprise on update.

Still stuck?

The SDK code is public: you can inspect it and open an issue on GitHub.