---
language: "en"
---
# Kelkoo Group Help Center
*
## [For Advertisers](https://docs.kelkoogroup.com/for-advertisers.md)
* [Product data](https://docs.kelkoogroup.com/for-advertisers/product-data.md)
* [Kelkoo sales tracking](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking.md)
* [How to use your analytics platform to track Kelkoo Group traffic](https://docs.kelkoogroup.com/for-advertisers/how-to-use-your-analytics-platform-to-track-kelkoo-group-traffic.md)
* [Merchant Center](https://docs.kelkoogroup.com/for-advertisers/merchant-center.md)
* [Merchant Statistics API](https://docs.kelkoogroup.com/for-advertisers/merchant-statistics-api.md)
*
### [For Publishers](https://docs.kelkoogroup.com/for-publishers.md)
* [Quick starts](https://docs.kelkoogroup.com/for-publishers/quick-starts.md)
* [Guides](https://docs.kelkoogroup.com/for-publishers/guides.md)
* [Shopping API Search](https://docs.kelkoogroup.com/for-publishers/shopping-api-search.md)
* [Shopping API Feeds](https://docs.kelkoogroup.com/for-publishers/shopping-api-feeds.md)
* [Shopping API Changes](https://docs.kelkoogroup.com/for-publishers/shopping-api-changes.md)
* [5 more pages](https://docs.kelkoogroup.com/for-publishers.md)
---
language: "en"
---
# For Advertisers
## Getting Started with KelkooGroup
To launch your KelkooGroup campaigns, please complete the following steps:
* [Submit Your Product Feed](https://docs.kelkoogroup.com/for-advertisers/product-data/product-data-feed.md) - Provide your product catalog in the required format so we can distribute your offers across our network.
* [Install KelkooGroup Sales Tracking (KST)](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking.md) - Implement our tracking solution to enable performance-based pricing.
* [Connect Your Analytics Tool To KelkooGroup](https://docs.kelkoogroup.com/for-advertisers/how-to-use-your-analytics-platform-to-track-kelkoo-group-traffic/connect-your-analytics-tool-to-kelkoogroup.md) - This enables us to proactively compare data, understand discrepancies, and align tracking methodologies.
## Recommended Next Steps
Once your campaign is live, we recommend the following resources to optimize performance and ensure accurate tracking:
* [KelkooGroup \& GA4: A Guide for Accurate Traffic Attribution](https://docs.kelkoogroup.com/for-advertisers/how-to-use-your-analytics-platform-to-track-kelkoo-group-traffic/a-guide-for-accurate-sales-attribution-in-google-analytics-4.md) - Learn how to properly track Kelkoo traffic and purchases in Google Analytics 4, and how to interpret attribution models.
* [KelkooGroup Statistics API](https://docs.kelkoogroup.com/for-advertisers/merchant-statistics-api.md) - Programmatically access your campaign data and performance insights through our API.
---
language: "en"
---
# How to use your analytics platform to track Kelkoo Group traffic
* [Setup Tracking Parameters In Your Product Feed](https://docs.kelkoogroup.com/for-advertisers/how-to-use-your-analytics-platform-to-track-kelkoo-group-traffic/setup-tracking-parameters-in-your-product-feed.md)
* [Understanding Differences Between KelkooGroup Reported Clicks and Your Analytics Data](https://docs.kelkoogroup.com/for-advertisers/how-to-use-your-analytics-platform-to-track-kelkoo-group-traffic/understanding-differences-between-kelkoogroup-reported-clicks-and-your-analytics-data.md)
* [Connect Your Analytics Tool To KelkooGroup](https://docs.kelkoogroup.com/for-advertisers/how-to-use-your-analytics-platform-to-track-kelkoo-group-traffic/connect-your-analytics-tool-to-kelkoogroup.md)
* [A Guide for Accurate Sales Attribution in Google Analytics 4](https://docs.kelkoogroup.com/for-advertisers/how-to-use-your-analytics-platform-to-track-kelkoo-group-traffic/a-guide-for-accurate-sales-attribution-in-google-analytics-4.md)
---
language: "en"
---
# A Guide for Accurate Sales Attribution in Google Analytics 4
Data-Driven Attribution (DDA) is Google Analytics 4's (GA4) default sales tracking attribution model. Since its inclusion in GA4 in 2020, and then its application as the default model in 2023, non-Google sources of traffic in affiliation and performance marketing have reported increasing discrepancies compared to DDA's reported sales attribution.
This document aims to clarify how these attribution discrepancies occur and guide you through alternative methods for measuring sales attribution. These complementary approaches can help you gain a more complete and accurate view of your sales performance.
It's also important to note that GA4 introduced a revised definition of user sessions, which may contribute to traffic discrepancies. For more details on this topic, please refer to our guide: Understanding Differences Between KelkooGroup Reported Clicks and Your Analytics Data.
Resolving these traffic discrepancies is a critical first step toward achieving reliable and accurate conversion attribution.
## CPA Whitepaper
In early 2024, the CPA, a profession union for digital marketers based in France, released a [white paper](https://www.cpa-france.org/project/ga4-et-laffiliation-2024/) that addressed the elephant in the room. That digital marketers' and affiliate networks' contributions to retailers bottom line was under increasing pressure due to Google's own Data-Driven Attribution model; a model which saw discrepancies balloon from a maximum of 20-30% in Google's prior default attribution model (Universal Analytics), to upwards of 80% with DDA. Digital marketers exhaled a sigh of relief reading this white paper, knowing that they were not alone, and that Google, through the implementation of their attribution technology were engaging in a degree of self-preferencing that could tilt sales attribution in their favour.
Although the white paper is in French you can find an analysis of its finding in our blog article, "[Digital marketing trade association casts doubt over Google Analytics 4's attribution model](https://www.kelkoogroup.com/resources/blog/digital-marketing-trade-association-casts-doubt-over-google-analytics-4s-attribution-model/)".
## Why DDA attributes fewer sales to non-Google sources
Google Analytics has the benefit of a complete historical view on the traffic that arrives on a retailer's site. As such it is able to implement an attribution model that looks to assign complete or partial responsibility for a sale on any source.
Non-Google sources will often be reliant on "last-click channel" attribution. In a KelkooGroup context, this means that KelkooGroup will always attribute a sale to KelkooGroup if it has been a part of the user journey.
Google Analytics, on the other hand, might have the following view.
The above example shows us that at KelkooGroup we'd attribute this sale for 100 Euros to ourselves, but that GA4's DDA might actually attribute this to Facebook. The method which Google uses to determine this attribution is based on how probable a given source's inclusion in the user journey is likely to generate a sale. You can find more information on this in Google's own documentation.
This attribution model is one that is referred to as "multi-touch", and using their algorithm, Google is able to assign partial attribution to a source. For example, they may decide that in the above user journey Google is responsible for 40% of the sale, Facebook for 40% and KelkooGroup for the remaining 20%. The goal of a multi-touch attribution model is that it is designed to try and reward all sources that contribute towards a sale, regardless of when they occur in the user journey. This is very different to established models of attribution like "last-click", which favour the last source a user visited before reaching the retailer and making the sale. Last-click attribution makes the assumption that the last source a user has visited is responsible for the user making the decision to purchase and places a high value on recency.
Given how differently the above models operate, it's easy to see how discrepancies occur. But beyond the assumptions behind the DDA model, there are some design decisions that are hard to reconcile, like how DDA defines a session.
## What are scopes?
GA4 uses the concept of scopes through which to view site behaviour. Scopes are essentially different lenses through which the data can be viewed and operate within a particular hierarchy.
* **User** - the highest level which represents a visitor to your site.
* **Session** - below a user is a session which represents a group of user interactions within a given timeframe (as explained in the previous section)
* **Event** - a specific interaction or occurrence on your site that occurs within a session
The concept of scopes are important because while GA4 does offer different ways of viewing sales data other than via the default DDA model, you're only able to interrogate the last-click model at "User" or "Session" scopes. And remember, GA4's definition of sessions is still different to that of GA3's, so you will not be able to replicate GA3's UA exactly.
But why this approach with scopes at all you may ask? DDA registers sales at Event scope level. This approach is what allows DDA to be multi-touch, as an event can be associated to multiple sessions.
## Configuring GA4 for Fair Attribution
Go to `Admin > Data Display > Events > Attribution Settings`:
* **Attribution Model:** Review default (DDA) vs Last Click
* **Lookback Window:** Set appropriate window for sales (e.g. 30 days)
* **Channels that can receive credit:** Change to `Paid and Organic` to avoid Google bias
## Viewing Sales (Conversions) from Kelkoo Traffic
### Using Attribution Reports
Last-click may be the model that has persisted for over 20 years in e-commerce, but that doesn't necessarily make it the best way to view conversions. DDA clearly has weaknesses too and we've seen all sorts of models come and go in the intervening years. What's clear is that no attribution model offers a definitive view on your sales. Each attribution model is merely an interpretation of available data.
At KelkooGroup, we strongly recommend reviewing your sales performance via multiple attribution models and luckily GA4 allows you to compare DDA with last-click reasonably easily.
* Navigate to `Advertising > Attribution > Attribution models`
* Select key event: **purchase**
* Compare attribution models: **Data Driven vs Last Click**
* Filter by **Source = kelkoo**
### Digging Deeper
Seeing the details of the multi-touch model can be done quite easily, and it can help you understand how DDA is attributing sales to each of your traffic sources.
* `Advertising > Attribution > Attribution paths`: Understand how different sessions contribute to a sale
## Discrepancy analysis: A case study
As part of our efforts to understand how non-Google sales sources are represented in DDA, we took a month of data from a prominent merchant and compared the data GA4 was providing versus the sales data we were registering in our own systems.
We were able identify the following sources of the discrepancies:
* Sales not reported in GA4
* Either Kelkoo Sales Tracking of GA4 can miscount
* Sales not attributed to Kelkoo due to DDA
* Sometimes 0% attribution
* Sometimes KelkooGroup source omitted due to GA4's definition of sessions
* DDA partially attributing sales to Kelkoo
* Kelkoo Sales Tracking not registering a sales
* Kelkoo Sales Tracking not registering a partially attributed sale
* And of course, users not consenting to cookies
This analysis showed that GA4's DDA model only attributed 30% of total sales value to KelkooGroup. This is consistent with the findings of the CPA whitepaper which saw many platforms report discrepancies as high as 80%.
Of course, we acknowledge that the sales reported by Kelkoo's Sales Tracking technology is just one attempt to find the truth in these conversions, as is GA4's DDA. What this analysis does, is highlight the need to view sales reporting from more than one perspective, rather than relying on a single "source of truth".
## Summary
GA4 offers a powerful, but complex, set of tools to understand user journeys. Due to its evolving default attribution model (DDA), it can significantly underreport contributions from non-Google channels such as KelkooGroup. By properly configuring GA4 and using the correct reports, you can recover a much more accurate view of our traffic and performance.
If you need assistance implementing any of these practices or understanding your reports, reach out to your KelkooGroup account manager.
---
language: "en"
---
# Connect Your Analytics Tool To KelkooGroup
To take full advantage of KelkooGroup's smart pricing algorithms, we strongly encourage all our customers to implement KelkooGroup Sales Tracking (KST) on their website.
Additionally, we recommend **connecting your analytics platform to KelkooGroup access** (e.g. Google Analytics, Adobe Analytics). This enables us to proactively compare data, understand discrepancies, and align tracking methodologies. Transparency and alignment are in our **mutual interest** and key to maintaining a high-performing, efficient campaign.
## Connect Your Google Analytics 4 Account To KelkooGroup
* Log into your Google Analytics 4 account at
* Go to `Admin > Property > Property Access Management`
* Click "+" at the top right, then `Add users`
* Enter the email provided by your KelkooGroup account manager with viewer rights and click the "Add" button.
* Then navigate to `Admin > Property > Property Details`, find the property ID and send it to your KelkooGroup account manager to verify the connection.
Navigate to Property Access Management
Add a new user
Find your property ID
---
language: "en"
---
# Setup Tracking Parameters In Your Product Feed
## Tracking Kelkoo Group traffic
To measure the performance of your shopping campaign on Kelkoo Group using your analytics tool, we recommend implementing one of the following tracking methods within the product URLs of your feed:
* **UTM parameters** (for Google Analytics users). Example: `https://www.yourshop.com/myproductpage123.html?utm_source=kelkoofr&utm_medium=cpc&utm_campaign=kelkooclick&utm_source_platform=KelkooGroup`
* **Alternative URL parameters** supported by your analytics platform (for non-GA users)
* **Third-party tracking** (e.g. provided by a feed aggregator like Lengow)
## Setting Up Your Product Feed to Track Kelkoo Group Traffic in Google Analytics
**Ensure that your product feed URLs sent to Kelkoo Group include UTM parameters.**
If your feed complies with the Kelkoo Group Product Data Specification, UTM parameters must be added to the `product_url` and `mobile_url` attributes.
Google provides full guidance on how to configure UTM parameters here:
[Collect campaign data with custom URLs](https://support.google.com/analytics/answer/11242870?hl=en)
### Key UTM Parameters
Below are the key UTM parameters to include, along with recommended values:
| **Parameter** | **Purpose** | **Examples** |
|-----------------------|-------------------------------------------------------------------|----------------------------------------------------|
| `utm_campaign` | Identifies a specific product promotion or campaign | `utm_campaign=kelkooclick` `utm_campaign=kelkoofr` |
| `utm_medium` | Identifies the advertising medium used | `utm_medium=cpc` |
| `utm_source` | Identifies the source platform sending the traffic (**required**) | `utm_source=kelkoogroup` `utm_source=kelkoofr` |
| `utm_source_platform` | Identifies the traffic platform in multi-channel reporting | `utm_source_platform=KelkooGroup` |
### URL Examples
**Example 1: Your landing page URL already includes parameters**
* Original:
`https://www.yourshop.com/showitem?sku=123`
* Updated with UTM parameters:
`https://www.yourshop.com/showitem?sku=123&utm_source=kelkoofr&utm_medium=cpc&utm_campaign=kelkooclick&utm_source_platform=KelkooGroup`
**Example 2: Your landing page URL has no parameters**
* Original:
`https://www.yourshop.com/product123`
* Updated with UTM parameters:
`https://www.yourshop.com/product123?utm_source=kelkoofr&utm_medium=cpc&utm_campaign=kelkooclick&utm_source_platform=KelkooGroup`
### Default UTM Parameters Added by Kelkoo Group (If Missing)
If your product URLs do not include UTM parameters, Kelkoo Group will automatically append the following default values:
| **Parameter** | **Default Value** | **Notes** |
|-----------------------|-------------------|-------------------------------------------------------------------------------------------------------------|
| `utm_campaign` | `kelkoo[xx]` | `[xx]` corresponds to the 2-letter country code where your campaign is active (e.g. `kelkoofr`, `kelkoode`) |
| `utm_medium` | `cpc` | |
| `utm_source` | `kelkooclick` | |
| `utm_source_platform` | `KelkooGroup` | |
*For best results and consistent attribution, we recommend configuring UTM parameters directly in your feed.*
---
language: "en"
---
# Understanding Differences Between KelkooGroup Reported Clicks and Your Analytics Data
When comparing KelkooGroup reports (available in the KelkooGroup Merchant Center, the Merchant Statistics API or your invoices) with the data in your own analytics platform (e.g. Google Analytics), it is common to observe differences in reported numbers. These differences arise from fundamental differences in how data is collected, defined, and counted across platforms.
## Clicks vs. Sessions: Key Conceptual Difference
The core reason for discrepancies lies in the difference between **clicks** and **sessions**:
* **Click (or Lead):** Counted every time a user clicks on one of your ads displayed on KelkooGroup's network (our own sites or publisher network).
* **Session:** Counted when a user interacts with your website. For example, in Google Analytics 4, a session starts with the first interaction of a user with your site and continues until 30 minutes of inactivity. GA4 does **not** reset the session when a new source is introduced.
Because these are two distinct metrics, they should not be expected to match exactly.
## Typical Scenarios That Explain Discrepancies
Here are common scenarios that may cause differences between the number of clicks reported by KelkooGroup and the sessions recorded in your analytics tool:
### 1. Multiple Clicks, Single Session
> **Scenario:** A user clicks two of your Kelkoo ads within 30 minutes.
>
>
> **Result:**
>
> * KelkooGroup reports: **2 clicks**
>
> * Your analytics tool reports: **1 session**
### 2. Click With No Session
> **Scenario:** A user clicks a Kelkoo ad but closes the browser or navigates away before your site fully loads.
>
>
> **Result:**
>
> * KelkooGroup reports: **1 click**
>
> * Your analytics tool reports: **0 sessions**
### 3. User Refuses Cookie Consent
> **Scenario:** A user clicks a Kelkoo ad, lands on your site, but does **not consent** to cookie usage.
>
>
> **Result:**
>
> * KelkooGroup reports: **1 click**
>
> * Your analytics tool reports: **0 sessions** (no data is tracked due to lack of consent)
>
> * This scenario is particularly common in markets with strict privacy regulations (e.g. GDPR in the EU), and can significantly affect session tracking accuracy.
### 4. User Accepts Cookie Consent But Analytics Tag Not Fired
> **Scenario:** A user clicks a Kelkoo ad, lands on your site, then consent to cookie usage but the Analytics Tag is not immediately fired to activate tracking. The user navigates and lose the tracking parameters. **Result:**
>
> * KelkooGroup reports: **1 click**
>
> * Your analytics tool reports: **0 sessions**
>
> * This scenario is particularly common in markets with strict privacy regulations (e.g. GDPR in the EU), and can significantly affect session tracking accuracy.
### 5. Adblockers and Anti-Tracking Tools
> **Scenario:** A user uses an adblocker or privacy extension.
>
>
> **Result:**
>
> * KelkooGroup's click tracking is server-based and typically unaffected.
>
> * JavaScript-based analytics tools (like Google Analytics) may fail to load or track the session.
>
> * Industry estimates suggest **up to 15%** of traffic may go untracked in GA due to these tools.
### 6. Spam Detection Differences
> **Scenario A:**
>
> * 10 clicks are registered by KelkooGroup.
>
> * Kelkoo's spam filters exclude 2 as invalid.
>
> * Your analytics tool logs all 10 sessions.
>
> * **Result:** 8 clicks, 10 sessions.
> **Scenario B:**
>
> * All 10 clicks are accepted by KelkooGroup.
>
> * Your analytics tool flags 2 sessions as spam or invalid.
>
> * **Result:** 10 clicks, 8 sessions.
## What Level of Discrepancy Is Normal?
Due to the differences outlined above, a **discrepancy of 15--25%** between Kelkoo Group click counts and your analytics session data is generally expected and considered normal.
However, larger discrepancies may indicate technical issues such as:
* **Cookie Consent:**
* If users don't consent, GA4 cannot track them --- this can hide up to 50% of traffic.
* Improperly configured cookie consent banners can prevent tracking
* **Incorrect or missing tracking parameters**
* **URL redirects stripping tracking parameters**
* Server- or client-side redirects can strip UTM parameters. Use parameter-preserving redirects or propagate UTM manually.
* **Analytics tags loading too late or not firing at all**
Additionally, **Google Analytics 4's new session definition** can contribute to higher discrepancies, especially in multi-touch user journeys. See below for more details.
If you observe discrepancies exceeding 25%, we recommend reviewing your technical setup or contacting your Kelkoo account manager for personalized support.
## Understanding Differences Between KelkooGroup Reported Clicks in Google Analytics 4
### UTM parameters
UTM parameters are picked up by GA4 to identify the traffic source. Ensure that:
* `utm_source_platform` and `utm_source` are correctly passed in each Product URL of your product feed. Refer to Setup tracking parameters in your product feed.
* GA4 is properly set up to track these parameters
> **Note:** GA4 only sees these parameters if the user consents to cookies **and** the page loads with the parameters present.
### GA4 Session Definition
The way Google counts sessions with GA4 differs to GA3's Universal Analytics (UA). In GA4, a new session will only be defined if a user has been inactive for over 30 minutes. This results in significant changes as to how attribution is credited. Below is an example that shows you how sessions are delineated in GA3 versus GA4.
In the above example, a user visited your site three times: first from Google, then from Facebook, and finally, five minutes later, via KelkooGroup.
In GA3, the KelkooGroup visit would have been counted as a new session. In GA4, however, it is attributed to Facebook rather than KelkooGroup. The reasoning behind this change is unclear, but it appears to disadvantage traffic sources that may have played a more decisive role in influencing the user's purchase decision.
### Viewing Kelkoo Traffic in GA4
#### Standard but Misleading Report:
* `Reports > Acquisition > Traffic acquisition`
* Use `Session source / medium` or `Source` and filter by `kelkoo`
#### Best Report:
While it is commonplace to filter reports against `utm_source=kelkoo` in order to identify traffic coming from a KelkooGroup source, this is no longer the most accurate method available to you. There have been instances where Google has replaced the `utm_source` value from "kelkoo" to "google". This has contributed even further to observed discrepancies.
An alternative method has been identified and we highly recommend trying it.
We are now actively populating the `utm_source_platform` parameter with the value "KelkooGroup". You can access the report that shows this value in the appropriate dimension by following these steps.
* Go to `Reports > Acquisition > Overview > View manual campaigns`
* Use **Session manual source platform** dimension
* Filter for value `KelkooGroup`
**Note:** You may need to build a custom or exploration report if not available by default.
## Maximize Accuracy and Performance with Kelkoo Sales Tracking
To to take full advantage of KelkooGroup's smart pricing algorithms, we strongly encourage all our customers to implement KelkooGroup Sales Tracking (KST) on their website.
Additionally, we recommend **granting KelkooGroup access to your analytics platform** (e.g. Google Analytics, Adobe Analytics). This enables us to proactively compare data, understand discrepancies, and align tracking methodologies. Transparency and alignment are in our **mutual interest** and key to maintaining a high-performing, efficient campaign.
---
language: "en"
---
# Kelkoo sales tracking
**Kelkoo Sales Tracking (KST)** helps Kelkoo Group measure the sales generated by your campaigns and optimise the traffic we send to your website.
By providing Kelkoo Group with accurate sales data, KST enables our optimisation algorithms to identify the traffic sources, placements and offers that deliver the best performance for your business.
## Why is Kelkoo Sales Tracking important?
Kelkoo Sales Tracking records sales completed on your website and provides Kelkoo Group with the information required to measure the performance of your campaigns.
This data allows us to understand which traffic generates the most value for your business and optimise your campaigns accordingly.
For example, KST data helps our optimisation systems determine which:
* traffic sources generate valuable sales;
* placements perform best;
* products and offers should receive more or less traffic.
Accurate and complete sales tracking is therefore essential for effective campaign optimisation.
## How does Kelkoo Sales Tracking work?
KST uses two main components:
### Lead Tag
The **Lead Tag** is loaded on your website to identify visits originating from Kelkoo Group.
When the required consent has been obtained, it stores an anonymous identifier using first-party storage. This identifier allows KST to recognise a Kelkoo visit if the user subsequently completes a purchase.
### Conversion Tag
The **Conversion Tag** fires when an order is completed and sends information about the transaction to Kelkoo Group.
This includes information such as:
* the order ID;
* the order value;
* the Kelkoo identifier, when available;
* additional transaction information, depending on your implementation.
The Conversion Tag should fire for **every completed order**. Kelkoo Group then determines whether the transaction should be attributed to Kelkoo traffic.
> **Important**
>
> KST should track every sale completed on your website, not only sales that you believe were generated by Kelkoo Group.
>
> Kelkoo Group applies its own attribution logic to determine which sales should be attributed to Kelkoo traffic. Missing or modified sales data can affect our ability to accurately measure and optimise your campaign performance.
> **Kelkoo Group and Google Analytics attribution**
>
> Kelkoo Group uses its own attribution methodology. As a result, the number of sales attributed to Kelkoo Group may differ from the figures reported by Google Analytics or other analytics platforms.
>
> See [How to use your analytics platform to track Kelkoo Group traffic](https://docs.kelkoogroup.com/for-advertisers/how-to-use-your-analytics-platform-to-track-kelkoo-group-traffic/understanding-differences-between-kelkoogroup-reported-clicks-and-your-analytics-data.md) for more information.
For a more detailed explanation, see [Understanding Kelkoo Sales Tracking](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/understanding-kelkoo-sales-tracking.md).
## Privacy and consent
Kelkoo Sales Tracking has been designed to minimise the amount of data collected and to respect applicable privacy requirements.
### Lead Tag
The Lead Tag requires the appropriate user consent before setting first-party cookies or using equivalent browser storage.
Users are identified using an anonymous identifier.
### Conversion Tag
The Conversion Tag does not require separate user consent. Kelkoo Group relies on **legitimate interest** as the legal basis for processing the sales data required to measure and optimise campaign performance.
Kelkoo Group only uses sales data relevant to the measurement and optimisation of Kelkoo Group campaigns and does not collect information that directly identifies individual customers.
For complete information about data processing, cookies and your responsibilities as an advertiser, see:
* [GDPR Notice for Kelkoo Sales Tracking](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/gdpr-notice-for-kelkoo-sales-tracking.md)
* [Kelkoo Group Privacy Policy](https://www.kelkoogroup.com/en/privacy-policy/)
* [Kelkoo Group Cookie Policy](https://www.kelkoogroup.com/en/cookie-policy/)
## How should I install Kelkoo Sales Tracking?
For the most accurate tracking, we recommend implementing both:
* [Google Tag Manager (GTM) tracking](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-via-google-tag-manager-gtm-with-enhanced-ecommerce.md)
* [Server-to-server integration](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/advanced-setup/server-to-server-integration.md)
When possible, these methods should run in parallel to maximise tracking coverage and accuracy.
Other installation methods are also available for websites using specific ecommerce platforms or custom technical setups.
See [Installation Methods](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods.md) to choose the most appropriate implementation for your website.
## Need help?
Our documentation covers the most common installation methods and [troubleshooting scenarios](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/troubleshooting.md).
If you are unable to resolve an issue after reviewing the installation and troubleshooting guides, contact the **Kelkoo Group Support team through** [**your Merchant Center**](https://merchant.kelkoogroup.com/app/contact).
> **Note**
>
> Technical support is currently provided in English only.
---
language: "en"
---
# GDPR Notice for Kelkoo Sales Tracking
Kelkoo Sales Tracking uses first-party cookies (in line with industry standards) which are set on your own domain.
In respect of Kelkoo Group traffic sourced from Google, Kelkoo Sales Tracking also calls a Google Global Site Tag to track conversions. The Google Global Site Tag uses cookies to identify unique users.
If you are using Kelkoo Sales Tracking, we suggest that you include the following information (or equivalent) in your cookie policy to notify users.
## 1st party cookie information
| name | Role | domain name | Duration | Comment |
|------------|-------------|-------------|-----------|------------------------------------------------------------------------------------|
| kelkooId | Measurement | your domain | 12 months | The kelkooid is used to mesure the performance of the Kelkoo ad campaigns |
| kk_gclid | Measurement | your domain | 12 months | The kk_gclid is used to mesure the performance of the Kelkoo Group ad campaigns |
| kk_leadtag | Technical | your domain | 12 months | The kk_leadtag is used to determine the version of the tracking tool that is used. |
More information can be found at . Please also refer to Google´s cookie policy: .
## Other information regarding data and processing
| Info | Description |
|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Technology partner | Kelkoo Group |
| Data Host | Kelkoo Group |
| Country of data storage | The Netherlands |
| Period of data storage | Raw data with timestamp: * Clicks, tracking points and events: Indefinite * Impressions: 30 days * Aggregated data: Indefinite |
| List of processed and stored data | * User ID * Time of Interaction * URL of Interaction * IP address * Location data * User agent data * Sales transaction data * Transaction details (if supplied by merchant) |
| Description of processed and stored data | Transaction details stored are defined by merchant integration and can include Product Ids, basket value, product names etc |
| Goal/Objective of data storage | Report sales conversion for Kelkoo Group traffic to optimize campaigns. |
| Used technologies | HTML, JavaScript, Cookie |
| Fallback technologies | * Local Storage * Session Storage * Third-party cookies |
| Cookie domain | Merchant domain name (for first party cookies) / [Kelkoogroup.net](http://kelkoogroup.net/) (for third-party cookies) |
| Integration on which pages | * LeadTag: all pages * ConversionTag: "Thank you page" / Confirmation page |
| Integration type | Asynchronous JavaScript Tag |
Data collected as part of Kelkoo Sales Tracking is processed by Kelkoo Group on its own behalf and Kelkoo Group is responsible as the data controller for the purposes of GDPR.
This is independent of any similar data which may be collected by you on your own behalf (or through other partners you work with), in respect of which you (or your partners) remain data controllers.
There is no controller-processor relationship between Kelkoo Group and You.
If you have any questions, please do not hesitate to contact your usual contact at Kelkoo Group, or Kelkoo Group's Data Protection Officer at [dpo@kelkoogroup.com](mailto:dpo@kelkoogroup.com).
---
language: "en"
---
# Installation Methods
There are several ways to install **Kelkoo Sales Tracking (KST)**. The best method depends on your website, ecommerce platform, technical setup, and available development resources.
Use the table below to choose the installation method that best suits your setup.
## Choose your installation method
| Method | Recommended for | Technical requirements | Installation guide |
|--------------------------------|-----------------------------------------------------------------------|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Google Tag Manager (GTM)** | Websites using GTM with Enhanced Ecommerce | Good understanding of Google Tag Manager | [GTM Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-via-google-tag-manager-gtm-with-enhanced-ecommerce.md) |
| **Manual integration** | Any website where KST can be integrated directly into the source code | Development skills required | [Manual Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/manual-installation-for-kelkoo-sales-tracking.md) |
| **Magento 1 \& 2** | Magento stores | Development skills required | [Magento 1 \& 2 Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/magento.md) |
| **PrestaShop 1.6 and earlier** | PrestaShop stores running version 1.6 or earlier | Development skills required | [PrestaShop 1.6 and Older Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/prestashop-1-6x.md) |
| **PrestaShop 1.7** | PrestaShop stores running version 1.7 | Development skills required | [PrestaShop 1.7 Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/prestashop-1-7x.md) |
| **PrestaShop 8** | PrestaShop stores running version 8 | Development skills required | [PrestaShop 8 Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/prestashop-8.md) |
| **Shopify / Shopify Plus** | Shopify and Shopify Plus stores | Manual integration | [Shopify / Shopify Plus Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/shopify-shopify-plus.md) |
| **WooCommerce** | WooCommerce stores | Plugin -- simple installation | [WooCommerce Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/woocommerce.md) |
| **Unas Ecommerce** | Unas stores | Plugin -- simple installation | [Unas Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/unas-ecommerce.md) |
| **Lightspeed C-Series** | Lightspeed C-Series stores | Manual integration | [Lightspeed C-Series Installation Guide](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/lightspeed-c-series.md) |
| **Server-to-server** | Custom implementations where browser-based tracking is not suitable | Advanced development skills required | [Server-to-Server Integration](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/advanced-setup/server-to-server-integration.md) |
> **Multi-campaign support**
>
> All installation methods support multi-campaign tracking.
> **Not sure which method to use?**
>
> If your website uses Google Tag Manager with Enhanced Ecommerce, we recommend the **GTM installation method**.
>
> If GTM is not available and there is no dedicated integration for your ecommerce platform, use the **manual installation method**.
## Test your installation
After installing Kelkoo Sales Tracking, we strongly recommend testing your implementation before considering the setup complete.
See [Test your Kelkoo Sales Tracking setup](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/test-your-kelkoo-sales-tracking-setup.md) for detailed instructions.
## Advanced setup
Once Kelkoo Sales Tracking is installed, additional configuration options are available for more advanced implementations.
These include:
* [Adding basket information](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/advanced-setup/add-basket-information.md) -- Share information about the products included in each transaction with Kelkoo Sales Tracking.
* [Reimplementing the Lead Tag logic](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/advanced-setup/lead-tag-reimplementation.md) -- Implement the Lead Tag functionality yourself when the standard implementation is not suitable.
* [Server-to-server integration](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/advanced-setup/server-to-server-integration.md) -- Implement sales tracking without relying entirely on browser-side tracking.
## Performance impact
Kelkoo Sales Tracking is designed to have minimal impact on your website's performance.
The tracking scripts and requests run asynchronously, allowing the rest of the page to load independently.
Typical timings are:
* Approximately 100 ms to download the Lead Tag (2.9 kB compressed). The download is asynchronous and does not block the page from displaying.
* Approximately 22 ms to download the Sales Tracking tag (3.9 kB compressed).
* Approximately 180 ms for the request to the Kelkoo Sales Tracking service. This request is performed in the background and does not block the user experience.
We recommend loading the script using `defer` where applicable to further minimise its impact on page loading.
---
language: "en"
---
# Advanced Setup
* [Add Basket Information](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/advanced-setup/add-basket-information.md)
* [Lead Tag Reimplementation](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/advanced-setup/lead-tag-reimplementation.md)
* [Server to server integration](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/advanced-setup/server-to-server-integration.md)
---
language: "en"
---
# Add Basket Information
You can enrich your Kelkoo Sales Tracking (KST) implementation by sending information about the products included in each transaction.
Basket information helps Kelkoo Group better understand which products generate sales and enables additional performance optimisations.
The implementation depends on how you installed Kelkoo Sales Tracking.
## Manual installation
If you installed KST manually, add a `basket` parameter to the `_kkstrack` variable on your order confirmation page.
The `basket` parameter must contain an array of all products included in the transaction:
JavaScript
_kkstrack = {
...
basket: [{ productname: 'Man@@ubri ricoperti di spugna 1 kg x 2 pz ',
productid: '1',
quantity: '1',
price: '4.2'
},
{ productname: 'p2',
productid: '2',
quantity: '3',
price: '8.6'
},
...
]
...
};
All four fields are required for each product:
| Field | Description |
|---------------|----------------------------------|
| `productname` | Name of the product |
| `productid` | Unique identifier of the product |
| `quantity` | Number of units purchased |
| `price` | Unit price of the product |
> **Important**
>
> The `productid` should match the product identifier used in your Kelkoo Group offer feed, such as the EAN, SKU or another unique product ID.
>
> Using the same identifier allows Kelkoo Group to match transactions with the corresponding products in your feed and enables additional performance optimisations.
## Installation via Google Tag Manager (GTM)
If you installed KST through Google Tag Manager, your Data Layer must contain information about the products included in the transaction.
JavaScript
window.dataLayer = window.dataLayer || [];
dataLayer.push({
'transactionId':'1234',
'transactionAffiliation':'Acme Clothing',
'transactionTotal':38.26,
'transactionTax':1.29,
'transactionShipping':5,
'transactionProducts':[{
'sku':'DD44',
'name':'T-Shirt',
'category':'Apparel',
'price':11.99,
'quantity':1},
{
'sku':'AA345',
'name':'Boots',
'category':'Shoes',
'price':99.99,
'quantity':4
}]
})
Make sure the product information required by your KST configuration is available in the Data Layer.
> **Important**
>
> The `sku` should match the product identifier used in your Kelkoo Group offer feed, such as the EAN, SKU or another unique product ID.
>
> Using consistent identifiers allows Kelkoo Group to match purchased products with the corresponding products in your feed and enables additional performance optimisations.
## Pass the product ID / SKU to Kelkoo Sales Tracking
* For an installation via Google Tag Manager (GTM), add SKU in the GTM tag
* For a Manual Installation, add SKU to js variable *_kkltrack* (_kkltrack.sku)
* If you already follow Google requirements regarding structured product metada ( ), Kelkoo Sales Tracking will retrieve them automatically
Ex:
* Kelkoo Sales Tracking also supports Google Analytics baskets
[
{
"id": "P12345",
"name": "Android Warhol T-Shirt",
"list_name": "Search Results",
"brand": "Google",
"category": "Apparel/T-Shirts",
"variant": "Black",
"list_position": 1,
"quantity": 2,
"price": '2.0'
},
{
"id": "P67890",
"name": "Flame challenge TShirt",
"list_name": "Search Results",
"brand": "MyBrand",
"category": "Apparel/T-Shirts",
"variant": "Red",
"list_position": 2,
"quantity": 1,
"price": '3.0'
}
]
---
language: "en"
---
# Lead Tag Reimplementation
This guide is intended for merchants who cannot use the standard Kelkoo Group `leadtag.js` script and need to reproduce its essential functionality in their own implementation.
For most integrations, we recommend using the standard **Kelkoo Lead Tag**. Only use the approach described below if you have a specific technical requirement to implement the Lead Tag logic yourself.
## Minimal implementation of lead tag
This is the minimal mechanism you need to implement
JavaScript
KELKOO.Tracking._getUrlParamValue = function (name) {
var bareUrlRegex = new RegExp("[\\?&]" + name + "=([\\w\\-]+)", "gi");
var result = bareUrlRegex.exec(document.location.search);
var activeObserveHandle = null;
if (result) {
activeObserveHandle = result[1];
}
return activeObserveHandle;
};
KELKOO.Tracking.setCookieAndStorage = function (name, value) {
var d = new Date;
d.setTime(d.getTime() + 365 * 24 * 60 * 60 * 1E3);
document.cookie = name + "=" + value + "; expires=" + d.toGMTString() + "; path=/; domain=acme.com; SameSite=Strict";
sessionStorage.setItem(name, value);
localStorage.setItem(name, value);
};
var kk = KELKOO.Tracking._getUrlParamValue("kk");
KELKOO.Tracking.setCookieAndStorage("kelkooId", kk);
var gclid = KELKOO.Tracking._getUrlParamValue("gclid");
KELKOO.Tracking.setCookieAndStorage("kk_gclid", gclid);
## The `kk` parameter and `kelkooId`
The `kk` URL parameter is automatically added by Kelkoo Group when a user clicks one of your ads.
Your Lead Tag implementation retrieves the value of `kk` and stores it as `kelkooId`
---
language: "en"
---
# Server to server integration
## Important
* Installation via Google Tag Manager (GTM) or Manual installation is the official implementation (see Installation Methods).
* This Server-to-Server implementation is only intended as a fallback method to increase tracking coverage.
* It is only available if you have an in-house development team managing. It is not suitable for agency/third party or if you don't have a technical team.
* We don't provide custom implementation and a very limited technical support for this implementation.
* You need to track inbound traffic directly from Kelkoo Group Network, as well as parallel tracking calls when the url contains gclid id from Google
* You need to make sure all sales are tracked, in-session as well as those made on a different session than the initial click.
### Global view
* End user browses Kelkoo Group websites, when clicking an offer on Kelkoo Group Network, he is redirected to the merchant website.
* KelkooId (*kk* ) and Google Click Id (*gclid*) is passed as parameters of the url
*ex:* [*https://www.acme.com/miror/137-miror.html?\*\*kk=a4csscc-1781b717420-34cf3\*\*\&\*\*gclid=EAIaIQobChMIpNXu6r6D6AIVQsjeCh27SQXcEAkYAyABEgIhz_D_BwE\*\*\&utm_source=kelkoofr\&utm_medium=cpc\&utm_campaign=kelkooclick*](https://www.acme.com/miror/137-miror.html?**kk=a4csscc-1781b717420-34cf3**&**gclid=EAIaIQobChMIpNXu6r6D6AIVQsjeCh27SQXcEAkYAyABEgIhz_D_BwE**&utm_source=kelkoofr&utm_medium=cpc&utm_campaign=kelkooclick)
* When the user reaches one of your Product page, your website stores *kk* and *gclid* id in a table on your website's backend, and associate it to the current user via the login/basket
| basket | login | kk | gclid |
|------------------|---------|---------------------------|---------------------------------------------------------|
| 17e8b1bxx7r17420 | 1233443 | a4csscc-1781b717420-34cf3 | EAIaIQobChMIpNXu6r6D6AIVQsjeCh27SQXcEAkYAyABEgIhz_D_BwE |
| ... | ... | ... | ... |
* When the user buys the product and reaches your Confirmation Page, your Website retrieves *kk* and *gclid* params value from database and calls the *Kelkoo Group Sales Tracking Webservice* on for each sale with an HTTP GET with the following parameters:
| name | type | mandatory | description | example |
|---------------|---------|-----------|----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| country | String | true | The 2-letter country code for the country on which your products are listed on Kelkoo Group: | fr |
| orderId | String | true | A unique order identifier | FAPC-MZL8-QFNY |
| comId | Long | true | The unique ID representing your shop within the Kelkoo Group system | 100503562 |
| orderValue | Double | true | The total amount of the order | 37.72 |
| productsInfos | String | true | A UrlEncoded Base64 of a Json Array of the products in the basket. | W3sicHJvZHVjdG5hbWUiOiJTaGltYW5vIiwiaWQiOiJwcm9kMTMwODIzIiwicHJpY2UiOjE0Ljk5LCJxdWFudGl0eSI6Mn1d `[{"productname":"Shimano","productid":"prod130823","price":14.99,"quantity":2}]` |
| saleId | Double | true | A randomly generated number between 0 and 1 | 0.24603935101497432 |
| kelkooId | String | false | The value of the kk parameter in the url of your landing page | a4c6224-1700767fb9f-c3de3 |
| gclid | String | false | The value of the gclid parameter in the url of your landing page | EAIaIQobChMIpNXu6r6D6AIVQsjeCh27SQXcEAkYAyABEgIhz_D_BwE |
| msclkid | String | false | The value of the msclkid parameter in the url of your landing page | 751ff8c7d3bf17f6f6729c640c4249d5 |
| returningUser | Boolean | false | "true" if the sale is done by a returning user, "false" for a new user | true |
| source | String | false | Set this param value to "serverToServer" | serverToServer |
Here is an example of decoded and pretty-printed `productsInfos`:
[
{
"productname": "Shimano", // string
"productid": "prod130823", // string
"price": 14.99, // double
"quantity": 2 // integer, floating number is not allowed here
}
]
### GDPR considerations
Consent needs to be managed directly by merchants as this is not part of the traditional cookie consent mechanism. See GDPR Notice for Kelkoo Sales Tracking.
## What exactly do you need to implement ?
*Workload: estimated to 5 days minimum of development for an experimented developer*
* Add parameters into the merchant landing page urls if you use an external tracking service (such as Lengow). For example, Lengow short urls are not compatible.
* Store kelkooId / Google Click Id in database whenever a page is visited and associate it with the current user with login and basket
* In order to add the domain, for best practice, add in the request header of the call : "Referer: [https://yourwebsite.com](https://yourwebsite.com/)"
* Retrieve the KelkooId and Google Click Id from the database when Confirmation Page is displayed, and call the Kelkoo Sales Tracking Webservice
*example of a call:* [*https://s.kelkoogroup.net/st?country=fr\&orderId=CMD0572084\&comId=100475501\&orderValue=609.07\&productsInfos=W3sicHJvZHVjdG5hbWUiOiJCb2l0ZSBkZSAxMDAwIGxhbWVsbGVzIGVuIGJvaXMgTGFtZWxsbyBlbiAyMCIsInByb2R1Y3RpZCI6IlAxNDA0OTAiLCJwcmljZSI6MzAuNTAsInF1YW50aXR5IjoxfSx7InByb2R1Y3RuYW1lIjoiQm9pdGUgZGUgMTAwMCBsYW1lbGxlcyBlbiBib2lzIExhbWVsbG8gZW4gMTAiLCJwcm9kdWN0aWQiOiJQMTQwNDkxIiwicHJpY2UiOjI5LjI1LCJxdWFudGl0eSI6MX0seyJwcm9kdWN0bmFtZSI6IkNvbGxlIHZpbnlsaXF1ZSBSIDY0IHByaXNlIGxlbnRlIHNww6ljaWFsZSBtZW51aXNlcmllIGVuIGJpYmVyb24gZGUgMC43NSBrZ3MiLCJwcm9kdWN0aWQiOiJQMTM3NzI4IiwicHJpY2UiOjEwLjkxLCJxdWFudGl0eSI6MX0seyJwcm9kdWN0bmFtZSI6IlNlcnJlIGpvaW50cyDDqWNhcnRldXIgUXVpY2sgR3JpcCAzMDAgbW0iLCJwcm9kdWN0aWQiOiJQMTA4NTMwIiwicHJpY2UiOjE4LjcwLCJxdWFudGl0eSI6Mn0seyJwcm9kdWN0bmFtZSI6IlNlcnJlIGpvaW50IMOgIHBvbXBlIE9icmEgc2FpbGxpZSAxMjAgbW0gc2VycmFnZSBtYXhpIDEwMDAgbW0iLCJwcm9kdWN0aWQiOiJQMjMwODE0IiwicHJpY2UiOjI1LjI2LCJxdWFudGl0eSI6Mn1d\&saleId=0.193286593627784\&kelkooId=66b5837-16afefa0c40-1b540\&source=serverToServer*](https://s.kelkoogroup.net/st?country=fr&orderId=CMD0572084&comId=100475501&orderValue=609.07&productsInfos=W3sicHJvZHVjdG5hbWUiOiJCb2l0ZSBkZSAxMDAwIGxhbWVsbGVzIGVuIGJvaXMgTGFtZWxsbyBlbiAyMCIsInByb2R1Y3RpZCI6IlAxNDA0OTAiLCJwcmljZSI6MzAuNTAsInF1YW50aXR5IjoxfSx7InByb2R1Y3RuYW1lIjoiQm9pdGUgZGUgMTAwMCBsYW1lbGxlcyBlbiBib2lzIExhbWVsbG8gZW4gMTAiLCJwcm9kdWN0aWQiOiJQMTQwNDkxIiwicHJpY2UiOjI5LjI1LCJxdWFudGl0eSI6MX0seyJwcm9kdWN0bmFtZSI6IkNvbGxlIHZpbnlsaXF1ZSBSIDY0IHByaXNlIGxlbnRlIHNww6ljaWFsZSBtZW51aXNlcmllIGVuIGJpYmVyb24gZGUgMC43NSBrZ3MiLCJwcm9kdWN0aWQiOiJQMTM3NzI4IiwicHJpY2UiOjEwLjkxLCJxdWFudGl0eSI6MX0seyJwcm9kdWN0bmFtZSI6IlNlcnJlIGpvaW50cyDDqWNhcnRldXIgUXVpY2sgR3JpcCAzMDAgbW0iLCJwcm9kdWN0aWQiOiJQMTA4NTMwIiwicHJpY2UiOjE4LjcwLCJxdWFudGl0eSI6Mn0seyJwcm9kdWN0bmFtZSI6IlNlcnJlIGpvaW50IMOgIHBvbXBlIE9icmEgc2FpbGxpZSAxMjAgbW0gc2VycmFnZSBtYXhpIDEwMDAgbW0iLCJwcm9kdWN0aWQiOiJQMjMwODE0IiwicHJpY2UiOjI1LjI2LCJxdWFudGl0eSI6Mn1d&saleId=0.193286593627784&kelkooId=66b5837-16afefa0c40-1b540&source=serverToServer)
* Implement Consent management. See GDPR Notice for Kelkoo Sales Tracking.
### Enhanced Code Implementation:
#### Languages
1. [PHP](https://developers.kelkoogroup.com/#php-version-550-or-higher)
2. [Java](https://developers.kelkoogroup.com/#java-version-8)
3. [Python](https://developers.kelkoogroup.com/#java-version-8)
4. [Node.js](https://developers.kelkoogroup.com/#nodejs-version-20x)
#### PHP (Version 5.5.0 or higher)
* The following example shows you how to store tracking click ID (kelkooId / Google Click Id / Microsoft Click ID) in the database whenever a page is visited and associate it with the current user upon login and during basket interactions.
* The following example illustrates how to retrieve the Tracking click ID (KelkooId, Google Click ID, or Microsoft Click ID) from the database when the Confirmation Page is displayed, and then call the Kelkoo Sales Tracking Webservice with your domain specified in the request header.
$country,
'orderId' => $orderId,
'comId' => $comId,
'orderValue' => $orderValue,
'productsInfos' => $productsInfos,
'saleId' => $saleId,
'kelkooId' => $kelkooId,
'gclid' => $gclid,
'msclkid' => $msclkid
);
// Append data to URL
$url .= '?' . http_build_query($data);
// Initialize cURL session
$curl = curl_init();
// Set the URL
curl_setopt($curl, CURLOPT_URL, $url);
// Set request header
curl_setopt($curl, CURLOPT_HTTPHEADER, array(
'Referer: https://yourwebsite.com'
));
// Set request method to GET
curl_setopt($curl, CURLOPT_HTTPGET, true);
// Execute the request
$response = curl_exec($curl);
// Close cURL session
curl_close($curl);
// Process response as needed
}
// Assuming you have retrieved the user ID from the session or other means
$userId = $_SESSION['user_id'];
// Your Kelkoo group information - Static values
$country = 'fr';
$comId = 100475501;
// Order information - dynamic values to retrieve from the order information
$orderId='CMD0572084';
$orderValue=609.07;
$basket = array(
array(
'productname' => 'Shimano',
'productid' => 'prod130823',
'price' => 14.99,
'quantity' => 2
)
);
// Retrieve KelkooId, Google Click Id, Microsoft click ID from the database
$ids = getIdsFromDatabase($userId);
if ($ids['kelkoo_id'] || $ids['google_click_id'] || $ids['ms_clk_id']) {
// Call Kelkoo Sales Tracking Webservice
callKelkooSalesTracking($country, $comId, $orderId, $orderValue, encodeBasket($basket), generateSaleId(), $ids['kelkoo_id'], $ids['google_click_id'], $ids['ms_clk_id']);
}
?>
#### Java (Version 8)
* The following example shows you how to store tracking click ID (kelkooId / Google Click Id / Microsoft Click ID) in the database whenever a page is visited and associate it with the current user upon login and during basket interactions.
import javax.servlet.*;
import javax.servlet.annotation.WebFilter;
import java.io.IOException;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.SQLException;
@WebFilter("/*")
public class TrackingFilter implements Filter {
@Override
public void init(FilterConfig filterConfig) throws ServletException {
// Initialization code if needed
}
@Override
public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
HttpServletRequest httpRequest = (HttpServletRequest) request;
String kelkooId = httpRequest.getParameter("kk");
String googleClickId = httpRequest.getParameter("gclid");
String msclkid = httpRequest.getParameter("msclkid");
HttpSession session = httpRequest.getSession();
String userId = (String) session.getAttribute("user_id");
if (kelkooId != null || googleClickId != null || msclkid != null) {
storeIdsInDatabase(userId, kelkooId, googleClickId, msclkid);
}
chain.doFilter(request, response);
}
@Override
public void destroy() {
// Cleanup code if needed
}
// Function to store kelkooId / Google Click Id / Microsoft Click ID in the database
private void storeIdsInDatabase(String userId, String kelkooId, String googleClickId, String msclkid) {
// Database connection parameters
String url = "jdbc:mysql://localhost:3306/your_database";
String user = "username";
String password = "password";
try (Connection connection = DriverManager.getConnection(url, user, password)) {
String query = "INSERT INTO user_tracking (user_id, kelkoo_id, google_click_id, ms_clk_id) VALUES (?, ?, ?, ?)";
try (PreparedStatement preparedStatement = connection.prepareStatement(query)) {
preparedStatement.setString(1, userId);
preparedStatement.setString(2, kelkooId);
preparedStatement.setString(3, googleClickId);
preparedStatement.setString(4, msclkid);
preparedStatement.executeUpdate();
}
} catch (SQLException e) {
e.printStackTrace();
}
}
}
* The following example illustrates how to retrieve the Tracking click ID (KelkooId, Google Click ID, or Microsoft Click ID) from the database when the Confirmation Page is displayed, and then call the Kelkoo Sales Tracking Webservice with your domain specified in the request header.
import java.io.IOException;
import java.io.OutputStreamWriter;
import java.net.HttpURLConnection;
import java.net.URL;
import java.nio.charset.StandardCharsets;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.HashMap;
import java.util.Map;
import com.google.gson.Gson;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
@WebServlet("/confirmation")
public class ConfirmationPageServlet extends HttpServlet {
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
// Retrieve user ID from session or other means
String userId = "user123"; // Replace with actual user ID
// Your Kelkoo group information - Static values
String country = "fr";
int comId = 100475501;
// Order information - dynamic values to retrieve from the order information
String orderId = "CMD0572084";
double orderValue = 609.07;
Map basket = new HashMap<>();
basket.put("productname", "Shimano");
basket.put("productid", "prod130823");
basket.put("price", 14.99);
basket.put("quantity", 2);
// Retrieve KelkooId, Google Click Id, Microsoft click ID from the database
String[] ids = getIdsFromDatabase(userId);
String kelkooId = ids[0];
String googleClickId = ids[1];
String msclkid = ids[2];
if (kelkooId != null || googleClickId != null || msclkid != null) {
// Call Kelkoo Sales Tracking Webservice
callKelkooSalesTracking(country, comId, orderId, orderValue, basket, kelkooId, googleClickId, msclkid);
}
response.getWriter().println("Confirmation Page Displayed");
}
// Function to retrieve KelkooId, Google Click Id and Microsoft Click ID from the database
private String[] getIdsFromDatabase(String userId) {
String[] ids = new String[3]; // Array to store kelkooId, googleClickId, msclkid
// Database connection parameters
String url = "jdbc:mysql://localhost:3306/your_database";
String user = "username";
String password = "password";
try (Connection connection = DriverManager.getConnection(url, user, password)) {
// Replace query to retrieve data from the database
String query = "SELECT kelkoo_id, google_click_id, ms_clk_id FROM user_tracking WHERE user_id = ?";
try (PreparedStatement preparedStatement = connection.prepareStatement(query)) {
preparedStatement.setString(1, userId);
try (ResultSet resultSet = preparedStatement.executeQuery()) {
if (resultSet.next()) {
ids[0] = resultSet.getString("kelkoo_id");
ids[1] = resultSet.getString("google_click_id");
ids[2] = resultSet.getString("ms_clk_id");
}
}
}
} catch (SQLException e) {
// Exception management
}
return ids;
}
// Function to call Kelkoo Sales Tracking Webservice
private void callKelkooSalesTracking(String country, int comId, String orderId, double orderValue, Map basket,
String kelkooId, String googleClickId, String msclkid) throws IOException {
// URL of the Kelkoo Sales Tracking Webservice
String urlString = "https://s.kelkoogroup.net/st";
// Data to be sent in the request
Map data = new HashMap<>();
data.put("country", country);
data.put("orderId", orderId);
data.put("comId", comId);
data.put("orderValue", orderValue);
data.put("productsInfos", basket);
data.put("saleId", generateSaleId());
data.put("kelkooId", kelkooId);
data.put("gclid", googleClickId);
data.put("msclkid", msclkid);
// Convert data to JSON
Gson gson = new Gson();
String jsonData = gson.toJson(data);
// Create connection
URL url = new URL(urlString);
HttpURLConnection connection = (HttpURLConnection) url.openConnection();
connection.setRequestMethod("POST");
connection.setRequestProperty("Referer", "https://yourwebsite.com");
connection.setRequestProperty("Content-Type", "application/json");
connection.setDoOutput(true);
// Write data to the connection
try (OutputStreamWriter writer = new OutputStreamWriter(connection.getOutputStream(), StandardCharsets.UTF_8)) {
writer.write(jsonData);
writer.flush();
}
// Get response
int responseCode = connection.getResponseCode();
if (responseCode == HttpURLConnection.HTTP_OK) {
// Process response as needed
System.out.println("Kelkoo Sales Tracking Webservice called successfully.");
} else {
System.out.println("Failed to call Kelkoo Sales Tracking Webservice. Response code: " + responseCode);
}
// Close connection
connection.disconnect();
}
// Function to generate randomly number between 0 and 1
private double generateSaleId() {
return Math.random();
}
}
#### Python (Version 3.x)
* The following example shows you how to store tracking click ID (kelkooId / Google Click Id / Microsoft Click ID) in the database whenever a page is visited and associate it with the current user upon login and during basket interactions.
import urllib.parse
import http.server
import socketserver
import mysql.connector
# Function to store kelkooId / Google Click Id / Microsoft click ID in the database
def store_ids_in_database(user_id, kelkoo_id, google_click_id, msclkid):
# Connect to the database
connection = mysql.connector.connect(
host='localhost',
user='username',
password='password',
database='your_database'
)
try:
cursor = connection.cursor()
# Replace query to store data in the database
sql = "REPLACE INTO user_tracking (user_id, kelkoo_id, google_click_id, ms_clk_id) VALUES (%s, %s, %s, %s)"
cursor.execute(sql, (user_id, kelkoo_id, google_click_id, msclkid))
# Commit changes
connection.commit()
finally:
cursor.close()
connection.close()
# Function to extract parameters from URL
def extract_params_from_url(url):
query = urllib.parse.urlparse(url).query
params = urllib.parse.parse_qs(query)
return params
class RequestHandler(http.server.SimpleHTTPRequestHandler):
def do_GET(self):
# Extract parameters from URL
params = extract_params_from_url(self.path)
# Extract kelkooId, googleClickId and msclkid from parameters
kelkoo_id = params.get('kk', [None])[0]
google_click_id = params.get('gclid', [None])[0]
msclkid = params.get('msclkid', [None])[0]
# Assuming you also retrieve the user ID from your session or other means
user_id = "user123"
# Call the function to store IDs in the database if either kelkooId or googleClickId is not None
if kelkoo_id is not None or google_click_id is not None or msclkid is not None:
store_ids_in_database(user_id, kelkoo_id, google_click_id, msclkid)
# Send response
self.send_response(200)
self.end_headers()
self.wfile.write(b'Data stored successfully!')
# Assuming your server runs on port 8000
with socketserver.TCPServer(("", 8000), RequestHandler) as httpd:
print("Server started on port 8000...")
httpd.serve_forever()
* The following example illustrates how to retrieve the Tracking click ID (KelkooId, Google Click ID, or Microsoft Click ID) from the database when the Confirmation Page is displayed, and then call the Kelkoo Sales Tracking Webservice with your domain specified in the request header.
import json
import random
import urllib.parse
import urllib.request
import mysql.connector
# Function to retrieve KelkooId, Google Click Id and Microsoft Click ID from the database
def get_ids_from_database(user_id):
# Connect to the database
connection = mysql.connector.connect(
host='your_host',
user='your_user',
password='your_password',
database='your_database'
)
# Create a cursor object
cursor = connection.cursor()
try:
# Sanitize input to prevent SQL injection
user_id = cursor.escape_string(user_id)
# Select query to retrieve data from the database
query = "SELECT kelkoo_id, google_click_id, ms_clk_id FROM user_tracking WHERE user_id = '%s'" % user_id
# Execute query
cursor.execute(query)
# Fetch data
row = cursor.fetchone()
# Return KelkooId, Google Click Id and Microsoft Click ID
return row
finally:
# Close cursor and connection
cursor.close()
connection.close()
# Function for custom base64 encoding without padding
def custom_base64_encode(data):
return urllib.parse.quote_plus(data)
# Function to encode basket items
def encode_basket(products_array):
# Convert the Python array to JSON
json_data = json.dumps(products_array)
# Encode the JSON in base64 without padding
base64_data = custom_base64_encode(json_data)
return base64_data
# Function to generate randomly number between 0 and 1
def generate_sale_id():
return random.random()
# Function to call Kelkoo Sales Tracking Webservice
def call_kelkoo_sales_tracking(country, com_id, order_id, order_value, products_infos, sale_id, kelkoo_id, gclid, msclkid):
# URL of the Kelkoo Sales Tracking Webservice
url = 'https://s.kelkoogroup.net/st'
# Data to be sent in the request
data = {
'country': country,
'orderId': order_id,
'comId': com_id,
'orderValue': order_value,
'productsInfos': products_infos,
'saleId': sale_id,
'kelkooId': kelkoo_id,
'gclid': gclid,
'msclkid': msclkid
}
# Append data to URL
url += '?' + urllib.parse.urlencode(data)
# Set request header
headers = {'Referer': 'https://yourwebsite.com'}
# Create request object
req = urllib.request.Request(url, headers=headers)
# Execute the request
with urllib.request.urlopen(req) as response:
response_data = response.read()
# Process response as needed
print(response_data)
# Assuming you have retrieved the user ID from the session or other means
user_id = 'user123' # Replace with actual user ID
# Your Kelkoo group information - Static values
country = 'fr'
com_id = 100475501
# Order information - dynamic values to retrieve from the order information
order_id = 'CMD0572084'
order_value = 609.07
basket = [
{
'productname': 'Shimano',
'productid': 'prod130823',
'price': 14.99,
'quantity': 2
}
]
# Retrieve KelkooId, Google Click Id, Microsoft click ID from the database
kelkoo_id, google_click_id, msclkid = get_ids_from_database(user_id)
if kelkoo_id or google_click_id or msclkid:
# Call Kelkoo Sales Tracking Webservice
call_kelkoo_sales_tracking(country, com_id, order_id, order_value, encode_basket(basket), generate_sale_id(), kelkoo_id, google_click_id, msclkid)
#### Node.js (version 20.x)
* The following example shows you how to store tracking click ID (kelkooId / Google Click Id / Microsoft Click ID) in the database whenever a page is visited and associate it with the current user upon login and during basket interactions.
const mysql = require('mysql');
// Create a connection to MySQL database
const db = mysql.createConnection({
host: 'localhost',
user: 'username',
password: 'password',
database: 'database_name'
});
// Connect to the database
db.connect((err) => {
if (err) {
throw err;
}
console.log('Connected to MySQL database');
});
// Function to store kelkooId / Google Click Id / Microsoft Click ID in the database
function storeIdsInDatabase(userId, kelkooId, googleClickId, msclkid) {
// Escape inputs to prevent SQL injection
kelkooId = db.escape(kelkooId);
googleClickId = db.escape(googleClickId);
msclkid = db.escape(msclkid);
userId = db.escape(userId);
// Check if kelkooId, googleClickId, or msclkid is not null
if (kelkooId !== null || googleClickId !== null || msclkid !== null) {
// Insert query to store data in the database
const query = `REPLACE INTO user_tracking (user_id, kelkoo_id, google_click_id, ms_clk_id) VALUES (${userId}, ${kelkooId}, ${googleClickId}, ${msclkid})`;
// Execute query
db.query(query, (err, result) => {
if (err) {
throw err;
}
console.log('Data inserted into database');
});
}
}
// Function to extract parameters from URL
function extractParamsFromUrl(url) {
const queryString = require('query-string');
const parsed = queryString.parseUrl(url);
return parsed.query;
}
// Assuming you retrieve the current URL
const currentUrl = req.url;
// Extract parameters from URL
const params = extractParamsFromUrl(currentUrl);
// Extract kelkooId, googleClickId, and msclkid from parameters
const kelkooId = params.kk || null;
const googleClickId = params.gclid || null;
const msclkid = params.msclkid || null;
// Assuming you also retrieve the user ID from your session or other means
const userId = req.session.user_id;
// Call the function to store IDs in the database if kelkooId, googleClickId, or msclkid is not null
if (kelkooId !== null || googleClickId !== null || msclkid !== null) {
storeIdsInDatabase(userId, kelkooId, googleClickId, msclkid);
}
* The following example illustrates how to retrieve the Tracking click ID (KelkooId, Google Click ID, or Microsoft Click ID) from the database when the Confirmation Page is displayed, and then call the Kelkoo Sales Tracking Webservice with your domain specified in the request header.
const https = require('https');
const querystring = require('querystring');
// Function to retrieve KelkooId, Google Click Id, and Microsoft Click ID from the database
function getIdsFromDatabase(userId) {
// Assuming db is your database connection
return new Promise((resolve, reject) => {
const query = `SELECT kelkoo_id, google_click_id, ms_clk_id FROM user_tracking WHERE user_id = '${userId}'`;
db.query(query, (err, result) => {
if (err) {
reject(err);
} else {
resolve(result[0]);
}
});
});
}
// Function to custom base64 encode without padding
function customBase64Encode(data) {
return Buffer.from(data).toString('base64').replace(/=+$/, '');
}
// Function to encode basket items
function encodeBasket(productsArray) {
const jsonData = JSON.stringify(productsArray);
const base64Data = customBase64Encode(jsonData);
return encodeURIComponent(base64Data);
}
// Function to generate a random sale ID
function generateSaleId() {
return Math.random();
}
// Function to call Kelkoo Sales Tracking Webservice
function callKelkooSalesTracking(country, comId, orderId, orderValue, productsInfos, saleId, kelkooId, gclid, msclkid) {
const data = {
country,
orderId,
comId,
orderValue,
productsInfos,
saleId,
kelkooId,
gclid,
msclkid
};
const url = `https://s.kelkoogroup.net/st?${querystring.stringify(data)}`;
const options = {
method: 'GET',
headers: {
'Referer': 'https://yourwebsite.com'
}
};
https.get(url, options, (res) => {
console.log('Response status code:', res.statusCode);
}).on('error', (err) => {
console.error('Error:', err.message);
});
}
// Assuming you have retrieved the user ID from the session or other means
const userId = req.session.user_id;
// Your Kelkoo group information - Static values
const country = 'fr';
const comId = 100475501;
// Order information - dynamic values to retrieve from the order information
const orderId = 'CMD0572084';
const orderValue = 609.07;
const basket = [{
productname: 'Shimano',
productid: 'prod130823',
price: 14.99,
quantity: 2
}];
// Retrieve KelkooId, Google Click Id, Microsoft Click ID from the database
getIdsFromDatabase(userId)
.then(ids => {
if (ids.kelkoo_id || ids.google_click_id || ids.ms_clk_id) {
// Call Kelkoo Sales Tracking Webservice
callKelkooSalesTracking(country, comId, orderId, orderValue, encodeBasket(basket), generateSaleId(), ids.kelkoo_id, ids.google_click_id, ids.ms_clk_id);
}
})
.catch(err => {
console.error('Error:', err);
});
---
language: "en"
---
# How To get your merchantId and associated Country Code
* Connect to *Kelkoo Group Merchant Extranet*
* Click on the dropdown at the top left
* Here you can see your Merchant Id and associated country code (in bracket)
In the example above you have the following
| merchantId | country |
|------------|---------|
| 100523248 | fr |
| 100507945 | de |
Here is the list of countries code we use at Kelkoo
| Code | Country |
|------|----------------------|
| ae | United Arab Emirates |
| au | Australia |
| at | Austria |
| be | Belgium |
| br | Brazil |
| ca | Canada |
| ch | Switzerland |
| cz | Czech Republic |
| de | Germany |
| dk | Denmark |
| gr | Greece |
| es | Spain |
| fi | Finland |
| fr | France |
| hk | Hong Kong |
| ie | Ireland |
| it | Italy |
| in | India |
| id | Indonesia |
| jp | Japan |
| kr | South Korea |
| my | Malaysia |
| mx | Mexico |
| nb | Flemish Belgium |
| nl | Netherlands |
| no | Norway |
| nz | New Zealand |
| ph | The Philippines |
| pl | Poland |
| pt | Portugal |
| ru | Russia |
| se | Sweden |
| sg | Singapore |
| tr | Turkey |
| uk | United Kingdom |
| us | United States |
| vn | Vietnam |
| za | South Africa |
---
language: "en"
---
# Installation Guides for eCommerce platforms
* [Magento](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/magento.md)
* [Shopify/Shopify Plus](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/shopify-shopify-plus.md)
* [WooCommerce](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/woocommerce.md)
* [Unas Ecommerce](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/unas-ecommerce.md)
* [Prestashop 1.6x](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/prestashop-1-6x.md)
* [Prestashop 1.7x](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/prestashop-1-7x.md)
* [Prestashop 8](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/prestashop-8.md)
* [LightSpeed (C-Series)](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/installation-guides-for-ecommerce-platforms/lightspeed-c-series.md)
---
language: "en"
---
# LightSpeed (C-Series)
This is the documentation to install Kelkoo Sales tracking for Lightspeed C-series.
## Before setting up your Kelkoo Sales Tracking Tag
### Get your merchantId and associated Country Code
See How To get your merchantId and associated Country Code.
## Installing Kelkoo Sales Tracking
1. Login to your Lightspeed Account.
2. On the left side menu, click on 'Web Extras'.
**Lead Tag**
3. Click on Custom JavaScript and add the **Lead Tag**in the text area.
**Conversion Tag**
4. Copy the code below and replace the COUNTRY_CODE and MERCHANT_ID with the one associated to your campaign in the **Conversion Tag.**
5. Click on Tracking Code and add the **Conversion Tag.**
6. Save the changes.
7. Perform a Test Order.
---
language: "en"
---
# Magento
This is a guide to manually install Kelkoo Sales Tracking if you use Magento 1 or 2 (up to 2.3).
You need to edit part of your code to succeed with this implementation.
## Before setting up your Kelkoo Sales Tracking Tag
### Get your merchantId and associated Country Code
See How To get your merchantId and associated Country Code
### Clean any old version of Kelkoo Sales Tracking
* In your code, remove any Kelkoo Sales tracking tag (search for *leadtag.js* and *_kkstrack*)
* On your website backend, uninstall any Kelkoo Sales Tracking plugin you might have installed
## Magento 1
You need to install two elements:
* the *Leadtag*, in charge of writing the cookie when the user first visits your website
* the *Conversion tag*, in charge of retrieving data from the cookie and registering the sale
**BOTH ARE MANDATORY FOR KELKOO SALES TRACKING TO WORK**
### Install the leadtag
Find and edit the right XML layout and add :
XML
]]>
### Install the conversion tag
* Paste this code **at the end of the file**. It gets the Order Value and the Order Id mandatory for Kelkoo Sales Tracking to work.
To add in *web/app/design/frontend/custom/default/template/checkout/success.phtml* , where *custom* is the name of your template.
PHP
loadByIncrementId($this->getOrderId());
$_totalData =$orderObj->getData();
?>
* Right after the code added above, add the Conversion tag.
HTML
* You need to edit some elements of the Conversion Tag. Those values can be hardcoded as they are the same for all the sales registered.
* *MERCHANTID_VALUE*: This is the unique ID representing your shop within the Kelkoo Group system.
* Check How To get your merchantId and associated Country Code.
* If you have multiple MerchantId please check [If you have multiple merchantIds and countries](https://developers.kelkoogroup.com/#multi-country--multi-campaign-integration)
* *COUNTRY_CODE* is the 2-letter country code (lower case) for the country on which your products are listed on Kelkoo Group. Check Full list of Kelkoo Group country codes
## Magento 2
### Install the leadtag
If you want to add Kelkoo Sales Tracking leadtag without creating a module, you can add the following code on your active theme.
To add in *YourTheme/Magento_Theme/layout/default_head_blocks.xml*
HTML
### Install the Conversion tag
* If missing, create *app/code/* under your Magento installation
* Download *magento2-kelkoogroup-salestracking-1.0.0.zip* module for Magento 2 here:
* extract the content of the zip file in directory */app/code*
* check directory tree, you should have something similar to:
app/code/Kelkoo/Modulekelkoost/
|- Block
| |- Success.php
|- etc
| |- di.xml
| |- module.xml
|- registration.php
|- view
| |- frontend
| | |- layout
| | | |- checkout_onepage_success.xml
| | |- templates
| | | |- checkout
| | | | |- success.phtml
* Modify *app/code/Kelkoo/Modulekelkoost/view/frontend/templates/checkout/success.phtml* to set the correct country and MerchantId
HTML
getOrder()->getId()):?>
* Enable kelkoost module :
php bin/magento module:enable Kelkoo_Modulekelkoost
php bin/magento setup:upgrade --keep-generated
## Test your integration
Please check Test Integration
---
language: "en"
---
# Prestashop 1.6x
This is a guide to manually install Kelkoo Sales Tracking if you use Prestashop 1.6 or older.
You need to edit part of your code to succeed with this implementation.
## Before setting up your Kelkoo Sales Tracking Tag
### Get your merchantId and associated Country Code
See How To get your merchantId and associated Country Code
### Clean any old version of Kelkoo Sales Tracking
* In your code, remove any Kelkoo Sales tracking tag (search for *leadtag.js* and *_kkstrack*)
* On your website backend, uninstall any Kelkoo Sales Tracking plugin you might have installed
### Backup your files
Before doing any changes, please remember to back up the files you're going to modify.
### Check Recompile option
* Go to *Advanced settings -\> Performance*
* Make sure option "Recompile files of template if updated" is checked.
## Install the leadtag
* Open the file *themes/custom/header.tpl* (where *custom* is the name of your template, the default being "prestashop")
* Add at the bottom of the file
HTML
* Clear the cache.
## Install the conversion tag
* Open the file */controllers/front/OrderConfirmationController.php*
* Search the following line
public function initContent()
{
* Add this code
PHP
/* Kelkoo Sales Tracking */
$order = new Order($this->id_order);
$products = $order->getProducts();
$productsKelkoo=array();
foreach ($products as $product) {
$productKelkoo=array('productname'=>$product['product_name'],
'productid'=>$product['product_reference'],
'quantity'=>$product['product_quantity'],
'price'=>$product['unit_price_tax_incl']);
array_push($productsKelkoo,$productKelkoo);
}
$this->context->smarty->assign(array(
'is_guest' => $this->context->customer->is_guest,
'HOOK_ORDER_CONFIRMATION' => $this->displayOrderConfirmation(),
'HOOK_PAYMENT_RETURN' => $this->displayPaymentReturn(),
'products_json' => json_encode($productsKelkoo),
'sales' => $order->getOrdersTotalPaid(),
'orderid' => $this->id_order
));
/* end Kelkoo Sales Tracking*/
* Go to the directory *themes/custom* (where *custom* is the name of your template, the default being "prestashop") and open the file *order-confirmation.tpl*
* Add at the bottom of the file
JavaScript
## Customize Conversion tag code
You need to edit some elements of the Conversion Tag
Those values can be hardcoded as they are the same for all the sales registered.
* MERCHANTID_VALUE: This is the unique ID representing your shop within the Kelkoo Group system.
* Check How To get your merchantId and associated Country Code.
* If you have multiple MerchantId please check [If you have multiple merchantIds and countries](https://developers.kelkoogroup.com/#multi-country--multi-campaign-integration)
* COUNTRY_CODE is the 2-letter country code (lower case) for the country on which your products are listed on Kelkoo Group. Check Full list of Kelkoo Group country codes
### If you have multiple merchantIds and countries
If you have several Kelkoo Group campaigns running for the same website (multiple MerchantId), you can setup all campaigns within the same tag.
You just need to have the following structure for the *merchantInfo* variable:
merchantInfo : [
{
country:'fr',
merchantId:'12941513'
},
{
country:'uk',
merchantId:'56789'
}
]
## If you use PayPal module for payments
If you enabled PayPal payment then you have to change two additional files:
* Open */modules/paypal/controllers/front/submit.php*
* Search for the following line inside the class *PayPalSubmitModuleFrontController* (you should find it at line 46)
$order = new Order($this->id_order);
* add below
PHP
/* Kelkoo Sales Tracking */
$products = $order->getProducts();
$productsKelkoo=array();
foreach ($products as $product) {
$productKelkoo=array('productname'=>$product['product_name'],
'productid'=>$product['product_reference'],
'quantity'=>$product['product_quantity'],
'price'=>$product['unit_price_tax_incl']);
array_push($productsKelkoo,$productKelkoo);
}
$this->context->smarty->assign(array(
'is_guest' => $this->context->customer->is_guest,
'HOOK_ORDER_CONFIRMATION' => $this->displayOrderConfirmation(),
'HOOK_PAYMENT_RETURN' => $this->displayPaymentReturn(),
'products_json' => json_encode($productsKelkoo),
'sales' => $order->getOrdersTotalPaid(),
'orderid' => $this->id_order
));
/* end Kelkoo Sales Tracking*/
* Open */modules/paypal/views/templates/front/order-confirmation.tpl*
* Add at the bottom of the file
JavaScript
## Clear Prestashop Cache
Admin \> Advanced Paramaters \> Performance \> Clear Cache
## Test your integration
Please check Test Integration
## If you face issues
Please check Common Issues with Prestashop Integration before contacting the support.
---
language: "en"
---
# Prestashop 1.7x
This is a guide to manually install Kelkoo Sales Tracking if you use Prestashop 1.7 and newer (tested with Prestashop 1.7.8.2)
You need to edit part of your code to succeed with this implementation.
## Before setting up your Kelkoo Sales Tracking Tag
### Get your merchantId and associated Country Code
See How To get your merchantId and associated Country Code
### Clean any old version of Kelkoo Sales Tracking
* In your code, remove any Kelkoo Sales tracking tag (search for *leadtag.js* and *_kkstrack*)
* On your website backend, uninstall any Kelkoo Sales Tracking plugin you might have installed
### Backup your files
Before doing any changes, please remember to back up the files you're going to modify.
### Check Recompile option
* Go to *Advanced parameters -\> Performance*
* Make sure that "Recompile templates if files have been updated " is selected for *Template compilation*.
## Install the leadtag
* Open *themes//templates/_partials/head.tpl* (where *custom* is the name of your template, the default being "prestashop")
* Add
* Clear you cache by going to *Admin \> Advanced Paramaters \> Performance \> Clear Cache*
## Install the Conversion tag
* Open the file */controllers/front/OrderConfirmationController.php*
* Replace following code block:
this->context->smarty->assign(array(
'HOOK_ORDER_CONFIRMATION' => $this->displayOrderConfirmation($order),
'HOOK_PAYMENT_RETURN' => $this->displayPaymentReturn($order),
'order' => $presentedOrder,
'register_form' => $register_form,
));
* With:
/* Kelkoo Sales Tracking */
$order = new Order($this->id_order);
$products = $order->getProducts();
$productsKelkoo=array();
foreach ($products as $product) {
$productKelkoo=array('productname'=>$product['product_name'],
'productid'=>$product['product_reference'],
'svn1'=>$product['product_quantity'],
'svn2'=>$product['unit_price_tax_incl']);
array_push($productsKelkoo,$productKelkoo);
}
$this->context->smarty->assign(array(
'HOOK_ORDER_CONFIRMATION' => $this->displayOrderConfirmation($order),
'HOOK_PAYMENT_RETURN' => $this->displayPaymentReturn($order),
'products_json' => json_encode($productsKelkoo),
'sales' => $order->getOrdersTotalPaid(),
'orderid' => $this->id_order,
'order' => $presentedOrder,
'register_form' => $register_form,
));
/* end Kelkoo Sales Tracking*/
* Go to directory */themes//templates/checkout/_partials/order-confirmation-table.tpl*
* Add at the bottom the file
* If you have a */themes//templates/checkout/_partials/order-confirmation-table-simple.tpl* file you also need to update it with same previous code (express checkout).
## Customize Conversion tag code
You need to edit some elements of the Conversion Tag
Those values can be hardcoded as they are the same for all the sales registered.
* MERCHANTID_VALUE: This is the unique ID representing your shop within the Kelkoo Group system.
* Check How To get your merchantId and associated Country Code.
* If you have multiple MerchantId please check [If you have multiple merchantIds and countries](https://developers.kelkoogroup.com/#multi-country--multi-campaign-integration)
* COUNTRY is the 2-letter country code (lower case) for the country on which your products are listed on Kelkoo Group. Check Full list of Kelkoo Group country codes.
## If you have multiple merchantIds and countries
If you have several Kelkoo Group campaigns running for the same website (multiple MerchantId), you can setup all campaigns within the same tag.
You just need to have the following structure for the *merchantInfo* variable:
merchantInfo : [
{
country:'fr',
merchantId:'12941513'
},
{
country:'uk',
merchantId:'56789'
}
]
* Clear you cache by going to *Admin \> Advanced Paramaters \> Performance \> Clear Cache*
## Test your integration
Please check Test Integration
## If you face issues
Please check Common Issues with Prestashop Integration before contacting the support.
---
language: "en"
---
# Prestashop 8
This is a guide to manually install Kelkoo Sales Tracking if you use Prestashop 8 and newer.
You need to edit part of your code to succeed with this implementation.
## Before setting up your Kelkoo Sales Tracking Tag
### Get your merchantId and associated Country Code
See How To get your merchantId and associated Country Code
### Clean any old version of Kelkoo Sales Tracking
* In your code, remove any Kelkoo Sales tracking tag (search for *leadtag.js* and *_kkstrack*)
* On your website backend, uninstall any Kelkoo Sales Tracking plugin you might have installed
### Backup your files
Before doing any changes, please remember to back up the files you're going to modify.
### Check Recompile option
* Go to *Advanced parameters -\> Performance*
* Make sure that "Recompile templates if files have been updated " is selected for *Template compilation*.
## Install the leadtag
* Open *themes/''/templates/_partials/head.tpl* (where *custom* is the name of your template, the default being "prestashop")
* Add
HTML
* Clear you cache by going to *Admin \> Advanced Paramaters \> Performance \> Clear Cache*
## Install the Conversion tag
* Open the file */controllers/front/OrderConfirmationController.php*
* Replace following code block:
PHP
$this->context->smarty->assign([
'HOOK_ORDER_CONFIRMATION' => $this->displayOrderConfirmation($this->order),
'HOOK_PAYMENT_RETURN' => $this->displayPaymentReturn($this->order),
'order' => (new OrderPresenter())->present($this->order),
'order_customer' => $this->objectPresenter->present($this->customer),
'registered_customer_exists' => Customer::customerExists($this->customer->email, false, true),
]);
* With:
PHP
/* Kelkoo Sales Tracking */
$order = new Order($this->id_order);
$products = $order->getProducts();
$productsKelkoo=array();
foreach ($products as $product) {
$productKelkoo=array('productname'=>$product['product_name'],
'productid'=>$product['product_reference'],
'svn1'=>$product['product_quantity'],
'svn2'=>$product['unit_price_tax_incl']);
array_push($productsKelkoo,$productKelkoo);
}
$this->context->smarty->assign([
'HOOK_ORDER_CONFIRMATION' => $this->displayOrderConfirmation($this->order),
'HOOK_PAYMENT_RETURN' => $this->displayPaymentReturn($this->order),
'products_json' => json_encode($productsKelkoo),
'sales' => $order->getOrdersTotalPaid(),
'orderid' => $this->id_order,
'order' => (new OrderPresenter())->present($this->order),
'order_customer' => $this->objectPresenter->present($this->customer),
'registered_customer_exists' => Customer::customerExists($this->customer->email, false,
true),
]);
/* end Kelkoo Sales Tracking*/
* Go to directory */themes//templates/checkout/_partials/order-confirmation-table.tpl*
* Add at the bottom the file
JavaScript
* If you have a */themes/''/templates/checkout/_partials/order-confirmation-table-simple.tpl* file you also need to update it with same previous code (express checkout).
## Customize Conversion tag code
You need to edit some elements of the Conversion Tag
Those values can be hardcoded as they are the same for all the sales registered.
* MERCHANTID_VALUE: This is the unique ID representing your shop within the Kelkoo Group system.
* Check How To get your merchantId and associated Country Code.
* If you have multiple MerchantId please check [If you have multiple merchantIds and countries](https://developers.kelkoogroup.com/#multi-country--multi-campaign-integration)
* COUNTRY is the 2-letter country code (lower case) for the country on which your products are listed on Kelkoo Group. Check Full list of Kelkoo Group country codes.
## If you have multiple merchantIds and countries
If you have several Kelkoo Group campaigns running for the same website (multiple MerchantId), you can setup all campaigns within the same tag.
You just need to have the following structure for the *merchantInfo* variable:
merchantInfo : [
{
country:'fr',
merchantId:'12941513'
},
{
country:'uk',
merchantId:'56789'
}
]
* Clear you cache by going to *Admin \> Advanced Paramaters \> Performance \> Clear Cache*
## Test your integration
Please check Test Integration
## In Case of Verison Update
The KST needs to be reinstalled after any Prestashop or theme upgrades.
## If you face issues
Please check Common Issues with Prestashop Integration before contacting the support.
---
language: "en"
---
# Shopify/Shopify Plus
## Before setting up your Kelkoo Sales Tracking Tag
### Get your merchantId and associated Country Code
See How To get your merchantId and associated Country Code
### Video Tutorial
The merchant can follow our Video Tutorial to install Kelkoo sales tracking for Shopify. Please refer to the link : [**How to install KST for Shopify**](https://groupleguidecom1-my.sharepoint.com/:v:/g/personal/stream_kelkoogroup_com/IQDV8HOLAZ6SS53MhxTnqPZ8Ae-tNONkp17On8QnfJPKKYM?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJPbmVEcml2ZUZvckJ1c2luZXNzIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXciLCJyZWZlcnJhbFZpZXciOiJNeUZpbGVzTGlua0NvcHkifX0&e=YMupt5)
## Install Kelkoo Sales Tracking module
### Implement lead tag
* Log in to your Shopify account.
* Navigate to and click on *Settings*.
* Select *Customer Events* from the sub-menu.
* Click on *Add Custom Pixel*.
* Set the name of Pixel as *Kelkoo Leadtag*.
* Edit the following lines of code:
**Leadtag Script**
JavaScript
(function() {
var leadTag = document.createElement('script');
leadTag.src = 'https://s.kk-resources.com/leadtag.js';
leadTag.async = true;
document.head.appendChild(leadTag);
})();
* Click on Customer Privacy:
* **Set Permission to Required Marketing / Analytics**
* **Set Data Sale to Data Collected does not qualify as data sale**
* Scroll to the bottom of the page and select *Connect*.
### Implement conversion tag
Follow similar steps to create Pixel
* Set the name of Pixel as *Kelkoo Conversion*.
* See How To get your merchantId and associated Country Code to get those two pieces of information.
* Edit the following lines of code:
JavaScript
analytics.subscribe("checkout_completed", event => {
console.log(event.data.checkout);
var basketFull = [] ;
var basketContent ;
for(i = 0 ; i < event.data.checkout.lineItems.length ; i++) {
basketContent = {} ;
basketContent.productname = event.data.checkout.lineItems[i].title ;
basketContent.productid = event.data.checkout.lineItems[i].id ;
basketContent.quantity = event.data.checkout.lineItems[i].quantity ;
basketContent.price = event.data.checkout.lineItems[i].variant.price ;
basketFull.push(basketContent) ;
}
_kkstrack = {
merchantInfo : [
{
country:'ADD YOUR COUNTRY CODE HERE',
merchantId:'ADD YOUR MERCHANT ID HERE'
}
],
orderValue: event.data.checkout.totalPrice.amount,
orderId: event.data.checkout.order.id,
basket: basketFull
};
(function() {
var s = document.createElement('script');
s.type = 'text/javascript';
s.async = true;
s.src = 'https://s.kk-resources.com/ks.js';
var x = document.getElementsByTagName('script')[0];
x.parentNode.insertBefore(s, x);
})();
});
* Click on Customer Privacy:
* **Set Permission to Not Required**
* **Set Data Sale to Data Collected does not qualify as data sale**
* Scroll to the bottom of the page and select *Connect*.
#### If you have multiple merchantIds and countries
If you have multiple Kelkoo Group campaigns running for the same website (multiple MerchantId), you can setup all campaigns within the same tag.
You just need to have the following structure for the *merchantInfo* variable:
JSON
merchantInfo : [
{
country:'fr',
merchantId:'123456'
},
{
country:'uk',
merchantId:'56789'
}
]
## Test your integration
Please check Test Integration
---
language: "en"
---
# Unas Ecommerce
## Before setting up your Kelkoo Sales Tracking Tag
### Get your merchantId and associated Country Code
See How To get your merchantId and associated Country Code
### Clean any old version of Kelkoo Sales Tracking
* In your code, remove any Kelkoo Sales tracking tag (search for *leadtag.js* and *_kkstrack*)
* On your website backend, uninstall any Kelkoo Sales Tracking plugin you might have installed
## Install Kelkoo Sales Tracking from Unas dashboard
### Step 1: Log in to your Unas dashboard, navigate to the *External marketing systems* through *Marketing* tab
### Step 2: Scroll down to find *Kelkoo Group logo* .
### Step 3: Click on *Add* button.
### Step 4: Activate it by entering your *merchantID* and *Save* changes.
* *merchantID*: This is the unique ID representing your shop within the Kelkoo Group system.
* Check How To get your merchantId and associated Country Code.
* If you have multiple MerchantId please see below
* *Country* here depends on the languages you add on *Settings/Texts,Languages/Setting languages*. Check Full list of Kelkoo Group country codes
## If you have multiple merchantIds and countries
If you have several Kelkoo Group campaigns running for the same website (multiple MerchantId), you can setup all campaigns in the *Kelkoo Group Sales tracking - multiple campaign*.
In order to setup a *Multi Merchant Campaign*, the web shop needs to have multiple languages set in the admin interface as shown.
### Step 1: In your Unas dashboard, navigate to the *Setting languages* through *Settings/Texts,Languages/*
### Step 2: Add required language/country.
### Step 3: Add merchantID provided for specific countries and *Save* changes
## Test your setup
Please check Test Installation
---
language: "en"
---
# WooCommerce
## Before setting up your Kelkoo Sales Tracking Tag
### Get your merchantId and associated Country Code
See How To get your merchantId and associated Country Code
### Clean any old version of Kelkoo Sales Tracking
* In your code, remove any Kelkoo Sales tracking tag (search for *leadtag.js* and *_kkstrack*)
* On your website backend, uninstall any Kelkoo Sales Tracking plugin you might have installed
## Install Kelkoo Sales Tracking from Wordpress dashboard
* Log in to your WordPress dashboard, navigate to the *Plugins* menu
* Click *Add New*.
* In the search field type *Kelkoo Group sales tracking* and click *Search Plugins*.
* You can install it by simply clicking *Install Now*.
* Once installed navigate to the *Plugins* menu again and activate the plugin
## Install Kelkoo Sales Tracking from source
* Download Kelkoo Group Salestracking plugin here:
* Go to folder */wp-content/plugins* and unzip the zip file
* Log to your WordPress admin dashboard, go to *Plugins* , Click *Activate*
## Configure the plugin
* On *Plugin* page go to *Settings* and click on the Kelkoo Group link
* Complete the form with information related to your Kelkoo Group subscription
* *Merchant Identifier*: This is the unique ID representing your shop within the Kelkoo Group system.
* Check How To get your merchantId and associated Country Code.
* If you have multiple MerchantId please see below
* *Country* is the 2-letter country code (lower case) for the country on which your products are listed on Kelkoo Group. Check Full list of Kelkoo Group country codes
## If you have multiple merchantIds and countries
If you have several Kelkoo Group campaigns running for the same website (multiple MerchantId), you can setup all campaigns in the *Kelkoo Group Sales tracking - multiple campaign*.
The *Multi Merchant Information* variable needs to have the following structure :
merchantInfo : [
{
country:'fr',
merchantId:'12941513'
},
{
country:'uk',
merchantId:'56789'
}
]
## Test your setup
Please check Test Installation
---
language: "en"
---
# Installation via Google Tag Manager (GTM) with Enhanced Ecommerce
If your website uses Google Tag Manager (GTM), this is the recommended method for installing Kelkoo Sales Tracking (KST).
## Video tutorial
You can also follow our video tutorial:[**How to Install KST using GTM**](https://groupleguidecom1-my.sharepoint.com/:v:/g/personal/stream_kelkoogroup_com/IQAekZ_Rdd8oRqOHZXHLwtSEAQbyieSnrYOEQi4-GStoC64?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJPbmVEcml2ZUZvckJ1c2luZXNzIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXciLCJyZWZlcnJhbFZpZXciOiJNeUZpbGVzTGlua0NvcHkifX0&e=c4t22X)
## Step 1: Identify the Data Layer variables
Before configuring Kelkoo Sales Tracking, you need to identify the Data Layer variables used by your website for purchase events.
### 1.1 Start GTM Preview mode
From your Google Tag Manager workspace, click **Preview** to launch Tag Assistant.
### 1.2 Connect your website
In the Tag Assistant window, enter your website URL and click **Connect**.
Make sure the URL belongs to the website on which the relevant GTM container is installed.
### 1.3 Check the connection
Your website should open in a new browser tab.
In Tag Assistant, confirm that the connection status is displayed as **Connected**.
### 1.4 Complete a test purchase
On the website opened in the previous step, complete a test purchase.
### 1.5 Find the purchase event
Return to Tag Assistant.
In the event list on the left, locate the event corresponding to the order confirmation or thank-you page.
### 1.6 Identify the relevant ecommerce event
Select the event associated with the completed purchase.
The exact event name depends on your website's GTM and Enhanced Ecommerce implementation.
### 1.7 Identify the required values
Open the **Data Layer** tab and identify the following values:
* **Event name**
* **Order ID**
* **Order value**
For example:
* Event name: `purchase`
* Order ID: `ecommerce.purchase.transaction_id`
* Order value: `ecommerce.purchase.value`
**Important:** Data Layer variables vary from one website to another. The examples above may therefore differ from those used on your website.
If you cannot find equivalent purchase information in the Data Layer, contact your ecommerce platform or implementation provider to check whether Enhanced Ecommerce data is being sent to GTM. Depending on your ecommerce platform, a plugin or extension may also be available to provide the required GTM ecommerce integration.
## Step 2: Create GTM user-defined variables
You now need to create GTM variables for the Order ID and Order Value identified in Step 1.
### 2.1 Open Variables
In your GTM workspace, select **Variables** from the left-hand menu.
### 2.2 Create a new variable
Under **User-Defined Variables** , click **New**.
### 2.3 Select the variable type
Click **Variable Configuration** , then select **Data Layer Variable**.
### 2.4 Create the Order ID variable
In **Data Layer Variable Name**, enter the Order ID variable identified in Step 1.7.
For example:
`ecommerce.purchase.transaction_id`
Give the variable a clear name, such as **Order ID**, and save it.
### 2.5 Create the Order Value variable
Repeat the previous step using the Order Value variable identified in Step 1.7.
For example:
`ecommerce.purchase.value`
Give the variable a clear name, such as **Order Value**, and save it.
## Step 3: Create a trigger for the purchase event
Next, create a GTM trigger that fires when the purchase event identified in Step 1 occurs.
### 3.1 Open Triggers
From the left-hand menu, select **Triggers**.
### 3.2 Create a new trigger
Click **New** , then click **Trigger Configuration**.
### 3.3 Select Custom Event
Choose **Custom Event** as the trigger type.
### 3.4 Configure the event
In **Event name**, enter the event name identified in Step 1.7.
For example:
`purchase`
Configure the trigger to fire on the appropriate purchase event, as shown in the screenshot below.
### 3.5 Save the trigger
Give the trigger a clear name, such as **Purchase Event** , and click **Save**.
## Step 4: Install the Kelkoo Sales Tracking tag
### 4.1 Open the Template Gallery
In GTM, select **Templates**.
Under **Tag Templates** , click **Search Gallery**.
### 4.2 Add the Kelkoo Group template
Search for **Kelkoo Group Sales Tracking Tag** and select it.
In the Template Details window, click **Add to workspace**.
### 4.3 Create the Kelkoo Sales Tracking tag
Go to **Tags** and create a new tag.
Under **Tag Configuration** , select the **Kelkoo Group Sales Tracking Tag** template.
### 4.4 Configure the tag
Configure the tag using:
* Your **Country Code**
* Your **Merchant ID**
* The **Order ID** GTM variable created in Step 2
* The **Order Value** GTM variable created in Step 2
Use the variable selector to choose the existing GTM variables created in Steps 2.4 and 2.5. Do not enter their names as plain text.
### 4.5 Add the purchase trigger
Under **Triggering**, select the custom purchase event trigger created in Step 3.
This ensures that the Kelkoo Sales Tracking tag fires when a purchase is completed.
### 4.6 Save the tag
Click **Save**.
## Step 5: Install the Kelkoo Lead Tag
The Kelkoo Lead Tag must also be installed and configured to fire on every page.
### 5.1 Create the Lead Tag
From the **Tags** menu, create a new **Custom HTML** tag.
Add the following code:
HTML
Under **Triggering** , select **All Pages**.
### 5.2 Save and publish
Save the tag.
Once you have completed the configuration, **Preview** your GTM container to verify that the tags fire as expected.
When you are satisfied with the setup, publish your GTM changes to complete the Kelkoo Sales Tracking installation.
## Test your setup
Once the installation is complete, we strongly recommend testing your implementation to make sure Kelkoo Sales Tracking is working correctly.
See **Test your Kelkoo Sales Tracking setup** for instructions.
## Troubleshooting
If you experience any issues with your installation, see [Troubleshooting GTM Integration](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/troubleshooting/troubleshooting-gtm-integration.md) before contacting our Support team.
---
language: "en"
---
# Manual installation for Kelkoo Sales Tracking
## Overview
Use this installation method if you are **not using Google Tag Manager (GTM)** or if you prefer to integrate Kelkoo Sales Tracking directly into your website's source code.
This guide explains how to manually install the two tags required for Kelkoo Sales Tracking:
* **Lead Tag** -- sets a first-party tracking cookie when a user visits your website.
* **Conversion Tag** -- reads the tracking cookie and sends completed order information to Kelkoo.
> **Important**
>
> Both the **Lead Tag** and the **Conversion Tag** must be installed. Without both tags, Kelkoo Sales Tracking cannot correctly attribute conversions.
## Before You Begin
Before installing the tags, make sure you have:
* Access to your website's source code.
* Your **Merchant ID** and **Country Code**.
* Access to the order confirmation (thank-you) page.
## Find Your Merchant ID and Country Code
Log in to your Kelkoo Merchant Portal and [retrieve your **Merchant ID** and associated **Country Code**](https://docs.kelkoogroup.com/for-advertisers/kelkoo-sales-tracking/installation-methods/how-to-get-your-merchantid-and-associated-country-code.md).
These values are required when configuring both tracking tags.
## Remove Previous Installations
If your website already includes an older version of Kelkoo Sales Tracking, remove it before installing the new tags (search for `leadtag.js` and `_kkstrack`).
Running multiple versions of the tracking code may result in duplicate or incorrect conversion tracking.
## Step 1 - Install Lead tag
The Lead Tag sets the first-party tracking cookie used to attribute future conversions.
Add the following script to **every page of your website** , immediately before the closing `` tag.
HTML
Once installed, the Lead Tag will automatically create the tracking cookie for eligible visitors.
## Step 2 -- Install the Conversion Tag
The Conversion Tag sends completed order information to Kelkoo.
Add the following script to your **order confirmation (thank-you) page** , immediately before the closing ` ` tag.
HTML