If you’re a Kelkoo Feed publisher please read, you may need to make changes to your feed integration.
On a release scheduled for 17th March 2014 the following changes will be made to the feed you receive:
In a previous release:
Read on for more details on all these changes.
The catalog feed format updated with new attributes will appear as follows:
<specification name=”Heade_Manuf” translation=”Brand”>
If you use a standard XML parser to process the catalog feed files no change should be required.
Please find a before and after example below:
Attribute file :
<KK:prd-attr name=”Type” cmp=”false” disp=”Category”/>
<KK:prd-attr name=”Heade_Manuf” cmp=”false” disp=”Brand”/>
After the simplification, we have a catalog feed with enriched values like this (new values in bold font) :
<specification name=”Type” translation=”Category”>
<specification name=”Heade_Manuf” translation=”Brand”>
Currently your catalog feed contains the entire Kelkoo catalog, regardless of whether there are any offers linked to them. As of the 17th March your catalog feed will contain catalogs with offers linked to them only. As a result your catalog feed file will reduce in size significantly.
Merchant feeds are now available once per hour instead of once per day. Use the status file in the merchant feed directory to know when the updated feed is ready to download. The feed contains only active merchants and as such can be used to remove invalid offers from your offer feed. For example, a merchant may remove all their offers in the middle of the day leaving you with a number of invalid offers in your offer feed. By checking the merchant file you’ll be able to see this change very quickly and remove any offers from the missing merchant in the offer feed.
If you have any questions or comment you can email us.
More and more of your revenue generating traffic is coming from mobile sources, that’s one of the realities of e-commerce we’ve seen emerge over the last few years. Retailers have had different responses, some have created mobile specific sites, others have created fully responsive sites, many have done nothing.
Up until now we’ve supported mobile URLs, so in instances where Retailers have mobile site URLs (think http://m.amazon.com) and they’ve made them available to us, we’ve passed them on to you via the element <MobileUrl>.
However, partners with mobile compliant responsive sites usually do not have separate URLs. Additionally many sites would auto-redirect to a mobile compliant site based on user agent information. Furthermore ECS did not allow you to return only mobile compliant offers, or even prioritise them above non-mobile compliant offers. Now we’re offering you these extra pieces of functionality so you can direct your mobile users to offers that are more likely to result in conversion.
Here are the three pieces of functionality:
1) I want to only return offers that are mobile compliant.
To do this simply include in your ECS ProductSearch query “mobileFriendly=1″. Only offers where mobileFriendly=true will be returned.
2) I want mobile compliant offers to be prioritized over non-mobile compliant offers.
To do this simply include in your ECS ProductSearch query “&boostMobileResults=1″, all non-mobile compliant offers will appear below mobile compliant ones.
3) I want to know if an offer is mobile compliant
If an offer is mobile compliant it will include the tag <MobileFriendly>true</MobileFriendly>.
If you have any comments or questions about our products or services you can email us at firstname.lastname@example.org
Kelkoo Publisher Network team
We’ve added some new fields in our API and feeds.
We’ve also added:
These fields will go into effect on Monday 9th September and should not require any change from you as XML schemas in both the webservice and feeds will remain unchanged. For those receiving CSV feeds please ensure that that your processing can handle the addition of new fields.
If you have any feedback on Kelkoo tools or services please email kpn-feedback ( at ) lists( dot ) kelkoo ( dot ) com
If you’ve logged into your account recently you may have noticed a new report we’ve recently put live called “Custom parameters”. This report is designed to give you a much deeper level of reporting granularity through the use of up to three custom parameters which you as a partner can define.
In order to begin using this report effectively you need to ensure that and Kelkoo URLs from ECS or from our feed going to a retailer offer includes the custom parameter.
Some examples of what a custom parameter could be:
Example 1: an SEM campaign ID
Example 2: a search term entered by a user
Example 3: a referrer URL
The maximum lengths of custom parameters vary, for example custom1 can accept larger values, particular useful for URLs (up to 511 characters in length). Custom2 & custom3 both have maximums of 127. Please adhere to these maximums if you want to be confident in meaningful reporting as anything larger will be truncated.
When you are calling ECS in a live manner (ie not caching results) you can easily apply your chosen
custom parameters to your ECS query. All offer URLs in the ECS response will then be automatically
appended. For example:
/V3/productSearch?query=ipod&sort=default_ranking&start=1&results=20&show_products= 1&show_subcategories=1&show_refinements=1&aid=[YOUR_PARTNER_ID]&custom1=x&custom2=y &custom3=z
If you choose to cache your ECS results you can still take advantage of custom parameters but it
doesn’t make sense that you would want to apply a blanket set of parameters against all your cached
offers. In this instance you must apply the custom parameters of your choice directly to the offer URLs in
the ECS response. In order to do so without breaking the URL you must include the extra parameter
addedParams. For example:
If you’re using the Kelkoo feed solution you follow the same procedure as “ECS – Cached offers” and
apply the custom parameters directly to the offer URLs in your feed, along with addedParams=true.
UPDATE: This change will now take place on the week commencing 3rd March 2014
Contains important information for partners using <lowestPrice> and <highestPrice> data, as returned in the productSearch web service.
We’re always looking for ways to improve our service and sometimes that means giving you a bit less. Currently the lowest and highest price data is returned by default in all productSearch queries. However, in the interests of making our web service responses even faster we’re removing this data by default.
If you use this data you can still get it but you need to ask for it specifically.
In your product search query include the following to return the data:
This change will take place within the next 2 weeks so please make the necessary adjustments to your queries as soon as you can.
By popular demand, it is now possible to query the Kelkoo productSearch API with only a merchantID. Every retailer on Kelkoo has a unique merchantID which you can find using our MerchantSearch API. So, by enabling a merchantID only query you’ll now be able to return all results by a particular merchant.
An example of a query for France:
It’s also worth mentioning that the productSearch API still has a 500 offer result limit, retrievable in 100 offer increments. This can be achieved using the &results and &start parameters:
The above query would return offers 101 through to 200.
A quick update to let you know that if you use Kelkoo’s ECF (e-commerce feed) solution you will notice a change in the format of our offerIDs.
What are offerIDs?
OfferIDs are a unique 32 character alpha-numeric identifier applied to each offer in Kelkoo’s database.
Why are they changing?
Up until now Kelkoo’s 2 main solutions ECS (API) & ECF (feed) have structured and applied offerIDs in a different way. As of today any new feed files you receive will include offerIDs in a format consistent with ECS.
How can I tell what the new offerIDs look like?
Here’s an example of an old offerID:
And here’s an example of the new offerID consolidated across all Kelkoo services:
Why am I still seeing old offerIDs in my feeds?
It will take some time for the changes to proliferate through your feeds, any new offers received will have the new offerID. Over time all will be replaced with the new format!
Click through rate (CTR) is a hugely important metric that has a massive impact on your bottom line, getting your users to click on an offer with legitimate interest is the key to success on the Kelkoo Partner Network.
In order to help you drive CTRs skywards you can utilise the rebate fields included on relevant offers in the productSearchV3 API. In short, if an offer is on sale, reduced from it’s original price, Kelkoo provide you more than just the sale price, we provide all of the following:
As you can see with this information is it possible to create a very compelling offer and increase your click through rate significantly. Here’s an example of how we use it on the Kelkoo site:
We’ve recently launched our Kelkoo Partner Network, and if you have a direct partnership with Kelkoo the good news is you are already part of it. Part of this launch is a brand new reporting interface that allows you to measure your leads and revenue on a daily basis across any number of our hundreds of categories.
You can log in here using your existing credentials: https://partner.kelkoo.com/signin
If you’re unsure of your credentials you can reset your password and if you’re having problems remembering your username please get in touch with your Kelkoo contact.
Included in this reporting system is the ability to export your data in a number of formats as well as extracting it using our reporting webservice. And if you’re an international partner generating leads in multiple countries you’ll be able to access all your reporting in the same place.
Designed from the ground up to be simple and informative the Kelkoo Partner Network reporting tool is there to help you make the most out of your campaigns and ultimately help you earn more. We’re continually working on it and improving the reporting functionality so we’d love to hear your feedback on how it can work for you better.
Kelkoo Product Team
A feature recently implemented across ECS templates will enable you to access video associated with a particular offer. Video will only be available in instances where it is provided by the merchant but we’re already seeing an increase in the number of merchants doing this. As such we’re making that information available to you.
Merchants are seeing an uplift in sales conversion when they include relevant videos in product pages, as such our advice is to start taking advantage of these new fields. We will continue to encourage even more merchants to include product videos.
The video field can be found under <Images> in the schema: