---
title: "Meta Catalog Feed for Travel Inventory & Dynamic Advertising"
description: "Study Meta catalog/feed architecture through travel inventory, product identity, landing URLs, event matching and dynamic advertising operations."
slug: "meta-travel-catalog"
translationKey: "platform-meta-travel-catalog"
locale: "en"
type: "profile"
category: "feed-platform"
tags: ["meta","facebook","feed","catalog","dynamic-ads","travel"]
vertical: ["hotel","flight"]
platform: "Meta"
domain: "facebook.com"
publishedAt: "2026-09-19"
updatedAt: "2026-09-20"
reviewedAt: "2026-09-26"
directory: {"status":"active","platformType":"feed","audiences":["b2b"],"businessModels":["advertising"],"integrationMethods":["feed","api"],"docsUrl":"https://developers.facebook.com/docs/marketing-api/catalog/","sources":[{"title":"Meta Business SDK — ProductCatalog (hotel and flight verticals)","url":"https://github.com/facebook/facebook-python-business-sdk/blob/main/facebook_business/adobjects/productcatalog.py"},{"title":"Meta Business SDK — ProductFeed and scheduled imports","url":"https://github.com/facebook/facebook-python-business-sdk/blob/main/facebook_business/adobjects/productfeed.py"}],"reviewedAt":"2026-09-26"}
sources:
  - title: "Meta Marketing API — Catalog documentation"
    url: "https://developers.facebook.com/docs/marketing-api/catalog/"
  - title: "Meta Business SDK — ProductCatalog"
    url: "https://github.com/facebook/facebook-python-business-sdk/blob/main/facebook_business/adobjects/productcatalog.py"
  - title: "Meta Business SDK — ProductFeed"
    url: "https://github.com/facebook/facebook-python-business-sdk/blob/main/facebook_business/adobjects/productfeed.py"
  - title: "Meta Business Help Center"
    url: "https://www.facebook.com/business/help/"
---
A Meta catalog/feed integration is best understood as the data layer behind an **inventory identity + event matching + dynamic creative** chain rather than simply as a way to upload advertisements.

Catalog and dynamic-advertising capabilities can vary by account, product and campaign type. Production implementations should therefore follow the current Business Help Center and account-level schema requirements.

## Canonical item identity

The feed item ID and the item/content ID sent through site or app events must represent the same canonical entity. Using HOTEL-123 in the catalog and a different supplier-specific identifier in events reduces match quality.

## Why travel is different

Travel inventory is not a classic fixed ecommerce product: availability changes, price depends on search context, landing URLs can carry dates and occupancy, and the same property can expose different offers by market and currency.

The boundary between a catalog item and a live booking offer is therefore an architectural decision.

## Feed freshness

Static property content and imagery change slowly; price signals can become stale quickly. Import frequency must align with the price semantics actually shown in advertising.

## Event matching

Dynamic-advertising quality is not only a feed-quality problem. Search, detail and booking events need to resolve to the same catalog identity. Track catalog coverage, event-to-catalog match rate, rejected items, stale items, broken landing URLs and conversion-event quality separately.

## OTA architecture

Meta feeds should not become an isolated artifact owned only by performance marketing. An OTA's canonical property/flight catalog, booking engine and analytics event model should share one identity backbone, allowing Google, Criteo and Meta adapters to be generated from the same source of truth.