Adtraction Integration

Adtraction's own help documentation frames product feeds as the mechanism that lets a publisher's channel show accurate, current product information — titles, prices, image URLs and stock status — without manual data entry. For an advertiser, that means your product catalog needs to be complete and current, since publishers across the network are pulling directly from it to build their promotions.

1. Publishers can automatically reflect your real prices and stock levels instead of working from outdated screenshots or manually typed listings.
2. A structured feed reduces the manual work needed to keep every publisher's product presentation in sync with your actual catalog.
3. Because Adtraction tracks feed freshness (each feed shows a last-updated timestamp), a feed that updates reliably signals to publishers that your listings are dependable enough to promote.

In short: the feed is the shared source of truth between your store and every publisher promoting you through Adtraction.

Adtraction documents two distinct mechanisms for moving product data through the network, and it's worth knowing which one your setup will rely on:

1. Feed URL (XML). Adtraction's help center states plainly that feeds accessed this way are delivered in XML format. A feed becomes available once the relevant brand relationship has an Approved status, after which the feed URL can be copied from the platform's Products > Feeds section.
2. API v3 (JSON). For developers and advanced integrations, Adtraction also exposes product feed data through its API v3, via endpoints such as /partner/products/feed and /partner/products/feedinfo/{programId}/{channelId}, which return structured JSON product objects rather than XML. Adtraction's documentation notes that the equivalent product feed endpoints in the older API v2 are deprecated in favor of v3.

Both paths expose the same underlying product data — the difference is format and delivery method, not content.

According to Adtraction's official help center, "all product feeds provided via Adtraction are delivered in XML format" when accessed through the standard feed URL. If your integration instead goes through Adtraction's API v3, product data is returned as JSON rather than XML.

Adtraction's public documentation does not publish a separate, standalone advertiser-side feed upload specification (such as a fixed CSV template with column-by-column rules or explicit character limits). What is documented is the resulting product data structure itself — the fields that make up each product record — which is covered in the next section. If your setup requires a specific file format beyond XML/JSON, it's worth confirming directly with Adtraction, since that level of detail isn't published in their public help articles.

Adtraction's own API v3 reference documents the exact structure of each product record moving through its feed system. These are the real, documented field names — not a general ecommerce checklist — confirmed directly from Adtraction's API documentation:

Two metadata values also appear alongside feed responses: count (total products in the feed) and feed_lastupdated (the timestamp of the last sync). Adtraction has not published a formal list of which of these fields are strictly mandatory versus optional for every advertiser — the safest approach is to populate all of them as completely as possible, since publishers rely on this data to build accurate listings.

Feedance sits between your product data (store platform, ERP, or existing feed file) and the destinations that need it, including affiliate networks like Adtraction. The general process looks like this:

1. Bring in your product data. Connect your store or upload your product data into Feedance so it becomes a single managed source.
2. Create an Adtraction-targeted output. Set up a data channel in Feedance configured for Adtraction, and map your product fields to the structure Adtraction's system expects — titles, descriptions, prices, images, stock status, identifiers (SKU/EAN), manufacturer details and category, mirroring the field structure documented above.
3. Generate the feed output and connect it on the Adtraction side. Feedance produces a feed URL from your mapped data; on the Adtraction side, this is where your product data source gets linked to your approved advertiser program so publishers can retrieve current listings.
4. Set your update schedule. Configure how often Feedance refreshes the output so price and stock changes propagate on a schedule that matches how frequently Adtraction and its publishers expect fresh data (see the next section).
5. Monitor and adjust mapping over time. Because Adtraction does not publish a rigid, fixed submission template, keep an eye on how your listings actually appear to publishers and refine field mapping as needed.

Because Adtraction's own documentation is written primarily from the publisher's side (how to retrieve a brand's feed) rather than a formal advertiser upload spec, exact linking steps in the Adtraction platform can vary by program setup — Feedance's role is to keep your underlying product data clean, complete and current regardless of exactly how it's connected on Adtraction's side.

Adtraction's help center states that product feeds are "typically updated once per day, though this can vary. Some brands offer more frequent updates, while others may update less often," and that the platform surfaces a last-updated timestamp for each feed so publishers can see how current the data is.

Practically, this means a daily refresh is a reasonable baseline for most catalogs. If your prices, promotions or stock levels change more often than once a day — for example during sales periods — increasing update frequency reduces the risk of publishers promoting stale prices or out-of-stock items, which directly affects commissionable conversions on affiliate traffic.

Adtraction has not published a specific list of feed error codes or rejection reasons, so rather than invent Adtraction-specific error messages, here are the general causes that typically break affiliate product feeds and are worth checking first:

1. Missing or empty required-looking fields. Gaps in core fields such as productName, productUrl, imageUrl or productPrice can make individual products unusable to publishers even if the feed as a whole loads successfully.
2. Broken or unreachable image and product URLs. If imageUrl or productUrl point to broken links or redirect chains, publishers may skip those products entirely.
3. Stale inStock or price data. If your update frequency doesn't match how often your actual prices or stock levels change, publishers end up displaying outdated information, which can trigger customer complaints or disputed commissions.
4. Inconsistent identifiers. Mismatched or missing sku/ean values make it harder to match your feed data with tracked conversions.
5. Encoding and formatting issues. Malformed XML, incorrect character encoding, or unescaped special characters in titles/descriptions are a common general cause of feed parsing failures across affiliate and shopping feeds alike.

If you suspect Adtraction itself isn't picking up your latest data, check the feed's last-updated timestamp in the Adtraction platform first — that's the diagnostic Adtraction's own interface provides — before assuming the feed file itself is broken.

These are general product-feed best practices — not Adtraction-published rules — that help any affiliate feed perform better for publishers and shoppers alike:

1. Keep titles descriptive and specific (brand, product type, key attribute) rather than generic, since publishers often display titles as-is.
2. Fill in as many of the documented fields as apply to your catalog — category, manufacturer, manufacturer article number, EAN — rather than leaving optional-looking fields blank, since richer data gives publishers more ways to filter, categorize and present your products.
3. Use the extraInfo key/value structure for attributes that matter to your category (like color or size) instead of cramming them into the title or description.
4. Keep oldPrice accurate whenever you're running a discount, since strikethrough pricing is a strong driver of affiliate click-through.
5. Match your feed's refresh schedule to how often your actual catalog changes, rather than defaulting to the lowest common setting.
6. Periodically spot-check how your products actually render on a few publisher sites, since that's the real test of whether your field mapping is complete.

Does Adtraction require XML or CSV feeds?
Adtraction's help documentation states that feeds delivered via its standard feed URL are provided in XML format. Product data is also available in JSON form through Adtraction's API v3. A generic CSV upload path is not described in Adtraction's public documentation.

Do I need approval before my feed becomes available?
Yes. Per Adtraction's help center, a feed URL only becomes accessible once the relevant program/brand relationship has an Approved status.

How often does Adtraction refresh feed data?
Adtraction states feeds are typically updated once per day, though this varies by brand — some update more frequently, some less. Each feed shows a last-updated timestamp.

What fields does a product record include?
Based on Adtraction's own API v3 documentation, product records include fields such as productName, productDescription, productPrice, oldPrice, currency, imageUrl, productUrl, trackingUrl, inStock, sku, ean, manufacturer, manufacturerArticleNumber, productCategory, market, shipping, approvalStatus and a flexible extraInfo key/value structure.

Can Feedance manage my Adtraction feed alongside other channels?
Yes — Feedance is built to manage one underlying product data source and generate mapped outputs for multiple destinations, including affiliate networks like Adtraction, from that single source.

What if my feed isn't updating on Adtraction's side?
Check the last-updated timestamp Adtraction displays for your feed first; if it's stale, verify your export schedule in Feedance and confirm the feed URL registered with Adtraction is still correct and reachable.