Landing Page
The provider or booking page opened after a metasearch click. HTTP 200 alone is insufficient; product and price context must also be preserved.
Why it matters
Transaction concepts describe how a metasearch click becomes a downstream booking experience. Without context-preserving links, durable click identity, booking lifecycle events and reconciliation, search performance becomes disconnected from actual commercial outcomes.
What does it look like in practice?
A metasearch click ID travels through the deeplink, returns with booking events and is reconciled through cancellation/stay states. Breaking this lineage creates commercial attribution gaps.
Implementation questions
- Is search context preserved on the landing page?
- Is there a durable ID from click to booking?
- Are booking lifecycle events idempotent?
- Is provider state reconciled with internal state?
Common mistakes
- Treating a generic landing page as successful handoff
- Treating unknown booking state as failed
- Counting replayed conversions twice
Where does it appear in the travel stack?
Landing Page commonly appears across transaction layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Google Hotels Integration: Developer Guide
Implement Google Hotels from a developer perspective with Hotel Lists, property mapping, Pull/Changed Pricing/ARI, Transaction XML, landing pages, OAuth2, request/response models, error handling and monitoring.
Explore →Google Hotel Feeds: Data Contracts and Recovery
Separate Google Hotel List, pricing, ARI, POI and landing contracts; diagnose stale updates and design publication, recovery and monitoring workflows.
Explore →What Is a Deep Link in Travel Metasearch?
Learn how deep links preserve travel search context, attribution, security and mobile behavior when sending users to booking providers.
Explore →What Is a Travel Feed? XML, JSON & Metasearch Data Flows
Learn how hotel-list, rate, availability, room-metadata and landing-page feeds work, how they differ from APIs and how to design them for production.
Explore →KAYAK Travel Trends 2026: Travel Demand Through Search Data
A metasearch-focused summary of KAYAK's 2026 flight-search demand, fare trends and destination signals.
Explore →KAYAK What the Future 2026: Travel Behavior Trends
A summary of KAYAK's 2026 future report covering AI, short trips, payment behavior and emerging destinations.
Explore →