Meta Catalog Feed for Travel Inventory & Dynamic Advertising

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.