Cross-Device Booking Attribution for Travel
Join an eligible campaign journey to a confirmed booking when the traveler moves between a website and mobile app.
This guide does not claim an expected conversion lift. Results depend on your identified journey coverage and attribution rules.
Cross-device booking attribution connects a consented web or app journey to a confirmed booking. It needs a shared first-party identifier. Server-side collection alone cannot prove that two anonymous devices belong to one traveler.
Define the conversion at the source
Use the reservation or order system as the source of truth. Send the conversion after the booking is confirmed, not when the traveler opens a checkout screen. Include a stable event ID so retries do not create duplicate purchases.
Carry the journey context
Preserve the eligible context that preceded the booking:
- campaign and affiliate parameters
- landing page and timestamp
- web or app session ID
- approved account or customer identifier
- consent state
- booking value, currency, and product category where permitted
Keep sensitive passenger and payment fields out of advertising events.
Validate attribution coverage
Compare:
- confirmed bookings in the source system
- confirmed events received by Hardal
- bookings with an approved shared identifier
- identified bookings with eligible campaign context
- duplicate and rejected destination events
This separates collection quality from identity coverage. A low identified share may be a product or consent-design constraint, not a delivery failure.
Start with one booking flow and one destination. Reconcile it against the reservation system before adding more attribution models or marketing endpoints.
See travel research journeys for pre-booking analysis and PNR tracking for airline reservation systems.
