Criteo Product Catalog & Feed for Travel Dynamic Ads

The primary role of a Criteo feed is to move advertiser inventory into the Product Catalog in a repeatable, observable way. In travel, a product does not have to behave like a classic ecommerce SKU; hotels, routes or other bookable entities can be represented through a catalog model.

Feed versus Catalog

The feed is your source dataset. The Catalog is Criteo's processed inventory view after import, field mapping and rules. This distinction matters operationally: a source file can be correct while the resulting Catalog is wrong because of mapping or transformation rules.

Travel inventory semantics

Stable entity ID, name, destination, image, landing URL and price presentation are core fields. Travel pricing is often date- and occupancy-sensitive, so the semantics of a displayed price must be explicit.

A “from” price is not equivalent to an exact currently bookable rate.

Import and freshness

Scheduled imports keep the Catalog current. Monitor last successful import, accepted/rejected items, stale-item age, missing imagery/landing URLs, malformed prices and field-mapping errors.

Dynamic Ads connection

Catalog data becomes an input to dynamic creative. A stale price or broken landing URL is therefore not just a backend quality problem—it can be shown directly to a traveler.

Feed QA and creative QA should be part of one operational release process.

Reusing Google or Facebook feeds

Criteo documentation states that an existing Google or Facebook product feed can be reused for Product Catalog setup. This reinforces the value of maintaining one canonical internal catalog and generating channel-specific mappings.

Production model

For an OTA or travel advertiser, a sustainable pipeline is:

canonical inventory → channel mapping → feed export → import monitoring → catalog QA → campaign performance.