In practice, this has a direct consequence for how you configure your Consent Management Platform (CMP): the Lead Tag must be gated behind consent, but the Conversion Tag should not be blocked by a missing consent signal — blocking it unnecessarily will cause Kelkoo to under-report your sales, even though you're fully compliant.
If you install via Google Tag Manager
Configure your CMP's GTM integration (e.g. via consent mode, a Tag Sequencing setup, or a blocking trigger) so that:
-
the Kelkoo Lead Tag (Custom HTML tag loading
leadtag.js) only fires once the relevant consent category (typically "Analytics" or "Measurement") has been granted; -
the Kelkoo Sales Tracking tag is not subject to the same consent gate, and fires on every completed order regardless of consent status.
If you install manually
-
Wrap the Lead Tag
<script>(Step 1) in whatever consent-check logic your CMP provides (most CMPs expose a JS callback or adata-category/data-consentattribute mechanism — refer to your CMP's documentation for the exact syntax). -
The Conversion Tag
<script>(Step 2) does not need to be wrapped in a consent check.
Verifying your configuration
-
Confirm the tracking cookie (
kelkooId) is only created after consent is granted, by testing with consent declined and then accepted. -
Confirm the Conversion Tag still fires and a sale is recorded even in a session where consent was declined (this is expected and compliant — see GDPR Notice for Kelkoo Sales Tracking ).
-
Incorrect CMP configuration is one of the most common causes of under-reported conversions — if you're seeing a discrepancy between your own analytics and Kelkoo's reporting, this is one of the first things to check.
For full legal and compliance details (cookie list, data retention, data controller information), see the GDPR Notice for Kelkoo Sales Tracking