Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Yieldify is a UK based customer journey and conversion rate optimisation platform that uses a JavaScript tag to track visitor behaviour and trigger personalised overlays, popups and messages.
Yieldify is a customer journey and conversion rate optimisation platform based in the United Kingdom. Website operators add a small JavaScript tag to their pages, which lets Yieldify observe how visitors browse, scroll, hesitate and leave, then trigger overlays, popups and personalised messages at the right moment.
Yieldify helps ecommerce and other websites increase conversions by personalising the on site experience. Its JavaScript tag loads in the visitor browser and reacts to behaviour such as scroll depth, inactivity, exit intent, cart abandonment and returning visits. Based on these signals it serves targeted overlays, popups and inline messages, and it can build visitor segments to tailor what each person sees.
To recognise visitors and remember their journey, Yieldify sets cookies in the browser, typically including a visitor identifier, a session identifier and an approximate location value. It collects behavioural data such as pages viewed, scroll depth, mouse movement linked to exit intent, time on page, device and browser details and interactions with the experiences it displays. This information is used to profile visitors, assign them to segments and decide which message to show.
Because Yieldify identifies and profiles individual visitors, the behavioural data it processes is personal data under the GDPR and the UK GDPR. The cookies it stores and reads on the user device fall under the ePrivacy Directive, which requires prior consent for any cookie that is not strictly necessary. As the website operator you are the controller for this processing and must be able to demonstrate a valid legal basis and proper transparency.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Yieldify behavioural tracking and personalisation cookies are not strictly necessary, so you must obtain freely given, specific, informed and unambiguous consent before the tag starts tracking. In practice this means the Yieldify tag should only fire once the visitor has accepted the relevant category in your consent banner, and visitors must be able to refuse or withdraw consent as easily as they gave it. Consent (Art. 6(1)(a) GDPR) is the appropriate legal basis here.
Yieldify is operated from the United Kingdom, which the European Commission recognises as providing an adequate level of protection, so transfers from the EEA to the UK are generally permitted. Some processing may nonetheless involve subprocessors located in the United States or other third countries; where that happens the transfers should be covered by Standard Contractual Clauses and, for UK data, the International Data Transfer Addendum, together with any necessary supplementary measures.
Block the Yieldify tag until consent is captured, ideally through your consent management platform, and document the integration. List the Yieldify cookies in your cookie policy with their purpose and duration, describe the behavioural tracking and profiling in your privacy notice, sign a data processing agreement with Yieldify and review its subprocessors and transfer safeguards. Where the tracking is extensive, carry out a data protection impact assessment before going live.
Websites using Yieldify must obtain user consent under GDPR regulations.
DPIA considerations
Yieldify performs behavioural tracking and visitor profiling to build segments and personalise overlays, which can amount to systematic monitoring of website visitors. A data protection impact assessment is recommended where tracking is extensive or combined with other identifiers. Document the categories of behavioural data collected, the retention periods and the safeguards applied to any transfers outside the UK and EEA.
Sample consent text
We use Yieldify to analyse how you browse our site and to show you personalised offers and messages; with your consent it sets cookies and tracks your behaviour, including exit intent.
Third-party domains contacted
yieldify.comcdn.yieldify.comtag.yieldify.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| yieldify_visitor | First party | 1 year | Stores a unique visitor identifier used to recognise returning visitors and build behavioural profiles and segments. |
| yieldify_session | First party | Session | Identifies the current browsing session to track behaviour during a single visit and trigger the right experiences. |
| yieldify_location | First party | 1 year | Stores an approximate location value used to tailor and target the messages and overlays shown to the visitor. |
| yieldify_campaigns | First party | 6 months | Records which Yieldify experiences or campaigns the visitor has already seen to avoid repetition and control frequency. |
Yieldify uses cookies for user preferences — inform visitors with a consent banner.
Yieldify typically sets a small number of first party cookies in the visitor browser, including a visitor identifier used to recognise returning visitors, a session identifier used to track the current visit and an approximate location value. These cookies support behavioural tracking, segmentation and the personalised experiences that Yieldify displays, so they are not strictly necessary.
Yes. Yieldify relies on behavioural tracking and personalisation cookies that are not strictly necessary, so under the ePrivacy Directive and the GDPR you must obtain prior, freely given and informed consent before the tag starts tracking. The Yieldify tag should only fire once the visitor has accepted the relevant category in your consent banner.
The appropriate legal basis is consent under Art. 6(1)(a) GDPR, combined with the consent requirement of the ePrivacy Directive for storing and reading cookies. Because the processing involves profiling and personalisation rather than a strict necessity, legitimate interest is generally not an adequate basis for this kind of tracking.
Yieldify is operated from the United Kingdom, which benefits from a European Commission adequacy decision, so EEA to UK transfers are generally permitted. Some processing may involve subprocessors in the United States or other third countries, in which case the transfers should be covered by Standard Contractual Clauses and, for UK data, the International Data Transfer Addendum.
A data protection impact assessment is recommended and may be required where Yieldify is used for systematic monitoring or large scale profiling of visitors. Assess the scope of the behavioural tracking, the segments created and any combination with other identifiers, and document the safeguards and retention periods before going live.
Integrate Yieldify behind your consent management platform so the tag is blocked until the visitor consents, list its cookies in your cookie policy, describe the tracking and profiling in your privacy notice, and sign a data processing agreement with Yieldify. Review its subprocessors and transfer safeguards as part of your due diligence.
Alternatives include other customer journey and conversion optimisation tools such as Dynamic Yield, Insider, OptiMonk, Optimizely and Nosto. When comparing them, look at where data is hosted, whether a cookieless or consent friendly mode is offered, the subprocessors used and the clarity of their data processing terms.
Yes. You should list the Yieldify cookies in your cookie policy with their name, purpose and duration, and explain in your privacy notice that Yieldify carries out behavioural tracking and profiling to personalise the experience. Keep these disclosures up to date if the cookies or their durations change.