This isn’t legal advice. Confirm pricing accuracy and availability claims with your legal or compliance team before publishing a hotel catalog.
File format
- CSV, TSV, or XML, one row per hotel property, with a header row naming each column.
- Fields containing a comma or whitespace need to be wrapped in double quotes.
- Nested or multi-value fields (address, neighborhood, images) can be provided either as a JSON-encoded value in a single column, or split into separate “flattened” columns using JSON-path-style names (for example,
address.regionandaddress.country). Pick one convention and use it consistently; a hand-built CSV almost always uses the flattened columns. - Upload once or on a recurring schedule (hourly, daily, or weekly).
Column template
This isn’t an exhaustive field list. Meta’s hotel spec includes additional optional attributes (amenities, neighborhood, brand affiliation, loyalty program details, and more); confirm the complete current list against Meta’s own documentation before a first upload.
Format rules
hotel_idis the catalog’s unique key for this vertical; other verticals use a different ID field (idfor products,vehicle_idfor vehicles, and so on), so don’t reuse an ID scheme across catalog types.base_pricefollows the same pattern as a product price: a number plus a three-letter ISO 4217 currency code.address.countryshould be the two-letter ISO 3166-1 alpha-2 country code, consistent with how country is formatted elsewhere in this knowledge base’s audience CSV templates.
Data and compliance rules
Official documentation
- Hotel Ads, Catalog & Feed, Meta for Developers
- About Commerce Manager
- Advertising Standards, Transparency Center