Programme Setup
Part of Affiliate landing pages and product feeds
Designing product feeds publishers can actually use
Map product feed fields to publisher tasks, keep item IDs stable and check the downloaded data against live product pages.
Design an affiliate product feed around what publishers need to do: find the right item, describe it accurately and send a reader to the correct page. A large export with unstable IDs or vague variant names may be less useful than a smaller, dependable catalogue.
Start with the publishing task
A comparison publisher may need precise model, size and compatibility fields. An editorial site may need a readable title, image, short description and direct destination. A deal placement needs the current price and clear offer conditions. Include confirmed values and make a temporary offer distinguishable from the ordinary price.
Map fields before exporting:
| Field group | Publisher use | Advertiser check |
|---|---|---|
| Stable item and variant ID | Keeps updates attached to the same item | Does the ID survive a title or price change? |
| Title and attributes | Identifies the model or variant | Can similar variants be distinguished? |
| Product URL and image | Shows and reaches the item | Does the URL open the intended page? |
| Price, currency and offer | States current commercial facts | Does the page show the same offer and limits? |
| Availability | Avoids presenting an unavailable variant as purchasable | Does it agree with the page and ordering state? |
The mandatory fields depend on the chosen format. Awin’s Google-format product specification includes an example product JSON with fields such as id, title, description, link and image_link. Check the relevant format’s documentation for its requirements rather than assuming a universal schema.
What each publisher type needs from the feed
- Comparison publisher
- Precise model, size and compatibility fields
- Editorial site
- Readable title, image, short description and direct destination
- Deal placement
- Current price and clear offer conditions
Advertiser checks for each field group
- Stable item and variant IDDoes the ID survive a title or price change?
- Title and attributesCan similar variants be distinguished?
- Product URL and imageDoes the URL open the intended page?
- Price, currency and offerDoes the page show the same offer and limits?
- AvailabilityDoes it agree with the page and ordering state?
Example product fields in Awin's Google-format specification
- id
- title
- description
- link
- image_link
Keep identities and destinations clear
Use an ID for the sellable item or variant the publisher displays. Keeping IDs stable when titles change helps publishers retain product references.
The product URL should open the specific item with the relevant variant apparent. Awin’s Google-format feed example includes a link field in its product JSON. Awin’s publisher feed can provide an affiliate deep link. Confirm which URL the advertiser submits and which link the publisher receives; do not pre-wrap a field unless the chosen platform requests it.
Check the export a publisher receives
Assign each field to its catalogue, pricing or stock source. Set a processing schedule that reflects how often important values change. For a manually uploaded feed, plan another upload when those values change; do not assume updates propagate automatically.
After processing, check errors, rejected rows and unexpected changes in item count. Sample the publisher-facing download against the store: compare IDs, variant names, price, currency, images, availability and destinations. A successful import does not establish that every commercial fact is current. The separate feed-accuracy process should continue those comparisons after launch.
When a product is discontinued or a material claim changes, tell affected publishers which IDs and facts changed and when. Automated tiles may refresh from a feed; manually written recommendations need the publisher’s attention.
From field mapping to publisher sign-off
- Map fields to publisher tasksStart from what the publisher must do: find the item, describe it accurately, send the reader to the right page.
- Assign each field to its sourceCatalogue, pricing or stock.
- Set a processing scheduleMatch it to how often the important values change.
- Re-upload if the feed is manualDo not assume updates propagate automatically.
- Review errors and rejected rowsWatch for unexpected changes in item count.
- Sample the download against the storeCompare IDs, variant names, price, currency, images, availability and destinations.
- Notify affected publishersFlag discontinued products and changed material claims by ID, and say when they changed.
