Dynamic product ads (DPA): what they are and how they work
What dynamic product ads are, how Meta and Google build them from your product feed, which feed fields matter, and how to make them look like your brand.
AI Shopping Feeds
A dynamic product ad (DPA) is an ad the platform builds for you from your product catalogue. You don’t design an ad per product. You give the ad platform a feed of products, and it picks which product to show each person and fills the ad with that product’s image, title and price.
That one idea covers a lot of names. Meta calls them Advantage+ catalog ads (they were “dynamic ads” before). Google calls the retail version dynamic remarketing, powered by your Merchant Center feed. TikTok, Pinterest and Snapchat each have their own catalogue ad formats. The mechanics are the same everywhere, so this guide uses DPA for all of them.
How dynamic product ads work
Every DPA setup has three parts.
- A product catalogue. A list of every product with an ID, title, description, link, image, price and availability. On Meta it lives in Commerce Manager. On Google it lives in Merchant Center. Either way it’s usually kept up to date by a product feed: a file or URL the platform fetches on a schedule.
- Events from your website or app. The Meta Pixel or Conversions API, or the Google tag, reports what people do: viewed a product, added to basket, purchased. Each event carries the product’s ID.
- An ad template. You set up the ad once, with placeholders for the product’s image, name and price. The platform fills it in at the moment it shows the ad.
When someone views a pair of trainers on your site and leaves, the event tells Meta which product ID they looked at. Meta finds that ID in your catalogue and can show them an ad for those trainers, or similar ones, with today’s price. If the price changes in your feed, the ad changes with it.
The link between parts 1 and 2 is the product ID. If the ID your pixel sends doesn’t match an ID in the catalogue, Meta can’t tell which product someone viewed. This is one of the most common reasons DPA retargeting underdelivers. We cover it in fixing pixel and catalogue content ID mismatches.
Where dynamic product ads run
| Platform | What it’s called | Where the products come from |
|---|---|---|
| Meta (Facebook, Instagram) | Advantage+ catalog ads | A catalogue in Commerce Manager |
| Dynamic remarketing (Display, Performance Max) | Your Merchant Center product feed | |
| TikTok, Pinterest, Snapchat | Each has its own catalogue ad format | A catalogue on that platform |
Meta’s version is the one most people mean by “DPA”. It can serve a single image, a carousel of several products, or a collection, and it runs on Facebook and Instagram feeds, Stories and Reels.
Retargeting and prospecting
DPAs started as a retargeting tool: show people the products they looked at. That’s still the most reliable use, because the intent is already there.
Meta’s catalogue ads can also go to broad audiences who have never visited your site. In that case Meta picks the products it expects each person to be interested in. This is how many brands use catalogue ads for prospecting, often alongside their other creative.
The practical difference is creative. Someone who saw your product yesterday recognises it in a plain product shot. Someone who has never heard of you sees a cut-out product on a white background with no brand, no reason to choose you and no price context. That’s where custom catalogue creative earns its place.
The feed fields that matter most
A DPA can only be as good as the data behind it. These fields do the most work.
- id: must match the content ID your pixel or tag sends.
- title: often shown in the ad. Lead with what the product is, not internal codes.
- image_link: the main image the ad uses. Size, crop and background decide how the ad looks.
- additional_image_link: extra images, used in some formats and placements.
- price and sale_price: must match the landing page, or products can be rejected.
- availability: keeps out-of-stock products out of your ads.
- brand: important if you sell more than one brand.
- item_group_id: groups variants such as colours and sizes of one product.
- custom_label_0 to 4: your own labels, such as “bestseller” or “high margin”, used to build product sets.
If your titles are messy or attributes are missing, fix them before you spend on catalogue ads. Our Feed Audit checks for the issues that get products rejected, and AI Product Optimisation rewrites titles and fills missing attributes in bulk.
Making DPAs look like your brand
Out of the box, a catalogue ad shows whatever is in image_link. For most stores that’s a product cut-out on white. It’s clear, but it looks the same as every other retailer selling the same product.
There are two ways to change that.
- Use the platform’s built-in options. Meta’s Ads Manager has options for catalogue ads such as overlays that show price or discount information on the image. They’re quick to set up but limited in design.
- Supply your own designed image for each product. You design a template once, with your colours, fonts, logo, a price tag and a sale badge, and render it for every product in the catalogue. The feed then points the platform at the designed image instead of the plain one.
The second approach is what a DPA creative editor does. In ours, you build the template from layers (text, shapes, images and the product photo). Text layers can use product data such as {{title}}, {{brand}}, {{price}}, {{sale_price}} and {{discount_pct}}. A layer can be set to show only when a condition is true, for example only when a product is on sale. You preview it against real products in your feed, then publish. Every product gets its own rendered image, in square 1:1, portrait 4:5 or story 9:16.
On Meta, the rendered images go into your catalogue through our Meta catalogue sync or your feed URL. Prices and sale badges update when your feed changes, so you don’t redesign anything for a sale.
Check each platform’s image rules before you send designed images. Google Merchant Center’s rules say the main product image must not include promotional text, watermarks or borders, so branded overlays don’t belong in a Google Shopping image_link. Our Google Merchant Center sync always sends the original product images.
How to get started
- Make sure your catalogue is complete and your pixel’s content IDs match the catalogue IDs.
- Clean up titles, images and prices. Broken images and price mismatches are the most common rejections.
- Launch a plain catalogue campaign first if you’ve never run one, so you have a baseline.
- Design a branded template, render it for your catalogue, and test it against the plain version.
- Keep the feed fresh. A DPA is only as current as the last time the catalogue updated.
If you want to try branded catalogue creative, the DPA Creative Editor starts from 36 ready-made layouts and renders them for every product in your feed.
Frequently asked questions
Are dynamic product ads the same as Meta Advantage+ catalog ads?
Yes. Meta now calls its dynamic ads Advantage+ catalog ads. Most advertisers and tools still say DPA or dynamic product ads for the same thing: ads built automatically from a product catalogue.
Do dynamic product ads only work for retargeting?
No. Retargeting people who viewed or added products to their basket is the classic use, but Meta can also show catalogue ads to broad audiences who have never visited your site, picking products it expects them to want.
What do I need to run dynamic product ads on Meta?
A product catalogue in Commerce Manager, kept up to date by a feed or an integration, and the Meta Pixel or Conversions API sending events whose content IDs match the product IDs in that catalogue.
Can I change how the product image looks in a DPA?
Yes. Meta offers some built-in options in Ads Manager, and you can also supply your own designed image per product through the feed, for example with a brand background, price tag or sale badge.