Pulsar · Field guide · No. 26 · What a catalog is, how Dynamic Product Ads personalize themselves, and the content-id match that makes it all work.
Let the Products Sell Themselves
A catalog turns your product feed into ads that assemble themselves — showing each person the exact items they viewed. Set up the feed, connect the events, and retargeting runs on autopilot.
What a catalog is
A catalog is a structured feed of your products — id, title, price, image, availability — that Meta reads to build ads automatically. One feed, kept in sync, becomes the raw material for thousands of ad variations.
You stop building product ads by hand. You build the feed once, and the ads assemble themselves.
Dynamic Product Ads personalize themselves
Dynamic Product Ads (DPA) auto-populate with the exact items a person viewed or added to cart. One template → a personalized ad per shopper, at scale no human could hand-build.
Someone browsed three products and left? DPA can show them those three, tomorrow, in their feed — assembled from the catalog, no manual work.
The feed is everything
DPA is only as good as the feed behind it. A stale feed shows sold-out items at the wrong price — and burns spend doing it. Keep price, availability and image auto-syncing.
Connect the events — the content_id match
The whole trick: your ViewContent / AddToCart / Purchase events must send content_ids that exactly match the catalog IDs. If they don’t match, Meta can’t tell which product a person saw — and DPA has nothing to show.
Prospecting vs retargeting
Two jobs from one catalog:
| Mode | Shows… | To… |
|---|---|---|
| Retargeting DPA | the exact items they viewed / carted | warm visitors (highest ROAS) |
| Advantage+ catalog | products Meta predicts they’ll want | cold prospects |