Admitad Integration

Without a feed, publishers on Admitad can only promote your program with generic banners or a handful of manually shared links. A product feed lets them pull in your actual catalog — names, images, prices, and availability — and build individual product links, comparison listings, or cashback offers at scale instead of entering products by hand.

1. Price comparison and cashback publishers can list many more of your products, which typically means more placements and more chances to earn a commission.
2. Product data (price, stock status) stays closer to what's actually on your site, reducing the risk of publishers promoting an outdated price or an out-of-stock item.
3. New products become available to publishers automatically the next time your feed is refreshed, instead of waiting for someone to update a link manually.

A detail that is easy to miss when preparing a feed for an affiliate network: once your feed is uploaded, Admitad automatically appends its own tracking parameters to the product URLs it contains so that clicks and resulting sales can be attributed back to the correct publisher and program.

Because of this, Admitad's own documentation advises submitting product page URLs without UTM tags or other tracking parameters already attached — let Admitad's parameters be the ones added to the link. Feed fields that accept a product URL are commonly labelled url, link, or url_address depending on the feed, and all are read the same way.

Admitad accepts product feeds in several formats: CSV, XML, YML, and files already formatted for Google Merchant Center (which must in turn meet Google's own product data specification). You can also attach more than one feed to a single program — for example split by language, product category, price tier, or format.

For a CSV feed, Admitad's documentation sets out a few strict syntax rules:

1. Only one delimiter type may be used to separate values in the file: comma ( , ), semicolon ( ; ), vertical line ( | ), tab, or double dash ( -- ).
2. The character chosen as the delimiter must not appear anywhere else inside the data (for example, inside a product description), or the row will not parse correctly.
3. Every product must be on its own row, and every row must contain the same number of values — if a field has no value, it should be left as an empty "" rather than omitted.

For an XML feed, product data must be contained inside <item> or <entry> tags. The Google g: namespace prefix on attributes is optional — the file is processed correctly whether it's present or not. Size, gender, and color, if present, should be passed inside a <param> tag rather than as top-level attributes.

One practical note worth knowing before you connect a feed: Admitad's column/attribute names are not read by a rigid automated schema. Admitad's own team maps and uploads each submitted feed into the program's Product feeds setting, which is why equivalent fields (like url, link, and url_address for the product page URL) are all accepted.

The table below lists the fields documented in Admitad's own product feed guidance for CSV-based feeds — five mandatory and six recommended. Equivalent XML/YML feeds carry the same underlying data under their own tag names.

For XML feeds built on the Google Merchant structure, size, gender, and color are supported but must be passed inside a <param> tag rather than as separate top-level fields.

Feedance builds and maintains the product feed itself; connecting it to Admitad is a slightly more assisted process than a fully self-serve dashboard upload, because Admitad's own team completes the final ingestion step.

1. In Feedance, generate a feed for your Admitad program in CSV, XML, or YML format, mapping your product data to the fields above (at minimum category_name, offer_id, url, price, and currencyId).
2. Make sure product URLs in the feed are clean, with no UTM or other tracking parameters, since Admitad appends its own tracking parameters after the feed is uploaded.
3. Host the feed at a stable, always-accessible URL — Feedance keeps this URL live and rebuilds the file whenever it publishes an update.
4. Share the feed URL with your Admitad account contact or add it via your program's General settings; Admitad's specialists connect and configure it in the Product feeds field on their side.
5. If you sell in multiple languages, categories, or price tiers, you can repeat this with separate feed URLs, since a single program can carry more than one feed.

Admitad's publicly accessible documentation does not state one fixed pull interval, so treat this as general best practice rather than an Admitad-specific rule: keep the feed URL live and accessible at all times, since Admitad (and the publishers using your catalog) will re-fetch it periodically rather than relying on a one-time upload. Update at least daily, and more frequently if prices or stock levels change often, so publishers are never linking to an out-of-stock item or an outdated price.

Admitad's own feed documentation calls out a small number of specific ways a CSV feed can fail to process correctly:

1. Delimiter character reused inside the data. If you use a comma as the column delimiter but a product description also contains a comma, the row will not parse correctly. Fix: pick a delimiter (comma, semicolon, vertical line, tab, or double dash) that never appears inside your text fields, or strip/escape it from the data.
2. Inconsistent number of columns across rows. Every row in the file must contain the same number of values. Fix: use an empty "" for any field that has no value for a given product rather than leaving the column out entirely.
3. Missing one of the five mandatory fields. A row without a populated category_name, offer_id, url, price, or currencyId will not carry the data Admitad needs. Fix: validate that all five required fields are present and filled in before submitting the feed.

These are general feed best practices — not Admitad-specific requirements — that help your listings perform better once they're live on publisher sites:

1. Fill in the recommended fields (name, picture, description, oldprice, vendor, available) rather than only the five mandatory ones — Admitad's own guidance notes that products with an image and description are more likely to convert.
2. Use the highest-resolution product images you have; low-resolution images look worse across the range of publisher sites and formats that pull from your feed.
3. Keep product URLs clean and free of UTM parameters so Admitad's own tracking parameters attach correctly for commission attribution.
4. Split large or multi-market catalogs into separate feeds by language, category, or price tier so publishers can select the slice that's relevant to their audience.
5. Keep the feed at one stable URL that stays online continuously, rather than a URL that changes or goes offline between updates.

What feed formats does Admitad accept?
CSV, XML, YML, and feeds already formatted for Google Merchant Center.

Do I have to match an exact column schema?
Not rigidly. Because Admitad's own specialists map and upload each feed, equivalent field names (such as url, link, or url_address for the product page URL) are all accepted — but the five mandatory fields (category_name, offer_id, url, price, currencyId) must be present.

Do I upload the feed myself in an Admitad dashboard?
You provide and host the feed URL, but the final connection step — attaching it to your program's Product feeds setting — is completed by Admitad's own team rather than a fully automated self-serve upload.

Will using a feed break my tracking links?
No — submit clean product URLs without UTM tags, and Admitad appends its own tracking parameters automatically once the feed is live.

Can I run more than one feed on the same program?
Yes. Admitad supports attaching multiple feeds to a single program, for example split by language, category, price tier, or file format.

What happens if my CSV has rows with different numbers of columns?
The file will not process correctly. Every row needs the same number of values, with empty fields represented as "" rather than left out.