The root element of the landing pages (formerly points of sale) file is
<PointsOfSale>
. This element has no attributes and takes one
child element, <PointOfSale>
. A landing pages file can have
any number of <PointOfSale>
child elements.
Each landing page that you define in the landing pages file is
contained in a <PointOfSale>
element. This element takes a
single attribute, id
. The id
attribute defines a
unique identifier for a landing page. You can use the value of id
to filter eligible landing pages for a matching hotel. You do this by using the
<AllowablePointsOfSale>
element in <Transaction>
.
The landing pages file uses the following syntax:
<?xml version="1.0" encoding="UTF-8"?> <PointsOfSale> <PointOfSale id="landing page id"> <DisplayNames display_text="landing page display name" display_language="language code"/> <Match status="[yes|never]" country="country code" language="language code" brand="booking engine or brand" currency="currency code" sitetype="[localuniversal|mapresults]" device="[desktop|mobile|tablet]"/> <!-- The dynamic landing page URL --> <URL>landing page url</URL> </PointOfSale> </PointsOfSale>
The following table describes the child elements of the
<PointOfSale>
element:
Element | Required | Description |
---|---|---|
<DisplayNames> |
Optional | Contains display text for Online Travel Agencies (OTAs). This element takes the following attributes:
The following example shows a display name for a French OTA: <DisplayNames display_text="TravelAgency.com.fr" display_language="fr" /> Omit the Note: For OTA's, if you have configured a default display name
with Google Support, then this field is optional. Otherwise OTA's must
provide |
<Match> |
Required | Defines filters for whether your ads and free booking links are displayed based on various characteristics of the end-user or hotel. For example, you can specify that an ad or free booking link is displayed only to users in a certain country. This element takes the following attributes:
For example: <PointOfSale id="test1"> <Match status="yes" country="US"/> <Match status="yes" currency="USD"/> <Match status="yes" device="mobile"/> <Match status="yes" language="en"/> <URL>www.google.com</URL> </PointOfSale> You can combine attributes of the <PointOfSale id="test1"> <Match status="yes" country="US" language="en" currency="USD" device="mobile"/> <URL>www.google.com</URL> </PointOfSale> For more information, refer to Landing Page Matching Rules. |
<URL> |
Required | Defines a link to your site where the end-user can book a room. You
can insert dynamic information about the user and their itinerary as query
string parameters. For example, you can include the hotel ID by using the
PARTNER-HOTEL-ID variable in the URL:
http://partner.com/landing?hid=(PARTNER-HOTEL-ID) When this link is constructed and displayed to the end-user, Google
replaces the When using tracking, specify the complete URL including the components needed for tracking. For example: https://example.tracker.com?campaign_id=(CAMPAIGN-ID)&t_url= http://partner.com/landing%3Fhid%3D(PARTNER-HOTEL-ID) ValueTrack parameters can't be used in You can define only one |
<LPURL> |
Optional | Used to support dynamic tracking in the landing page URL. Specifies
the non-tracking segment of the URL defined in the <URL>
element. Tracking segments of the landing page URL must be specified
using Google Ads tracking templates (available in your Google Ads
account) and/or the final URL suffix. If
tracking URLs are not present in Google Ads, the The http://partner.com/landing?hid=(PARTNER-HOTEL-ID) ValueTrack parameters can’t be used in |
The landing pages file schema defines the structure and constraints of a landing pages file. For more information, read Schemas.