A landing pages (formerly called points of sale) file is an XML file that partners create to define various URL destinations for when a user clicks on a hotel ad price on Google and gets redirected to a partner website. You can upload a landing page file using Hotel Center (for details, see Manage and update your landing pages).
The root element of the landing pages file is
<PointsOfSale>. Each landing page in the file is defined by a
<PointOfSale> child element.
You can have any number of
<PointOfSale> child elements in a
landing pages file. However, all landing pages refer to the same partner: you
cannot use a single landing pages file to define landing pages for more than
The following example shows a landing pages file that defines two landing pages:
<?xml version="1.0" encoding="UTF-8"?> <PointsOfSale> <PointOfSale id="TravelAgency"> <DisplayNames display_text="TravelAgency.com" display_language="en"/> <DisplayNames display_text="TravelAgency.com.fr" display_language="fr"/> <Match status="yes" language="en"/> <Match status="yes" language="fr"/> <Match status="yes" country="US"/> <Match status="yes" country="FR"/> <Match status="yes" currency="USD"/> <Match status="yes" currency="EUR"/> <Match status="yes" clicktype="room"/> <URL>http://partner.com/landing?hid=(PARTNER-HOTEL-ID)&checkin=(CHECKINYEAR)-(CHECKINMONTH)-(CHECKINDAY)&checkout=(CHECKOUTYEAR)- (CHECKOUTMONTH)-(CHECKOUTDAY)&language=(USER-LANGUAGE)</URL> </PointOfSale> <PointOfSale id="Others"> <DisplayNames display_text="TravelAgency en espanol" display_language="es"/> <Match status="yes" language="es"/> <Match status="yes" country="US"/> <Match status="yes" currency="USD"/> <Match status="yes" clicktype="room"/> <URL>http://partner-espanol.com/landing?hotelID=(PARTNER-HOTEL-ID)</URL> </PointOfSale> </PointsOfSale>
In this example, English or French speaking end-users in the US or France
would match the first landing page. This landing page has two display names:
TravelAgency.com.fr. These two
sites support English and French for languages, and US dollars and Euros for
currencies. The generated URL that is passed to the landing page includes
details about the transaction, such as the check-in and check-out dates, hotel
ID, and user language.
A Spanish-speaking end-user in the US would match the second landing page. However, this landing page supports only one display name, one language, and one currency. The generated URL also only sends the hotel ID to the landing page. This most likely results in a frustrating experience for the end-user.
For more developer-focused information, proceed to Landing Pages File Syntax.