Adform Integration

Adform's Dynamic Creative Optimization tools let advertisers build ads whose content — product name, price, image, and description — updates automatically from a connected product feed, instead of every SKU or price change requiring a manually rebuilt banner.

1. Automatically populate ad creative with current product names, prices, and images, without a designer rebuilding each variant.
2. Show shoppers ads for products they viewed or added to cart (product retargeting), driven directly by the feed's product data.
3. Keep pricing and availability messaging accurate across a running campaign as your catalog changes.
4. Scale creative production across large catalogs by letting the feed — not manual design work — populate each ad variation.

Adform builds dynamic ads from two components: one or more creative shells (HTML5 or rich media templates containing the display logic) and a data source telling each shell what content to show. For product-targeting and product-retargeting banners, that data source is a product feed. Adform's own help documentation shows product records passed to the ad system with fields including product_id, product_name, product_price, product_image, and product_deeplink — notably, the ad system uses the deeplink supplied in each product record for the click-through, rather than one static landing-page URL, so a rendered banner links straight to the specific product it displays.

Adform's broader Dynamic Content Ads (DCO) feature works a little differently: it reads a separate 'version spreadsheet' (an .xlsx file with one row per ad version) mapped to the dynamic elements inside a creative shell, and a single dynamic ad setup can combine up to 15 creative shells. Feedance's role sits on the product-feed side of this system — keeping the underlying product data (names, prices, images, availability) accurate and current, which is the data advertisers then reference when building product-targeting banners or preparing a version spreadsheet for DCO.

Adform's documented product feed formats are XML and CSV. Integration guidance for Adform's dynamic ad system specifies that an XML feed must follow a products > product structure — Adform explicitly does not accept XML feeds built on the structure used for Google Retail (Merchant Center) feeds, so a feed formatted for Google Shopping cannot simply be reused as-is for Adform.

Beyond format and structure, Adform's publicly available documentation does not detail file-size ceilings, hosting requirements, or a maximum SKU count per feed. If your account has specific limits, Adform typically confirms them when you set up the Client ID and Template ID tied to your feed inside the platform.

Adform's help documentation for building product-targeting ads shows the following fields being read from the feed and returned to the ad system. This reflects Adform's own sample product data rather than a fully published field dictionary, so treat it as the confirmed core set rather than an exhaustive spec:

Connecting Adform to Feedance follows the same feed-based workflow used across Feedance's supported channels:

1. Import your product catalog into Feedance from your store, ERP, or an existing feed file, so Feedance holds one accurate source of product data.
2. Add Adform as a destination channel and let Feedance map your product data to the fields Adform expects for product-targeting and retargeting ads (product_id, product_name, product_price, product_image, product_deeplink, and the related category fields).
3. Generate the Adform-ready feed URL from Feedance and provide it when setting up your product feed and its Client ID / Template ID inside Adform, following Adform's own feed-upload flow.
4. Set an update schedule in Feedance so price, stock, and availability changes flow through automatically, then check the feed inside Adform after the first sync to confirm products, prices, and images are rendering correctly in a test creative.

Adform's public documentation does not publish a mandated minimum refresh interval for product feeds. As a general best practice for any retargeting or dynamic-creative feed, update it at least once daily so Adform is never serving ads for an out-of-stock item, a stale price, or a discontinued product — catalogs with frequent price or stock changes may warrant more frequent updates. Feedance lets you schedule automatic updates so this stays hands-off rather than manual.

Adform does not publish a public list of feed error codes, so the items below combine the one structural failure mode documented across Adform's own feed-integration ecosystem with general causes that affect any product-feed-driven ad platform:

1. Wrong feed structure. Adform's product feed integrations expect a products > product XML structure (or the equivalent CSV column layout); feeds built on other schemas, such as the structure used for Google Retail/Merchant Center feeds, are not accepted and need to be reformatted.
2. Non-HTTPS image or destination URLs. Integration guidance for Adform's dynamic feed system flags that image and link URLs should use HTTPS; feeds referencing HTTP-only assets can fail validation or fail to render inside the ad.
3. Missing core fields. Rows missing product_id, product_price, product_image, or product_deeplink will typically prevent that product from rendering correctly, since these are the fields a creative shell reads directly.
4. Feed and Client ID / Template ID mismatch. Because Adform ties a feed to a specific Client ID and Template ID at upload, pointing a campaign at the wrong IDs — or restructuring the feed without updating the mapping — is a common cause of ads not picking up new data.

These are general product-feed best practices rather than Adform-specific requirements, but they apply directly to any feed powering dynamic or retargeting ads:

1. Keep product titles concise and specific — dynamic ad templates have limited space to render text.
2. Use high-resolution, clean product images with a consistent aspect ratio so they scale correctly across the many banner sizes a dynamic campaign can serve.
3. Keep pricing and availability fields synced in near-real time to avoid serving ads for sold-out or repriced items.
4. Populate category fields consistently so category-based filtering and segmentation inside Adform work as intended.
5. Test a sample of feed rows against your creative shell before launching broadly, since a single malformed row can affect how a shell renders.

Does Adform support both CSV and XML product feeds?
Yes — Adform's product feed integrations support CSV and XML, with XML feeds expected to follow Adform's own products > product structure rather than a generic shopping-feed schema.

Can I reuse my Google Merchant Center feed for Adform?
Not directly. Documentation for feed-based integrations with Adform notes that XML feeds built on the Google Retail feed structure are not accepted, so the feed needs to be reformatted to Adform's expected structure and field names first.

What's the difference between Adform's product-targeting ads and its Dynamic Content Ads?
Product-targeting and retargeting banners read product data (name, price, image, deeplink) directly from your feed. Dynamic Content Ads (DCO) instead use a version spreadsheet mapped to a creative shell, and a single dynamic ad setup can combine up to 15 creative shells.

Do I need a developer to connect my feed to Adform?
Not with Feedance. Feedance handles the field mapping and feed formatting; inside Adform you'll still need the Client ID and Template ID for your feed, which Adform provides when the feed is uploaded.