Installation Overview
Choose a Hardal setup for web, mobile, backend, or AI crawler traffic, then configure your first-party collection domain.
Choose Web, Mobile, or API for product and business events. AI Visibility uses a separate server-side request flow for agent and crawler traffic.
Web
Load the tracker through your first-party URL and automatically send page views.
Mobile
Send app events with an HTTP POST to the collection endpoint.
API & Server-side
Send backend events (orders, leads, server-side conversions) to the same endpoint.
AI Visibility
Send original request metadata from your CDN or application server.
Custom Domain
Set up a CNAME so collection runs on your own first-party subdomain.
The setup order
Follow these steps to start sending data:
Set up your first-party URL
Add the CNAME record first. If you add it later, you'll need to update and redeploy your installation.
Install your source
Add the web script, or send your first event from mobile or the API. For crawler traffic, set up AI Visibility collection.
Send and verify events
Confirm your base event arrives, then add the standard events you need.
The Dashboard has a separate Onboarding page that tracks setup progress without blocking access to the rest of the Dashboard.
Which method should I use?
- Most websites: start with the Web script. It sends page views automatically.
- Mobile apps: send events with an HTTP POST. No SDK needed.
- Backend or privacy-sensitive events: use the API for server-side conversions like orders and leads.
- AI agent and crawler traffic: send request metadata from your CDN or application server. Browser tracking is not enough for this traffic.
You can mix methods. A common setup is the Web script for browser events plus the API for server-confirmed purchases.
Verify Your Setup
Use the Onboarding page to review source installation and first-data verification.