Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Yxper is a digital experience and personalisation tool embedded on websites to analyse visitor behaviour and tailor content. In a standard deployment it sets analytics cookies and collects interaction data through a client side script. Because these cookies are not strictly necessary, its use requires prior consent under European data protection and ePrivacy rules.
Yxper is a digital experience and personalisation tool that websites embed through a client side script. It observes how visitors navigate and interact with pages, builds behavioural insight and can adapt content to individual users. Tools in this category typically combine session analytics, segmentation and personalisation, all of which depend on recognising visitors over time.
In a standard deployment Yxper sets analytics cookies and may store identifiers in the browser to recognise returning visitors. It commonly collects page views, clicks, scrolling, navigation paths, device and browser attributes and IP addresses. This behavioural data is used to measure engagement and to drive personalisation, which can amount to profiling depending on configuration.
The analytics cookies and identifiers Yxper sets are not strictly necessary, so storing or reading them is subject to prior consent under Article 5(3) of the ePrivacy Directive. The behavioural data and IP addresses it processes are personal data under the GDPR, requiring a lawful basis, transparency, data minimisation and respect for data subject rights, especially where personalisation involves profiling.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Yxper should load only after the visitor gives freely given, specific, informed and unambiguous consent for analytics and personalisation. The script must stay blocked until consent is granted, withdrawal must be as easy as giving consent, and where personalisation produces significant effects you should give clear information about that profiling. Maintain a record of each consent decision.
Experience and analytics vendors often process data on infrastructure located in the United States or other third countries. If Yxper transfers personal data outside the European Economic Area, you need a valid transfer mechanism such as the EU US Data Privacy Framework or Standard Contractual Clauses, together with a transfer impact assessment and any necessary supplementary measures.
Place Yxper behind a consent management platform, document its cookies and the behavioural data it collects, and record the legal basis and purposes in your processing records. Sign a data processing agreement, confirm transfer safeguards and retention limits, enable any IP anonymisation or data minimisation options offered, and test that declining consent prevents all collection.
Websites using Yxper must obtain user consent under GDPR regulations.
DPIA considerations
A data protection impact assessment should be considered where Yxper is used for systematic behavioural analysis or personalisation across large audiences. Assess the interaction data and identifiers collected, whether profiling occurs, retention periods, the legal basis, any transfers outside the EEA and how consent is captured, recorded and withdrawn.
Sample consent text
We use Yxper to understand how visitors use our site and to personalise their experience. This sets analytics cookies and records your interactions for these purposes. These cookies load only with your consent, which you can change or withdraw at any time in cookie settings.
Third-party domains contacted
cdn.yxper.comcollect.yxper.ioapi.yxper.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| _yx_id | Analytics | 12 months | Persistent identifier used to recognise returning visitors and link their behavioural events across sessions. |
| _yx_ses | Analytics | Session | Tracks the current session to group interactions and page views for analysis. |
| _yx_pers | Personalisation | 6 months | Stores personalisation state so the tool can adapt content to the visitor on later visits. |
| _yx_consent | Strictly necessary | 6 months | Records the visitor consent choices for Yxper analytics and personalisation cookies. |
Yxper collects user analytics data — you legally need a consent banner. Try FlowConsent free.
In a standard deployment Yxper sets analytics cookies and may store browser identifiers to recognise returning visitors and link their interactions across sessions. The exact names and durations depend on your configuration, so audit the live integration to confirm what is placed.
Yes. The analytics and personalisation cookies Yxper sets are not strictly necessary, so prior consent is required under Article 5(3) of the ePrivacy Directive before the script runs. The tool should stay blocked until the visitor accepts analytics and personalisation.
For setting and reading its analytics and personalisation cookies the basis is consent under Article 6(1)(a) GDPR combined with Article 5(3) ePrivacy. Legitimate interest is generally not sufficient for behavioural analytics and personalisation that recognise individuals across visits.
It may. Experience and analytics vendors often process data on infrastructure in the United States or other third countries, so personal data such as IP addresses and behavioural events may leave the EEA. Confirm the data location and transfer safeguards such as the EU US Data Privacy Framework or Standard Contractual Clauses with the vendor.
A DPIA is advisable where Yxper performs systematic behavioural analysis or personalisation that profiles visitors at scale, which can present a high risk. Document the data captured, whether profiling occurs, retention, transfers and the consent mechanism as part of the assessment.
Load Yxper only through a consent management platform so it fires after the visitor accepts analytics and personalisation. Disclose it in your cookie policy, sign a data processing agreement, enable IP anonymisation and minimisation options, set retention limits and test that declining consent stops all data collection.
Alternatives include privacy first analytics and experience tools that offer cookieless measurement, aggregated reporting or self hosting, which can reduce or remove the need for consent. Any tool that profiles visitors with non essential cookies still requires consent, so compare data flows before choosing.
List each Yxper cookie with its name, purpose and duration, classify it as analytics or personalisation, name the controller and processor, state the legal basis as consent, describe any international transfers and link to your consent settings. Review the entry whenever the configuration changes.