Create an XML Hotel Feed file
This beta release of Hotel Ads is available to select participants only. For information about participating in the beta release program, please contact your account manager.
The Hotel feed and documentation are subject to change.
To provide Bing your hotel listings, create an XML document that contains a listing of each hotel you want to advertise. A listing describes the hotel's name, address, telephone number, and geographical coordinates.
The document must use UTF-8 encoding and must conform to the Hotel XSD.
For information about creating a feed file using CSV or TSV file format, see Creating a CSV Hotel Feed file.
Bing does not support all XSD elements. Bing ignores any element or attribute in the document that it does not support. The Hotel Feed Reference includes only those elements and attributes that Bing supports.
The document must specify the elements in the order defined in the Hotel XSD (or as shown in the reference).
Getting the data right
Because Bing attempts to match properties in your hotel feed to businesses in Bing Maps, it is import that the data you provide about the hotel is accurate and complete.
If your property has missing or incorrect information, Bing may not be able to match it. If Bing cannot match the property, Bing will not advertise it. When your TAM imports your hotel feed file, they will let you know the hotels that Bing could not match.
The top-level element in your feed
The hotel feed contains a single, top-level listings element. The
listings element contains two required child elements:
<?xml version="1.0" encoding="UTF-8"?> <listings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <language>en</language> <listing> . . . </listing> ... </listings>
language element specifies the language that the data in the feed is written in. To specify the language, use the two-letter ISO 639 language code. For example, use en for English.
The hotel feed supports only the English language.
Defining a hotel listing
listing element defines a hotel. You must specify a
listing element for each hotel that you advertise. The listing must specify all elements. The exception is that you may specify either the geographical coordinates or a telephone number. Although you may specify either the coordinates or telephone number, you should specify both to ensure a better chance of matching properties in Bing Maps.
<listing> <id>abc123</id> <name>Great Ambers Getaway</name> <address> <component name="addr1">1234 Porter Road</component> <component name="city">Goldendale</component> <component name="province">WA</component> <component name="postal_code">98234</component> </address> <country>US</country> <latitude>47.694351</latitude> <longitude>-122.451782</longitude> <phone type="main">123-456-7890</phone> </listing>
The ID in the
id element is user-defined and must be unique within the feed.
The address in the
address element is the hotel's street address. The address must be a street address and not a post office box. You can specify the hotel's address using the
component element seen in the above example or by using a free-form string seen in the below example. The preference is to use
<address>1234 Porter Road, Goldendale, WA, 98234</address>
longitude element specify the hotel's geographical coordinates. Use a geocoding API such as Location API to generate the coordinates from a street address.
The listing must specify at least the hotel's main telephone number. The main number should be the front desk's phone number and not a central reservations phone number. The more contact phone numbers that you provide the better. The following example shows the other phone options.
<phone type="main">123-456-7890</phone> <phone type="tollfree">800-456-7890</phone> <phone type="fax">123-456-7890</phone> <phone type="tdd">123-456-7890</phone> <phone type="mobile">123-456-7890</phone>
For more information about specifying telephone numbers, see the phone element.
What happens if the hotel's content changes?
If you change any of the hotel’s property values between feed runs (for example, its name, address, phone, etc.), Bing Ads may treat it as a new hotel property and create a new listing for it. If Bing creates a new listing, prior performance history for the old hotel remains available for up to 36 months. Note that the old hotel's bids and multipliers will not transfer to the new hotel entity.
If you remove a hotel and add it back in a later feed with the same property values as before, Bing treats it as a new listing. Also, the performance report will show it as two separate listings.
Use the Hotel XSD to validate your hotel feed file before sending it to Bing.
The hotel feed document must use UTF-8 encoding.
The feed must include listings for all your hotels— the feed process does not support partial updates.
Bing ignores any element or attribute that it does not support.
Elements must be in the order specified in the Hotel XSD.
If your data includes special characters such as apostrophies or quotes, escape them or use CDATA sections. If you escape them, you may use entity codes or character codes. For example, you can escape Paul's as Paul's or Paul's.
Do not include elements that do not contain data. For example, if you do not provide the geographical coordinates for a hotel, do not include empty <latitude/> and <longitude/> elements.
Do not use HTML in your XML elements.
After creating your feed file, use the Hotel XSD to validate it.
Ask your account manager to import the feed file.
Be sure to also import your points of sale data. For information about creating your points of sale feed file, see Points of Sale Feed.
After Bing successfully imports your data and is able to match your hotels with properties in Bing Maps, you may begin sending your hotel pricing and availability data. For information, see Transaction Messages.