What is a dynamic product ad (DPA)?

You have seen dynamic product ads even if you have never heard the term. Look at a pair of shoes online, and for the next few days ads for those exact shoes follow you across apps, with the right price and image. That is a DPA at work. It is one of the most common ad formats in ecommerce, and understanding it clears up a lot of confusion about how modern catalog advertising actually functions.

This is a short, plain explanation of what a dynamic product ad is, how it works, and where it fits among the other terms you will hear.

The definition

A dynamic product ad, or DPA, is an ad that the platform builds automatically from your product feed and personalizes for each viewer. You do not create one ad per product. You connect a feed, set up the campaign, and the platform generates ads across your entire catalog, showing each person the products most relevant to them.

The word doing the work is "dynamic." The ad is not a fixed creative; it is a template that gets filled in differently for every viewer and every product, live, from your feed data.

DPA, catalog ads, dynamic remarketing: same idea

The terminology is messier than the concept. Meta coined dynamic product ads. Google talks about Shopping ads and dynamic remarketing. Other platforms have their own labels. The neutral umbrella term is catalog ads, and they all describe the same mechanism: a feed goes in, personalized ads come out.

So if you have read about catalog ads elsewhere, DPA is not a different thing to learn. It is Meta's name for it. We use the broader framing in what are catalog ads, which covers the same ground across all platforms.

How a DPA works

Three things happen behind every dynamic product ad.

It reads your feed

Everything starts with the product feed: your catalog as machine-readable data, with fields like id, title, price and image_link. The platform stores its own copy and builds ads from that. The feed is the foundation, covered in the product feed guide.

It matches product to viewer

Using signals from your pixel or conversions API, the platform decides which products to show each person. Someone who viewed a specific item sees that item; a broad prospect sees your bestsellers. This matching, done automatically across a whole catalog, is the core value of the format.

It assembles and serves the ad

The platform drops the chosen product into a template and serves it into a placement, pulling the image, price and title straight from your feed. Whatever the feed contains is what appears, which is why the feed quality determines the ad quality.

DPA versus static ads

The clearest way to understand a DPA is against its opposite. A static ad is a single creative you design by hand and upload. It shows the same message to everyone and does not change per viewer or product.

A DPA is generated and personalized. One is a poster; the other is a machine that prints a tailored poster for every person and product. They are not competitors so much as different tools, and knowing when to use each is its own topic, covered in catalog ads vs static ads.

The catch, and the opportunity

Because a DPA pulls straight from the feed, and the feed image is a plain product photo, the default ad looks generic. Every advertiser selling the same product from the same distributor photo gets the same bare creative. The automation is powerful; the look is forgettable.

That gap is the opportunity. The targeting is handled; the creative is where you can still differentiate, by adding your brand, offer and social proof on top of the feed. That is what FeedForce does for Meta dynamic product ads: it turns the plain feed-driven ad into an on-brand one across every SKU automatically, so you keep the automation and lose the sameness.