If you have to generate unique product IDs for the affiliate datafeed only, consider the following: numeric IDs work the best, because they leverage the power of database software. Avoid letters if you can. Only use hyphens, dots or underscores if there is a practical benefit for doing so. Don't add them just "for looks."
MAKE SURE that there are no duplicate records with the same product ID in the datafeed.
If alternative categories are available for a product, use additional columns for the alternative categories. Additional categories are often special promotional categories like Clearance and On Sale. Or, for example, a category that can be a top category by itself can also be a subcategory. For example: Sport Shoes can be top category and you also can have Sport Shoes as a subcategory for Women's Shoes, Men's Shoes and Kids' Shoes. I will come back to categories and category hierarchies and alternatives to static hierarchies a bit later (Faceted Classification).
If a product has multiple size and color options, don't send a record for each possible combination unless you have a separate product detail page for each of them. Add the main SKU or Master SKU to the datafeed and provide available options (attributes) in separate columns. I will come back to the scenario where you might not have certain combinations available for the product, or you might have different prices for different combinations.
You might want to provide the direct URL without affiliate ID as separate column. This especially makes sense if the affiliate link is a completely different URL than the direct URL and not only the direct URL with the affiliate ID as additional parameter.
If you are concerned about affiliates showing items on sale after a sale ends, you have multiple ways to prevent and combat it.
Prevention: Add a column for the sale's end date. If you can, because there are no competitive reasons not to, provide the sale's start date if you know that a product will be on sale on a specific date and know the sale price. Some affiliates can work this into their marketing planning and increase exposure and traffic to your offers.
If possible get datafeed access information, such as: which affiliate accesses the datafeed when (how often), how (if you offer multiple delivery options) and in which format (if you provide the datafeed in more than one format).
Combat issues: Check affiliate sites that use your feed (this is where knowing where to look for datafeed access information comes in handy). Separate tracking and statistics for affiliate product detail links might help or referral data in the Website log of your Webserver.
If you see something you don't like, contact the affiliate. For repeat offenders block access to the feed if you can. In severe cases terminate the relationship. Adding guidelines to your affiliate resource pages or terms and conditions might be a good idea, too.
If you utilize matrix-like, faceted or dynamic drill-down navigation (Faceted Classification) without having pre-defined paths or hierarchy offered by products like Endeca Guided Navigation, Dieselpoint Faceted Navigation or Fast ESP Dynamic Drill-down, great!
I love the navigation based on Faceted Classification. The resulting dramatic increase in conversion proves it is the right approach, and the way to do it.
You should provide all relevant attributes in separate columns via your datafeed.
But not everybody is that advanced yet. Also, the price tag for a professional solution that leverages this method of content delivery, filtering and refinement is beyond the means of the average affiliate - and many merchants as well.
If you have the money to afford the solutions mentioned above, you should have the money and resources needed to generate for your affiliate product datafeed an artificial hierarchy based on the common paths taken by users on your site.
Navigation based on Faceted Classification and XML Feeds excel and show their real power in cases where you have products with multiple possible values for a single attribute.
In this case the delimited format shows one of its biggest weaknesses, which can only be worked around to a limited extent by having multiple values for an attribute in one "Field" separated by a third delimiter (not the same as used for columns and rows).
To provide information about the availability or the lack of specific combinations of values for two or more attributes, delimited values for each attribute involved must be ordered, and nonexistent attribute values for another attribute value must be specified via a value that indicates that it does not "exist."
Example: Product A is available in three sizes: S, M and L and the colors: white and black. All but one of the six combinations is available; L/black. "-" indicates that the combination does not exist and a comma is used to separate the values.
The values for Size and Color in the datafeed
If you never have combinations of more than two attributes to worry about, the missing value pair for the two attributes could be dropped. I used it in the example because you would need it for combinations of three attributes.
No problem if you have a different price for each value pair. Simply add another column for the prices, structured the same as the other attributes. Like this (0.00 indicates "not available", you could use something like -1 to make it more obvious): Price: 5.00,5.00,7.00,7.00,10.00,0.00
As you can see, this method has its limitations and becomes impractical for large number of attributes and/or values.
This eliminates one more step for the user to purchase the product and at the same time eliminates one more step where the user might decide to "bail out" and leave the sales funnel.
|< previous page||<< Index||next page >|
|Merchant Product Datafeeds for Affiliates - 101 Page 1/3||Articles Index||Merchant Product Datafeeds for Affiliates - 101 Page 3/3|
©2006 Carsten Cumbrowski.
Replication of this Content in full or in part without written permission by the author is prohibited.
Other Data Feed Guides, Articles and Resources for Affiliates and Advertisers|