Edit

Points of Sale reference

  • Article

Note

This beta release of Hotel Price Ads is available to select participants only. For information about participating in the beta release program, please contact your account manager or enroll here.

If you create hotel price ads in Bing, you must use a Points of Sale feed to provide Bing the point of sale URLs to include in ads. You must define and import your points of sale feed prior to sending Bing Transaction Messages.

For information about creating a points of sale feed, see Creating a Points of Sale Feed.

Note

The elements must be specified in the order defined by the PointsOfSale XSD (and as listed in this topic).

Note

Bing ignores any element or attribute not included below.

PointsOfSale

Defines the top-level element of a points of sale feed.

Element Description Children
PointsOfSale The top-level element in a points of sale feed. PointsOfSale Type

PointsOfSale Type

Defines a list of points of sale.

Element Description Children
PointOfSale Defines a point of sale (POS) where users book rooms. Include a PointOfSale element for each POS you offer. You must define at least one POS, and all points of sale must be for a single partner.

Attributes:
  • id—Required. An opaque, user-defined ID that uniquely identifies the POS in the feed.

    If you want to limit booking to a specific POS for specific itineraries in your transaction message, use this ID in the PointOfSale element of your transaction message.
 PointOfSale Type

PointOfSale Type

Defines a point of sale.

Element Description Children
DisplayNames Optional.

The online travel agency's name or domain to display in the ad. Specify a DisplayNames element for each language you support.

Attributes:
  • display_text—Required. The name of the online travel agency to display in the ad.
  • display_language—Required. The language used by the ad. Specify the language using the two-letter ISO 639 language code. For example, use en for English.

Notes:
  • Include DisplayNames for online travel agencies only. Do not use for partners such as central reservations systems (CSR), hotel owners, or chains. For these partners, Bing uses the hotel's name from the hotel feed.
  • The POS must specify a Match element with the same language that you specify for the display name.
  • Bing uses the display name and the URL in the URL element to create a hyperlink that Bing includes in the ad.
 None
LPURL Optional.
Data type is string.

A tracking URL that is used as the landing page for your hotel or property listing. It tracks traffic coming from Hotel Ads campaigns to your website and it can be configured by providing the <LPURL> XML element to the Point of Sale file.

Notes:
  • Tracking templates must reference a landing page URL using {lpurl} or a permutation of that tag.
  • Tracking templates at the account, campaign, and ad group level must include a parameter that inserts your landing page URL using either the {lpurl} or other advanced parameters.
  • Once your ad is clicked, these parameters will insert your final URL. If you don’t include a URL insertion parameter in your tracking template, your landing page URL will break.
 None
Match Required.

The criteria used to determine if the POS is used in the ad.

Attributes:
  • country—Optional. The publishing country of the Bing site used by the user. Specify the country using a two-letter ISO 3166 country code. For example, if the user uses Bing.com, set country to US for United States.
  • language—Optional. The language used by the user. Specify the language using a two-letter ISO 639 language code. For example, use en for English.
  • currency—Optional. The currency used by the user or hotel. Specify the currency using a three-character ISO 4217 currency code. For example, USD for US Dollar.
  • device—Optional. The type of device used by the user. The following are the possible case-insensitive values.
    • Desktop
    • Mobile
    • Tablet
  • sitetype—Optional. The type of site where the ad request originated. The following are the possible case-insensitive values.
    • LocalUniversal—The ad request originated from a web search results page.
    • MapResults—The ad request originated from a map site.
    • PropertyPromotionAd—The ad request originated from display ads throughout all available Property promotion placements.
  • status—Optional. The condition used to match the criterion. The following are the possible case-insensitive values.
    • Yes—Use the POS if the criteria matches.
    • Never—Don't use the POS if the criteria matches.
Notes:
  • You cannot set the status attribute to Never if the device attribute is set to Tablet.
For more information, see POS Matching Rules.		 None
URL Optional.
Data type is string.

The URL of the site where the user books the room.

Notes:
  • The POS may specify only one URL.
  • The URL may include one or more dynamic query parameter. For information about dynamic query parameters, see Using Dynamic Query Parameters.
  • If the URL includes special characters, you must replace the special characters with encoded entities. For example, if the URL includes query parameters, you must encode ampersands (&) as &amp;.
None