TextfinityVisit Website →
← Back to blog

Dynamic Product Ads: How They Work and How to Set Them Up

November 8, 2026
Dynamic Product Ads: How They Work and How to Set Them Up

Dynamic product ads (DPAs) are catalogue-driven ads that show each person the products they viewed, added to a basket or are likely to want, without you building an ad per product. You upload a product feed, connect tracking, build one ad template, and Meta fills it with the right item for each viewer. Meta now calls the format Advantage+ catalogue ads, but the idea is unchanged, and you will still hear it called DPA.

This guide covers how DPAs work, what a store needs before launch, the consent rules that apply to a Swedish or wider European shop, a sensible campaign structure, and the feed and tracking errors that quietly waste budget.

Textfinity
textfinity.io
Keep Your Meta Product Feed Ready
Textfinity maps and publishes product feeds for Meta and other channels, with scheduled rebuilds to keep catalogue data current.
Get your feed set up

TL;DR

  • A DPA needs three things that must agree with each other: a product catalogue, tracking events (Meta Pixel or Conversions API) and a catalogue sales campaign.
  • The product ID in your feed must match the ID your tracking sends. When it does not, ads show the wrong product or nothing.
  • In Sweden and the rest of the EU/EEA, the pixel should not fire before the visitor consents, and server-side sending does not remove that duty.
  • Start with retargeting (7 to 30 day audiences), then widen to prospecting once the catalogue is clean and purchase signal is steady.
  • Feed quality is the lever you control most. Fix IDs, images, prices and stock before you touch budgets.

Table of Contents

What dynamic product ads are

A DPA is a template that the system fills automatically. You build the frame once: a headline pattern, a description pattern, a card layout and perhaps an overlay. Meta then reads the catalogue and the event data to decide which product goes into that frame for each viewer, as described in AdPlay's 2026 guide.

In practice, someone looks at a pair of walking boots on your store and leaves. Later, in Instagram or Facebook, they see those boots with the current price and stock status, and a link straight back to the product page. A catalogue of 40 products or 40,000 needs the same single setup.

The ads can run in single image, carousel or collection formats across Facebook, Instagram, Messenger and the Audience Network. They can also reach new people, not only past visitors, because Advantage+ shopping is built on the same catalogue foundation.

The three parts that make a DPA work

Every working DPA setup has the same three components, as laid out by Digital Codex:

  1. A catalogue in Meta Commerce Manager holding your inventory, with price, image, description and availability for each item.
  2. Pixel events (ViewContent, AddToCart, Purchase) that tell Meta which products each person interacted with. Many stores add the Conversions API alongside the pixel.
  3. A catalogue sales campaign that links the catalogue to the audience and the ad template.

Meta's own requirements, as summarised from its help documentation, also stress that the catalogue must sit inside a business portfolio and the pixel must be connected to that catalogue. If any link is missing, the campaign can still be created, but it will not behave as you expect.

The product ID is the thread that ties it together

When a shopper views a product, the ViewContent event carries that product's content ID, and Meta looks that ID up in the catalogue. If your feed says SHOP-123 and the pixel reports 123, the signals do not match, and retargeting may show wrong products or nothing at all. The ad still serves, so nothing looks broken in the dashboard while money leaks.

Matching and mismatching product IDs in ad events

On Shopify and similar platforms, decide early whether you use product IDs or variant IDs. A variant-based approach gives the best precision for size and colour, while a product-based approach is simpler but less granular. Whichever you pick, the feed and the events must use the same one.

Feed fields a DPA catalogue needs

The minimum fields for a DPA catalogue are an ID, title, description, link, image link, price with currency, availability and brand, plus a Google product category, according to Digital Codex. Square 1:1 images are recommended for feed placements.

Two habits pay off straight away:

We publish a Facebook catalogue feed template with the Meta CSV columns and a worked Facebook catalogue feed example showing rows that Meta accepts. If your feed already exists for Google, our guide to mapping a Google Shopping feed to a Facebook catalogue shows which columns carry across.

How DPAs differ from Google Shopping ads

The two are often confused because both run from a product feed. The difference is how the product reaches the person.

Meta dynamic product adsGoogle Shopping and Performance Max
TriggerPast behaviour and interest signalsSearch queries and Google placements
Feed sourceMeta catalogue in Commerce ManagerMerchant Center product feed
Titles matterLess, the image and price carry the adA great deal, titles are matched to searches
Data requirementsLooser, a missing GTIN does not disqualifyStricter, missing GTINs can cause disapproval
TrackingMeta Pixel or Conversions APIGoogle tag, consent mode

The contrast on titles and field strictness comes from a comparison of the two platforms. It means one feed rarely suits both channels unchanged. Google wants search-friendly titles of 100 to 150 characters with the key information in the first 70, while Meta leans on visuals. Our Google Shopping product title template by category covers the Google side. A tool that builds one feed per channel from the same catalogue saves you from maintaining two spreadsheets by hand.

This is where European stores differ most from the advice written for the US. DPA relies on tracking, and tracking in Sweden needs consent first.

Swedish law on cookies sits in the Electronic Communications Act (LEK), supervised by the Post and Telecom Authority. Under it, visitors must be told that a site uses cookies, how and why, and must give consent before cookies are stored or read, as IMY, the Swedish data protection authority, explains on its own site.

For the pixel, that has practical consequences:

  • The pixel stays silent until opt-in. It sets the _fbp cookie and calls Meta's servers as soon as it loads, and under Article 5(3) of the ePrivacy Directive that needs prior consent. If a visitor declines marketing cookies, there should be no _fbp cookie and no requests to facebook.com/tr.
  • Conversions API does not remove the duty. It sends events from your server without browser cookies, but if events are matched to people through email or phone, your server must check the visitor's consent state first.
  • Make declining as easy as accepting. Consent should be active, informed, granular and as easy to refuse as to give. Swedish guidance summaries note that IMY has acted on this.

Retargeting audiences will be smaller than in markets without such rules, because only consenting visitors enter them. That is a reason to feed Meta clean, accurate catalogue data: you have fewer signals, so each one must count. For your specific consent set-up, a data protection adviser or your consent platform provider should confirm the details for your store.

Setting up a DPA campaign step by step

  1. Build the catalogue. Create it in Commerce Manager, connect your store or upload a scheduled feed URL, and check the diagnostics for errors.
  2. Install tracking with consent. Add ViewContent, AddToCart and Purchase events, gated behind your consent banner. Consider adding the Conversions API.
  3. Verify ID matching. Open a product page, trigger the event, and confirm the content ID equals the catalogue ID.
  4. Create product sets. Group by category, margin or stock level so you can give different budgets to different parts of the range.
  5. Build the template. Choose carousel or collection, set headline and description patterns, and add price overlays or a branded frame if useful. Meta supports dynamic sale price overlays and custom frames.
  6. Launch retargeting first. Add a prospecting campaign later.

Retargeting audiences that work

Digital Codex lists the usual options:

  • Viewed or added to cart but did not buy: 1 to 180 days, with 7 to 30 recommended.
  • Added to cart but did not buy: 1 to 30 days, the highest intent.
  • Viewed specific products: 1 to 30 days.
  • Upsell to buyers: 1 to 180 days after purchase.
  • Cross-sell based on purchase history.

The audience list comes from Digital Codex. Abandoned baskets are the obvious starting point: the Baymard Institute's tracking of 50 studies puts average cart abandonment at 70.22%, so recovering even a small slice of that intent matters. If your product pages sometimes break or lead nowhere, shoppers who click a DPA hit a dead end, so it is worth learning how to check product links that do not load properly.

Prospecting and Advantage+ shopping

Prospecting DPAs use broad or Advantage+ audiences and let the algorithm pick products. Agency benchmarks suggest retargeting audiences convert at three to five times the rate of cold audiences, and that prospecting returns lower ROAS but can bring in volume. Treat such figures as one agency's experience, not a promise for your store.

Advantage+ shopping merges both stages into a single campaign. One 2026 analysis says it suits accounts with 100 or more purchase events a week, and that you give up granular control in return for algorithmic optimisation. Smaller stores often do better keeping retargeting separate until volume builds. If you would rather hand campaign management to a specialist, a Google Shopping management guide shows what that kind of service covers.

Creative that makes catalogue ads perform

A DPA is only as good as the images in your feed, because the product image and price carry most of the ad. Some practical rules:

  • Use clean square images with a consistent background.
  • Show the sale price next to the original price with an overlay when you run promotions.
  • For Advantage+ shopping, Meta recommends 10 to 20 creative assets in a mix of static, video and carousel formats.
  • Keep product information complete: size, colour, material and brand give the algorithm more to match on.

For stores selling across Europe, the text also needs to read naturally in each market. A Swedish shopper, a German one and a Dutch one should each see titles and descriptions in their own language, with local currency and VAT-inclusive prices. Textfinity's AI configs rewrite titles and descriptions to each channel's rules and translate them into 25 European languages, with a review step before any text reaches a feed.

Feed and tracking problems to check first

When DPA results disappoint, look at data before creative or budget.

  • ID mismatches. The most common and costly error, covered above.
  • Low catalogue match rate. One practitioner source says that below an 85% match rate Meta cannot rebuild visitors' product journeys properly. Look in Commerce Manager under Catalogue, then Catalogue Diagnostics, not in campaign reporting.
  • Stale stock and prices. A feed refreshed once a week will advertise products you no longer have.
  • Missing attributes. Brand, category, size and colour gaps limit both matching and product set filtering. Fashion stores in particular should read our notes on feeds for fashion: sizes, colours and variants.
  • Consent blocking everything. If the pixel never fires for most visitors, check your banner configuration before blaming the campaign.

A useful habit is a weekly five-minute check: diagnostics errors, match rate, items out of stock and a test event on one product page.

Keeping the feed clean without manual work

Most DPA problems are feed problems, and feeds go wrong when someone edits a spreadsheet by hand. Textfinity reads your catalogue from Shopify, WooCommerce, Magento, PrestaShop, BigCommerce, a CSV, TSV or Google Shopping XML file, or a Google Sheet. It then maps, filters and publishes one feed per channel and market to a stable URL that rebuilds on a schedule. You can point your Meta catalogue at that URL and let it refresh.

Processing runs on German infrastructure and the AI models are pinned to EU-hosted endpoints, which matters if your data protection policy promises that product data stays in Europe.

Plans on the pricing page include Free at $0 a month, Basic at $4.99 a month or $49.90 a year, Standard at $9.99 a month or $99.90 a year, and Premium at $14.99 a month or $149.90 a year. If you would prefer not to configure it yourself, have us set it up: you send the store and channels, and we connect the catalogue and build the feeds. Agencies running several stores can look at feed management for agencies, and if you are comparing options, our checklist on what to look for in product feed management software is a good start.

Keeping the feed clean without manual work

FAQ

What does DPA stand for in advertising?

DPA stands for dynamic product ads. They are automated ads that pull items from your product catalogue and show each person products they viewed or are likely to want. Meta's current name for the format is Advantage+ catalogue ads.

Do I need a product feed to run dynamic product ads?

Yes. The catalogue is a structured file or connection holding each product's name, price, image, availability and link. Meta combines it with Pixel or Conversions API data to decide what each person sees.

No. Swedish rules require informed consent before cookies are stored or read, and the Meta Pixel should not fire before a visitor opts in. Your consent platform provider or a data protection adviser can confirm the exact configuration for your store.

Should I start with retargeting or prospecting?

Start with retargeting. Audiences of recent product viewers and basket abandoners are the highest intent, and they let you confirm that IDs and events match. Add prospecting once the catalogue is clean and purchase volume is steady.

How often should the catalogue update?

At least daily for catalogues with changing stock or prices. A scheduled feed URL that rebuilds automatically keeps Meta in step with your store without manual uploads.

Sources