How Hardal Works
Follow your data from collection to reporting and server-side delivery.
Hardal helps you collect first-party events, understand activity in reports, and forward events to other tools through server-side integrations. Use it for websites, mobile apps, backend activity, commerce, lead generation, and AI agent traffic.
Collect
An event records something that happened, such as a page view, a purchase, or a submitted application. Its parameters describe that activity: a page path, order value, product, or form name.
| Data | How it reaches Hardal |
|---|---|
| Website activity | The web tracker collects page views and supported interactions. You send business events explicitly. |
| Mobile activity | Your app sends HTTP requests with event names and parameters. |
| Backend activity | Your server sends confirmed orders, leads, or other business events to the collection API. |
| AI agents and crawlers | Your server or CDN forwards metadata from the original incoming page request to the separate agent-events endpoint. |
Events belong to a Source, inside a Tenant, inside an Organization. The selected tenant and source determine which data a report includes. See workspace structure.
Start with Choose Your Integration Method and Plan Your Events.
Report
Reports answer different questions about the collected data:
| Question | Report |
|---|---|
| How much traffic do we receive? | Overview |
| Which channels and campaigns receive conversion credit? | Acquisition |
| Which content and actions attract engagement? | Pages, Events, and Sessions |
| Where do visits drop out of a defined journey? | Funnels |
| Which products and traffic groups contribute to sales? | Commerce |
| Which AI agents reach our pages? | AI Visibility |
Reports depend on what you send. Installing the tracker does not automatically collect purchases, form submissions, or app events. Commerce also requires the tenant's Commerce report type and the relevant event fields.
Use the Analytics API to read reports in your own scripts and integrations.
Forward
Destinations deliver selected event data from Hardal to an external platform, such as an advertising or analytics tool. Collection, reporting, and destination delivery are separate steps: seeing an event in a report does not establish that it was sent to another platform.
Destination availability and setup depend on your deployment. Confirm the supported destination and its activation, event mapping, fields, and consent requirements before relying on delivery. A reporting API key reads reports; it does not configure destinations or send events.
Consent and identity
Hardal can group anonymous activity into sessions when events share a session ID. Recognizing a visitor across visits additionally depends on consent, supplied identifiers, and collection context. A session is not a person, and a collected identity does not by itself authorize forwarding it to another tool.
Read Sessions and Visitors and Consent & Privacy before implementing identity.
Example: a demo-request journey
- A visitor opens your pricing page. The web tracker sends
page_view. - Your application confirms a demo request and sends
generate_lead. - You use Events to verify the event, Acquisition to analyze its attributed traffic, and a funnel to study progression from pricing to submission.
- If a supported destination is configured, separately verify that it receives the intended event and permitted fields.
Follow Measure Lead Generation to build this workflow.