Installation
Add one script tag to your site. No tag manager or SDK required.
1. Create a site
2. Add the tracking script
</head> tag:<script defer src="https://datalaunch.vercel.app/track.cookieless.js"
data-site-id="YOUR_SITE_ID"></script><script defer src="https://datalaunch.vercel.app/track.js"
data-site-id="YOUR_SITE_ID"></script>3. Verify it works
/api/collect requests. Data should appear in the dashboard within seconds.What we track
Page analytics plus custom events you define.
- Real-time visitors, pageviews, referrers, and geography
- Browser, OS, and device breakdowns
- Custom events via JavaScript or HTML attributes
- Goals and funnels configured in Settings
Tracking modes
We collect
- Session IDs
- Country-level location
- Browser, OS, device
- Page paths & referrers
- Custom events
We do not collect
- Stored IP addresses
- Personal identity
- Cross-site profiles
- GPS location
Goals & funnels
Track conversions and see where visitors drop off in multi-step flows.
Create a goal
Send custom events
// JavaScript
window.datalaunch?.track('signup_completed')
// HTML — no extra JS
<button data-datalaunch-goal="signup_completed">Get started</button>View goals
Create a funnel
Step 1 — Page visit: /
Step 2 — Custom event: signup_completed
Step 3 — Custom event: first_project_created
Step 4 — Page visit: /billingView funnels
API reference
The tracker calls these endpoints automatically.
/api/collectPageviews and sessions
/api/heartbeatSession duration
/api/eventCustom events
Custom events
window.datalaunch.track('signup_completed')
document.getElementById('btn')?.addEventListener('click', () => {
window.datalaunch.track('signup_completed')
})SPAs are supported — route changes via pushState and popstate count as pageviews automatically.
FAQ
Cookieless vs standard — what is the difference?
Cookieless uses sessionStorage only and a daily server pseudonym. Standard keeps a localStorage visitor ID for returning visitors and journeys. Neither mode uses HTTP cookies.
Do I need a cookie consent banner?
Cookieless mode usually does not require a banner for DataLaunch alone. Standard mode stores a visitor ID in localStorage. Requirements depend on your jurisdiction.
How accurate is the analytics?
Pageviews, visitors, sessions, and custom events are tracked reliably. Some visitors may block JavaScript or use privacy tools.
Can I track multiple domains?
Yes. Create one site per domain. Each gets its own tracking ID. Switch between them from the dashboard.
Does it work with SPAs and Next.js?
Yes. The tracker handles client-side navigation via the History API — pushState, replaceState, and popstate.
How do goals and funnels work?
Goals count unique sessions that hit a page path or fire a custom event. Funnels chain those steps in order within a single session.
Can I export my data?
Export is available from the dashboard. CSV and JSON options are planned.
What browsers are supported?
Chrome, Edge, Firefox, Safari, and Opera. The tracker uses standard web APIs.
Troubleshooting
No data in dashboard
<head>, the site ID is correct, and /api/collect returns 200 in the Network tab.CORS errors
Sessions look wrong
Custom events missing
window.datalaunch exists, call track() after page load, and check for /api/event requests.