Skip to main content
If you want to learn which data Kameleoon stores client-side, in the visitor’s browser, refer to the data collection client-side article.
This article primarily applies to Kameleoon Web Experimentation or when using Kameleoon Hybrid Experimentation mode.If you only use Kameleoon’s SDKs (Feature Experimentation), Kameleoon collects no data except:
  • Data you explicitly send using the addData method of the SDK.
  • All exposure events related to feature flag evaluations.

​
List of collected data

Kameleoon collects and stores the following data on its backend servers for each visit an individual visitor makes to your website:
  • Visitor code (a unique Kameleoon identifier for this visitor)
  • Visit number (if the same visitor made multiple visits)
  • Device type (mobile, tablet, or desktop)
  • Operating system (Windows, macOS, Linux)
  • Browser name and version
  • Screen size
  • Window size
  • Browser time zone
  • Browser language
  • Original referrer (acquisition channel)
  • Number of pages viewed
  • Time elapsed since the visitor’s previous visit (if any)
  • Time spent on the website
  • Start and end time of the visit
  • Number of mouse clicks
  • Ad blocker detection (whether the visitor has an ad blocker)
  • List of conversions (for example, clicks, transactions), including revenue (if applicable)
  • List of personalizations and A/B experiments seen by the visitor
  • List of targeted Kameleoon segments (requires Audiences Explorer)
  • Current weather conditions (if you use the corresponding targeting condition): temperature, wind, rain, and other conditions.
  • Sunset and sunrise times (required for some weather-based targeting criteria)
  • Geolocation (only if you use a corresponding targeting condition, as some weather-related criteria require geolocation data)
  • Products viewed (only if you enable the add-on)
  • Titles and URLs of pages visited
  • Custom data
  • External segmentation data (obtained from a third-party DMP or CRM)
  • Conversion probabilities computed by the Kameleoon AI Targeting engine (only when at least one AI-driven personalization is active; required for generating Kameleoon Conversion Score heat ranges)
By default, Kameleoon doesn’t collect any personal information as defined by GDPR or similar data privacy laws. However, Kameleoon may still collect and store personal data on its backend servers in the following cases:
  • Your URLs contain parameters with personal data, as Kameleoon collects visited URLs. Kameleoon strongly recommends removing such parameters from your URLs, as all web analytics platforms collect them.
  • You explicitly define a custom data field and populate it with personal data.
  • You explicitly configure an integration with a third-party DMP or CRM that provides personal data.
Kameleoon never stores IP addresses on its data servers. There are no exceptions to this rule: even when a visitor gives legal consent, Kameleoon doesn’t save IP addresses.

​
Data retention policy

Kameleoon retains visit and product event data for 24 months for analytics purposes. The retention period begins when Kameleoon processes the first event. If you require a shorter retention period, contact your Customer Success Manager.
  • Cross-Device Experimentation: you can retrieve 2 months of prior data for targeting in Web Experimentation and Feature Experimentation.
  • ITP Management: you can retrieve 2 months of prior data for targeting in Web Experimentation and Feature Experimentation.
  • Remote Synchronization of Visits: you can retrieve 2 months of prior data for targeting in Web Experimentation and Feature Experimentation.
  • AI Targeting: Kameleoon uses 2 months of prior data to compute Kameleoon Conversion Scores.
  • Product Targeting: you can retrieve 2 months of prior data for targeting in Web Experimentation.
  • Data API MAP Endpoint: you can retrieve 1 year of prior data in Web Experimentation and Feature Experimentation.