Measure Travel Research Journeys Across Devices
Connect consented travel research across phone, tablet, and desktop when a traveler signs in or provides another approved first-party identifier.
Cross-device stitching requires an approved shared identifier. Hardal does not infer that two anonymous devices belong to the same person.
A traveler can research a destination on a phone, compare options on a tablet, and return on a laptop. Treat those visits as one journey only when the traveler provides a shared first-party identifier and your consent policy allows the connection.
What can connect the sessions
- an authenticated account ID
- a pseudonymous CRM ID presented after an eligible action
- a booking or quote reference tied to the approved customer record
- another first-party identifier reviewed by your privacy team
Device fingerprints and probabilistic identity claims are not a substitute for a documented identifier and purpose.
Implementation pattern
- Collect events separately on each device before identification.
- Record the consent state with every event.
- Send an identify event when the traveler signs in or presents the approved identifier.
- Join only the eligible events within your defined lookback window.
- Keep the original device and session fields for analysis.
Questions the data can answer
- Which device starts a research journey?
- Which device completes a quote or booking?
- How often does an authenticated journey cross surfaces?
- Which campaigns introduce journeys later completed elsewhere?
- Where does consent or identification disappear from the flow?
Measure the identified subset separately from anonymous traffic. Reporting a stitched journey as representative of every visitor will overstate what the data knows.
For the booking event itself, use the cross-device booking attribution guide. For web and app collection in one system, see web and mobile measurement.
