Meta Ads

Dynamic Product Ads (DPA)

Also called DPA, catalogue ads

Ads built automatically from a product catalogue, showing each person the items they viewed or ones likely to suit them.

Quick facts: Dynamic Product Ads (DPA)

Category
Meta Ads
Also called
DPA, catalogue ads
Level
Intermediate
Affects
Ecommerce sales, retargeting efficiency, catalogue coverage
Where to see it
Meta Commerce Manager (catalogue), Meta Ads Manager, Meta Events Manager
In this article4
  1. How dynamic product ads work
  2. Why dynamic product ads matter
  3. Common mistakes with dynamic product ads
  4. How to act on it

How dynamic product ads work

Three things have to be in place: a catalogue, a tracking connection and a template. The catalogue is a structured list of everything you sell, each row carrying a unique product id, title, description, price, availability, image and link. The tracking connection — the Meta Pixel, the Conversions API or both — reports which product ids a person viewed, added to a basket or bought. The template is the frame the ad is built inside: your headline pattern, your styling, your call to action.

Nothing is designed product by product. When someone becomes eligible to see an ad, Meta assembles the creative at that moment and drops in whichever items it expects that person to respond to. Run against people who have already browsed, it shows the things they looked at and items sold alongside them. Run against a broad audience, it starts from what sells well across the catalogue and narrows as delivery learns.

Why dynamic product ads matter

A shop with a deep range cannot hand-build an ad for every line, and the lines that quietly sell best are rarely the ones a marketing team would have chosen to feature. A catalogue campaign covers the whole range with one set-up, and the decision about what to show is made per person rather than per campaign.

It also keeps the ad honest. Because price, stock and image are read from the feed, an item that sells out or goes on offer stops being advertised on the old terms. For a Nepali retailer running cash on delivery, where a wrong price or a missing size becomes a refused parcel rather than a refund, that live link between shop and ad is worth more than the targeting.

Common mistakes with dynamic product ads

The most common failure is not in the ad account at all. If the product ids your website sends with each event do not match the ids in the catalogue, Meta cannot connect a browsing session to a product, and the campaign quietly falls back to generic delivery. Variants cause the same break: a site that reports the parent product while the feed lists each size separately will never line the two up.

After that it is feed neglect — stale availability, images cropped so the product is unrecognisable in a square frame, titles written for a search engine rather than for a person scrolling. Forgetting to exclude recent buyers is the mistake customers actually notice, because being followed around by something you have already paid for reads as carelessness.

How to act on it

Start with the feed and the event data, not the creative. Confirm that a single product id appears identically in your product feed and in the events your site sends, then test one product from view to purchase before scaling. Keep the catalogue updating on a connection rather than by manual upload, so availability is never a day behind the shop.

Then separate the jobs. Run retargeting and broad prospecting as different campaigns with different expectations, exclude recent purchasers for a sensible window, and give the template enough brand framing that the ad still looks like you. Where the plumbing is beyond what your platform exposes, wiring the catalogue and dynamic product ads together properly is a technical job worth doing once.

Do and do not

Do

  • Match feed product ids to the ids your site sends
  • Update the catalogue automatically so stock and price stay current
  • Exclude recent buyers from retargeting for a sensible window

Do not

  • Launch before testing one product from view to purchase
  • Leave availability set to a default value on every row
  • Run retargeting and prospecting from the same budget

Questions people ask about this

Do I need an online shop to run dynamic product ads?

You need a catalogue and a way to report product-level events, which in practice means an ecommerce platform. Shopify and WooCommerce both produce a feed and send the right events once connected. A brochure site with a price list will not work, because there is no product id for Meta to match a visitor against.

Why do my ads show products that are out of stock?

Because the catalogue is still telling Meta they are available. That happens when the feed is uploaded by hand and has not been refreshed since the last sale, or when the availability field carries the same default value on every row. Move to a scheduled or live feed connection and check that availability reflects real stock.

What is the difference between retargeting and broad audience catalogue ads?

Retargeting shows items to people whose browsing you already have a record of, so the products are chosen from what they viewed. Broad audience campaigns run against people with no history on your site, so Meta picks products from what performs across the catalogue. They need separate budgets and separate expectations about cost per sale.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.