What the click discards

Feed-driven creative over travel inventory is not new, and any proposal in this space has to say plainly what already exists before claiming a contribution.

Meta Travel Ads is a shipping product. It supports hotel, flight and destination catalogs with price and date fields, and serves inventory-specific creative off cross-device intent signals. Cruise catalogs are absent from it, which is its own story. Dynamic creative optimization platforms have been generating variations from a product feed across social, display and CTV for years, with travel as a supported vertical.

So the generation problem is solved. What none of them do is persist the semantics of the engaged unit past the click.

Meta optimizes delivery and renders the catalog row into the creative. The click still lands on a surface that knows only that a click occurred. DCO personalizes the ad. The destination stays generic.

Why the CDP does not close it

The reflex answer is the customer data platform, and it does not work, for a structural reason rather than a vendor one.

A CDP profile is trait- and audience-shaped. It is a repository of attributes and segment memberships: this person is in the high-value segment, has these traits, belongs to these audiences. There is no native representation of which specific creative initiated this intent and what that creative depicted. That datum is the one the entire mechanism turns on, and the schema has nowhere to put it.

There is a latency problem underneath the modelling problem. Segment’s own engineering documentation states that its Profiles API is subject to response times unsuitable for the request path, and the render-time pattern it recommended relied on caching profiles at the CDN edge, via an SDK that has since moved to a deprecated-projects organization. mParticle positions its Profile API for request-time reads and publishes no latency guarantees.

Three reasons this persists, only one of them technical

Paid social, lifecycle messaging and the web property are separately owned, separately budgeted, and often separately outsourced. A mechanism that spans all three has no natural owner, so it does not get built.

The semantics of creative were never stored anywhere durable. Platforms return an identifier. What the unit actually depicted lived in a brief and a filename, so there is nothing to resolve the identifier against without a tagged asset library.

And the tooling assumes one of two shapes: a SKU with a short window, or a trait-shaped profile. Inbound-creative semantics carried to an owned surface is neither, so nothing on the shelf does it.