# Journeys and continuity

People rarely install on their first visit. CLItrail keeps every visit the install's computer can prove, in order, so you see the whole path and not only the last click.

## The journey

When the hook reports several receipts, every one that resolves to an active visit becomes a touch, stored oldest first. The [attribution policy](https://clitrail.com/docs/attribution-policies) chooses which touch gets the credit; the others stay in the journey either way. Install events in the dashboard show the timeline, and webhooks receive it as `journey`.

- Each page keeps one marker per browser profile. A revisit to the same page replaces it and revokes the earlier receipt, but the new visit was issued against that receipt, so the earlier visits (and the clicks they carried) stay in the journey while they are unexpired.
- A handoff or reconstructed install has a single touch: the visit behind the token, or the reconstructed visit.
- The hook reports up to 64 receipts for one install.

## First and last touch

The Overview's model switch changes reporting only. **Last touch** credits the most recent visit in the journey; **First touch** credits the oldest, whatever the policy chose. Destinations always follow the policy: each ad platform and GA4 stream receives its own most recent identifier under latest visit, the way each platform's own tag keeps its latest click in a cookie, or its earliest under first visit. The Overview also reports how many attributed installs had more than one touch, and the average number of touches.

## Several domains

A website can list more domains in **Settings**, such as a docs site on another host: 5 on Free, 10 on Standard and 25 on Enterprise, counting the primary one. The SDK works on all of them, and each domain leaves its own receipt, so the hook finds visits across domains and joins them into one journey.

## Session source

Each touch keeps where its browsing session began: the six UTM values and the external referrer. A new source starts when a page URL carries a campaign tag, a `gad_` parameter or a click ID, or when the visitor arrives from another origin. Moving between pages of the same origin keeps the source. Your other domains count as another origin, so crossing to one starts a new session source.

## How long it lasts

A receipt can match an install for 30 days after the visit, unless the browser clears site data, the visitor browses privately, or storage is evicted. Stored visits and installs follow your website's [retention period](https://clitrail.com/docs/retention).