Kelkoo Integration

Kelkoo Group positions itself to retailers as a way to reach comparison-shopping demand across dozens of European markets from a single feed submission.

1. Multi-market reach from one feed: the same feed can power listings across Kelkoo's roughly 29 markets instead of requiring a separate setup per country.
2. Performance-based traffic: Kelkoo runs on a cost-per-click model, so you pay for clicks your offers actually receive rather than for impressions.
3. Extended distribution: offers submitted to Kelkoo can also surface across its network of 2,700+ direct publishers and Google/Bing Shopping, per Kelkoo Group's own description of its traffic sources.
4. Category-aware matching: support for identifiers like EAN and manufacturer part numbers, plus category-specific fields such as efficiency-class for appliances, cars and tyres, helps offers land in the right comparison results.

Kelkoo Group's merchant-facing pricing product, Performance Flex, replaces flat cost-per-click bids with a dynamic model built around four stages: Connect (import your product feed), Analyse (machine learning evaluates sales potential from performance data and intent signals), Optimise (CPCs adjust automatically toward your ROAS goals), and Refine (ongoing monitoring by Kelkoo's technology and specialists).

Kelkoo Group reports that campaigns on Performance Flex hit ROAS targets 93% of the time, with an average 1.7% conversion rate and a €152 average order value across its comparison shopping sites, Google/Bing Shopping Ads, and partner network spanning 29 markets. Because pricing is CPC-based, feed accuracy on price, availability and shipping cost has a direct effect on how much qualified traffic and spend a listing attracts.

Kelkoo Group accepts product data as an XML file, a delimited text/CSV file, or a feed you've already built for another channel (such as a Google Shopping-format feed), since Kelkoo Group states it can often reuse existing feed formats rather than requiring a bespoke build.

1. For text/CSV feeds, the first line must be a header row naming every attribute, field separators must be used consistently, and every product row needs the same number of fields — use an empty placeholder rather than dropping a field.
2. For XML feeds, tag names must match Kelkoo's specification exactly, and Kelkoo Group recommends wrapping free-text fields (titles, descriptions) in CDATA sections to protect special characters like &, < and > — an invalid XML file is rejected outright and none of its offers will update until it's fixed.
3. Kelkoo recommends validating XML feeds with the W3C Markup Validation Service before submission.
4. Feeds can be delivered over HTTP/HTTPS, retrieved by Kelkoo via FTP, or uploaded directly to Kelkoo's own FTP server, and the feed's file name needs to stay the same over time so Kelkoo's scheduled fetch jobs keep finding it.

Kelkoo Group's product data specification defines both required and recommended attributes. Missing a required attribute can keep that specific product out of Kelkoo's shopping listings entirely, while missing a recommended one can simply reduce how often it's shown. Based on Kelkoo's own sample feed and published field descriptions, the core attributes are:

Feedance handles the field mapping and formatting so you don't hand-edit XML tags for a single sales channel.

1. Connect your existing product source — Shopify, WooCommerce, PrestaShop, a PIM, or a raw CSV/XML export — to Feedance.
2. Select Kelkoo as a destination and map your fields to Kelkoo's attribute names, including the required id, title, product-url, price, merchant-category and availability, plus the recommended attributes above.
3. Let Feedance automatically wrap free-text fields in CDATA and validate the generated XML before publishing, so a stray "&" in a title can't take your entire feed offline.
4. Publish a stable feed URL with a file name that stays constant over time, matching what Kelkoo's fetch schedule expects.
5. Monitor feed health inside Feedance and get alerted if Kelkoo reports fetch failures or a spike in rejected offers.

Kelkoo Group fetches merchant feeds roughly 4 to 15 times a day depending on the market, with schedules aligned to that country's time zone (CET, GMT or UTC).

Because Kelkoo's model is cost-per-click, and Kelkoo itself asks merchants to provide the freshest possible availability status and complete, correct shipping information, keeping price, stock and delivery data current between fetches directly affects both offer eligibility and click quality. Feedance can regenerate and republish your Kelkoo feed on a schedule aligned to Kelkoo's fetch windows so price or stock changes don't sit stale for a full day.

1. Invalid XML rejects the whole feed. Kelkoo Group's documentation warns that an invalid XML file cannot be processed and offers will not be updated — a single unescaped &, < or > in a title or description can break the entire file.
2. Missing CDATA around free text. Kelkoo recommends CDATA-wrapping text fields specifically to prevent this class of failure.
3. Non-numeric characters in numeric fields. Values like price must contain digits only (no currency symbols or letters), and decimals must use a dot rather than a comma.
4. Uneven field counts in text/CSV feeds. Every row needs the same number of fields as the header row; a missing separator on an empty field misaligns the rest of that row.
5. Missing required attributes. Leaving out id, title, product-url, price, merchant-category or availability can keep that specific product out of Kelkoo's listings even if the rest of the feed is otherwise valid.
6. Unstable feed file names or URLs. Kelkoo expects the feed's file name to stay constant over time; changing it can cause scheduled fetch jobs to miss updates entirely.

1. Wrap titles and descriptions in CDATA so special characters never put the whole feed at risk.
2. Add EAN/GTIN and MPN wherever you have them — Kelkoo explicitly uses these identifiers for product-level matching.
3. Keep availability and price genuinely current between Kelkoo's fetch windows, since Performance Flex CPCs and campaign reach respond to how well a listing is performing.
4. Fill in delivery-cost and delivery-time accurately; Kelkoo lists complete, correct shipping information among the practices it expects in order to avoid offers being rejected.
5. Use merchant-category consistently, since Kelkoo's own categorisation process relies on it to place your products correctly.
6. For regulated categories, add efficiency-class (cars, tyres, appliances) — Kelkoo calls this out as highly recommended for matching in those verticals.
7. Validate XML with the W3C Markup Validation Service, or let Feedance validate automatically, before every submission.

Does Kelkoo require XML, or can I send a CSV? Kelkoo Group accepts either an XML feed or a delimited text/CSV feed with a header row, and can often reuse a feed you've already built for another channel.

How often does Kelkoo fetch my feed? Roughly 4 to 15 times a day depending on the country, aligned to that market's time zone.

What happens if my XML is invalid? The whole file is rejected and none of your offers update until it's fixed — Kelkoo recommends CDATA-wrapping text fields and validating with the W3C validator to prevent this.

Do I need a GTIN/EAN for every product? EAN is a recommended, not required, field, but Kelkoo states it "guarantees good matching at the product level," so it's worth including whenever available.

Is Kelkoo pay-per-click? Yes — Kelkoo Group runs on a cost-per-click model, and its Performance Flex product dynamically adjusts CPCs toward each retailer's ROAS goals instead of using flat bids.

Which countries can one Kelkoo feed reach? Kelkoo Group runs comparison shopping sites and a publisher network across roughly two dozen European markets plus Brazil, so a single feed submission can be localized across that footprint.