Personal Data Review (GDPR)
Overview
This article describes what personal data Omniconvert Explore collects about your website's visitors, where it is stored, which services it is shared with, and which cookies Explore sets in the visitor's browser. Use it when you review Explore for GDPR compliance or fill in your own cookie policy.
How visitors are identified
Each visitor is identified by a unique, randomly generated ID, such as 1397959525186146805.
Data can also be linked to a session, using a randomly generated session ID, such as ses1938008560ion or sess.2.1690461205.1570627742542.
Data stored on our servers
Stored permanently
Linked to the visitor ID and the session ID:
Conversions (events), such as making a purchase or clicking a button
Survey responses
Survey duration: the time from the start of the survey until the responses are submitted
Lead info (name, email, phone), plus country, region and city *
Custom user attributes, explicitly sent by the website
The URL on which the experiment or survey was applied
Browser name and version
Device resolution
Device type: desktop, tablet or mobile
Country, region and city **
Referrer type: direct, referral, paid traffic or organic search
Visitor type: new or returning, determined from a cookie
Operating system
Timestamp
* Optional. Stored only if you choose this option when you create the experiment.
** Determined from the IP address, using a third-party provider library. The data is not sent to that provider.
This information is used to show aggregated, anonymized reports. Lead information submitted by the visitor is the exception: it is not anonymized.
The application can also use some of this data for each visitor in segmentation, to decide which experiments to apply next:
Viewed experiments, to know which variation a visitor has seen before
Conversions
Survey answers
Custom user attributes
Stored temporarily
Linked to the visitor ID and the session ID:
The URL on which the experiment or survey was applied, per session
Not stored
IP address: used only to determine the visitor's location and to apply segmentation (for example, to limit an experiment to your own IP while you test it before release).
Internet service provider: used only in segmentation.
Third-party services and integrations
Opt-in services that receive anonymized data
Google Analytics (events)
Inspectlet
Hotjar
Kissmetrics
HubSpot
Yandex Metrica
Opt-in services that receive personal data supplied by the visitor
MailChimp
GetResponse
Campaign Monitor
FreshMail
SalesManago
Woopra
Zapier
These are generally connected to lead collectors, so the data sent is usually a name and an email address or phone number.
Internal-use services
We send Intercom the personal data that clients of the Omniconvert platform (not their website visitors) have provided to us.
Data stored in the visitor's browser
Kept for 1 year
Visitor ID
Session ID
A brief experiment history (which variations were seen)
Number of visits
First and last visit time
Lead collector status (completed or refused, and when)
Survey status (completed or refused, and when)
Refreshed each session
Landing page for the current session
Referrer URL for the current session
Referrer type: direct, referral, paid traffic or organic search
Visitor type: new or returning, determined from a cookie
Current session start time
Experiments seen in the current session
UTM parameters of the current session's landing page (for the Google Analytics integration)
Cookies
What each cookie does
| Cookie | Lifetime | What it stores |
|---|---|---|
mktz_optout | 1 year | The visitor's choice to opt out. While it is set, the tracking code does not run for them, so nothing from Explore applies. |
mktz_client | 1 year | Whether the visitor is new or returning, the generated visitor ID and session ID, the number of pages viewed in the current session, the total number of sessions, the referrer URL and type, the date and time of the first and last visit, the experiments viewed in the current session, and the UTM parameters from the URL that started the session (if any). |
mktz_survey | 1 year | The status of a survey: completed, rejected or remind me later. |
mktz_interaction | 1 year | Whether a lead was collected by an overlay. |
mktz_ab | 1 year | The variation viewed for each A/B test the visitor has seen, so the visitor always sees the same variation. |
mktz_storage | 1 year | Additional information needed by experiments, such as whether the visitor interacted with an experiment, scrolled the page or used the search bar. |
mktz_persistent_group | 1 year | The visitor's RFM group, saved while they are signed in to the website, so the group is still known on later visits when they are not signed in. Used by the RFM integration. |
mktz_sess | Session (10 hours of inactivity) | The session ID. |
mktz_temp_* | Session (10 hours of inactivity) | The view of an experiment that has a frequency limit, such as once per session. * is a number. |
mktz_engagement | 1 hour or less | The time an experiment that uses the Engagement goal was viewed, to measure the time passed and the pages viewed since. |
_mktz_enabled | 1 hour or less | Whether the browser accepts cookies. It is set only to be read back immediately. |
Cookie types and the impact of blocking them
| Cookie | Type | If it is blocked |
|---|---|---|
mktz_optout | Strictly necessary | The opt-out is lost: the tracking code runs for the visitor, and experiments are shown, even if they chose to opt out. |
mktz_client | Strictly necessary | Segmentation does not work correctly, and experiments are not applied reliably as set up in the dashboard. |
mktz_storage | Strictly necessary | Segmentation and experiment functionality break. |
_mktz_enabled | Strictly necessary | Experiments are not applied. |
mktz_survey | Functional | Surveys keep showing even after the visitor completed them, which can annoy the visitor. |
mktz_interaction | Functional | The lead collection in overlays is triggered multiple times. |
mktz_ab | Functional | The same visitor may see different variations of the same test. |
mktz_sess | Session | Each view is recorded as a new visitor, which breaks segmentation and affects how experiments are applied. |
mktz_temp_* | Session | Experiments ignore the frequency settings set up in the dashboard, which can annoy the visitor. |
mktz_persistent_group | Targeting | Segmentation and the application of experiments break. It is only used when the website is integrated with Reveal; otherwise, blocking it breaks nothing. |
mktz_engagement | Performance | Experiment reporting in the dashboard breaks. |
For when each cookie is set and how its expiry is counted, see Omniconvert Cookies Reference.
Opt-out
Visitors can opt out by opening any page of your website with the mktz_optout parameter in the address. From then on, the tracking code does not run for them, so nothing from Explore applies: no experiments, surveys or overlays, and no tracking. A cookie marking the opt-out is set for 1 year. For the exact link and how to share it, see Configure GDPR & Privacy Settings.