Kelkoo Sales Tracking
How to configure Kelkoo Sales Tracking at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for Kelkoo Sales Tracking (KST) on a merchant website and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Kelkoo Sales Tracking Lead Tag and Conversion Tag.
What the service does in this scope. KST uses first-party cookies set on the merchant's own domain. The Lead Tag sets the tracking cookie when a user arrives from a Kelkoo Group ad; the Conversion Tag reads it on the confirmation page and sends order data. The kelkooId cookie lasts 12 months. Kelkoo states that the Lead Tag must be gated behind consent while the Conversion Tag does not require separate consent, relying on legitimate interest for the order data it sends. A server-to-server option exists, with consent managed directly by the merchant.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Lead Tag and Conversion Tag both loaded only after Consenter consent. |
| Configuration B — Medium risk (default configuration) | Lead Tag after consent; Conversion Tag without consent, as Kelkoo recommends. |
⚠ Recommendation. In B the Conversion Tag reads a cookie only set after consent, but sends order data on the basis of legitimate interest. Have your DPO confirm this legal basis (GDPR) separately from the device-access question (§ 25 TDDDG).
Step 1 — Configure Kelkoo Sales Tracking
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Medium risk (default configuration) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Support marketing analytics | Support marketing analytics |
| 2 | Lead Tag | Landing pages / tag manager | After consent | After consent |
| 3 | Conversion Tag | Confirmation page | After consent | Without consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Kelkoo Group is a European company; check its terms for US sub-processors and list the United States if present.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Medium risk (default configuration) |
|---|---|---|
| Processing purposes | Support marketing analytics | Support marketing analytics |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers |
| Data categories | Device identifiers, Browsing and interaction data, e-commerce Activity | Device identifiers, Browsing and interaction data, e-commerce Activity |
| Legal role of data recipient | Individual Controller | Individual Controller |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | 12 months | 12 months |
| Processing location | EU | EU |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on