Kelkoo Sales Tracking is a tracking solution based on first-party cookies.
-
Cookie-based means that the tracking is done via a small file, named "cookie"
-
First-party means that this cookie is dropped by Kelkoo Sales Tracking on your website domain, not on ours. This makes Kelkoo Sales Tracking compliant with modern browser policy
For Kelkoo Sales Tracking to work, you need to place.
-
The Lead Tag on all the landing pages defined in the product feed you sent us, to write the cookie when the user first visits your website
-
The Conversion Tag on the confirmation page, to retrieve data from the cookie and register the sale
Attribution model
Kelkoo Sales Tracking uses a "Kelkoo Channel Last Click" attribution model with a 30-day conversion window.
How it works
-
If a user clicks through Kelkoo at any point within 30 days before converting, Kelkoo receives attribution for that sale
-
This applies even if the user returns through another channel (e.g., Google, direct traffic, email) for their final visit
-
The first-party cookie ensures Kelkoo clicks are tracked across return visits from other sources
Important considerations
-
This attribution model may differ from your internal analytics or other marketing platforms
-
Attribution overlap may occur with other channels using last-click models
-
For reconciliation with Google Analytics, see: Understanding Differences Between KelkooGroup Reported Clicks in Google Analytics 4
Master Tag Functionality
Kelkoo Sales Tracking is a master tag (like Google Tag Manager). It means that this tag can "host" other tags, simplifying the implementation of all your trackers
Kelkoo Sales Tracking triggers a Google Global Site Tag, to optimize Kelkoo Group traffic sourced from Google and allows us to further optimize your campaigns.
Conversion Window
The conversion window of Kelkoo Sales Tracking is 30 days:
-
This means that we will consider any sale happening between the time of click and 30 days later as a sale generated by Kelkoo Group
-
It's important to note that this attribution model might differ from the one you use
For more information, please refer to Understanding Differences Between KelkooGroup Reported Clicks and Your Analytics Data.
FAQs
Tag Loading: Does your technology require the tags to be loaded only once for SPAs, or should they fire with each new virtual page view?
Our lead tag is used to store the user id from the kk query parameter to a first party cookie. The goal of this is the correct attribution and measurement of the sales. It need to be loaded only once.
Performance: We've noticed that the tags inject into the head section with each virtual page load, potentially affecting site performance. Do you have guidelines for minimizing this impact?
The tag does indeed load a pixel asynchronously as a fallback to store the user id. As this is asynchronous this does not impact site performance.
Optimization: Are there specific measures or best practices you recommend for ensuring accurate and optimized tracking for SPAs? Additionally, are any changes or alterations to pixel codes necessary for SPA compatibility?
There is no optimization needed for SPAs, as we don't track the individual pages of products viewed by the end user. We do not use this tag for retargeting purpose.