Product
Keep the first click connected.
Capture website activity on a domain you control, then connect known visitors to the conversions and revenue in DATALYR. Build a first-party measurement foundation with an explicit consent and identity strategy.
Compare plans and usage
Start with the data your business collects.
A payment record says what was bought. A browser session explains how that buyer arrived. DATALYR brings these observations together when the identifiers are available. A custom tracking domain supports your collection architecture, but does not override browser restrictions, consent choices or ad-platform policies. The goal is a verifiable path from a visit to a known outcome.
In DATALYR
First-party tracking software
Capture the landing context
Record the campaign parameters and events that describe a visit. Keep the original acquisition context available when a visitor returns through another page or channel.
Connect a known customer
Identify users at an appropriate authenticated or checkout boundary. Stable IDs make a stronger join than hoping that separate visits will always share the same browser storage.
Use one measurement foundation
Bring the web event stream into customer journeys, attribution and reporting. Review collection problems before drawing conclusions from a sudden change in campaign performance.
The workflow
From setup to a useful answer.
Choose the collection path
Use the web installation and domain setup appropriate to your site. Document which pages, forms and checkout surfaces are covered, including any third-party destinations.
Name the meaningful events
Define a small set of actions such as signup, trial start and purchase. Keep names stable and avoid sending sensitive free-text fields as event properties.
Verify a known journey
Follow a tagged visit through identification and payment. Confirm the events arrived in order and inspect the customer record before expanding tracking across the site.
Verify the result
Know what good looks like.
- A tagged landing visit retains the expected campaign values.
- A known test customer connects to the correct payment record.
- Consent choices and excluded fields behave as intended.
Go deeper
Use the guide for context, then follow the implementation reference for your setup.
A few practical questions.
Does first-party tracking capture everyone?
No. Consent, browser behavior, missing identifiers and external checkout paths can still create gaps. Use observed coverage and individual test journeys to evaluate the implementation.
Is this a replacement for server events?
The two complement each other. Browser events describe interactions; a server or payment integration can confirm a completed transaction. Both need consistent identity and event definitions.
Explore related workflows.
- Server-side conversion tracking ↗
Connect verified business events to ad-platform conversion delivery in DATALYR. Configure rules, inspect destinations and validate results before scaling.
- UTM tracking and campaign links ↗
Use DATALYR tracking links and campaign parameters to preserve acquisition context across marketing activity.
- Customer journey analytics ↗
Explore customer sessions, events and conversions in DATALYR to understand the recorded path from acquisition to payment.