Identity assertions require permitted identifiers from your integration.
Predictive booking probabilities and spend values are not currently available.
What you get
First-party events
Collect events through a configured integration and apply your consent rules.
Identity assertions
Link records only where your own configured integration supplies a permitted identifier.
Booking outcomes
A booking is treated as verified only when submitted by the authenticated server-side booking integration.
Retention and controls
Configure workspace access and data handling to match your organisation’s obligations.
Questions teams ask
No. TravelSpy does not provide predictive visitor profiles. Event collection depends on the configured integration and your consent settings.
Elsewhere in the platform
How TravelSpy works
TravelSpy collects configured first-party events, streams live updates and can accept authenticated booking outcomes from your server integration.
Travel journey signals
Organise consent-aware first-party interaction events and view the event history your configured integrations provide.
Live event streaming
Share configured travel-event updates with connected clients through TravelSpy’s persistent stream. This is not an automated trip-packaging or offer-orchestration service.
Travel data integrations
Connect your application to TravelSpy’s configured event and booking-outcome interfaces. Third-party providers require a separate integration and agreement.
Discuss your travel data integration
Tell us about your website, consent setup and booking systems so we can confirm which TravelSpy event and outcome interfaces fit your requirements.