Cookies are very small text files that are stored on your computer when you visit some websites.

We use cookies to help identify your computer so that we can tailor your user experience and recall where you are in the order process.

You can delete any cookies already stored on your computer and prevent your computer from receiving future cookies, but these may stop our service from functioning properly.

The following is strictly necessary in the operation of services.

Yieldify will:

The following are not strictly necessary, but are required to provide you with the best user experience and also to tell us which pages you find most interesting (anonymously).

Functional Cookies

This website will:

Targeting Cookies

Yieldify will:

Yieldify will not:

Names of cookies

For a basic campaign, the subset of cookies below will likely be dropped. When targeting more specific things, there may on occasion be other custom cookies used

yieldify_iv Initial visit cookie which can show overlay    Session
yieldify_visit Visit cookie that always appears when tag is live    1 day
yieldify_sale Sales tracking    28 days
yieldify_fb Sales tracking    Session
yieldify_isale Sales tracking    Session
yieldify_original_referrer Visitor origin    Session
yieldify_frequency_#### Frequency capping    14 days
yieldify_frequency_click#### Same as above but for clicks    Session
yieldify_basket Sales tracking    365 days
yieldify_st User journey tracking    20 Years
yieldify_stc User journey tracking    Session
yieldify_delay Frequency capping    30 Minutes
yieldify_tv User journey tracking    30 Days
yieldify_ab User journey tracking    Session/30 Days
yieldify_userinfo User info tracking    365 days
yieldify_dynamic_campaign User journey tracking    Session
yieldify_after_submit Frequency capping    Session
yieldify_yie_coupon For coupons    1 year
yieldify_ujt User journey tracking    Session

How is data being transferred between a client website and Yieldify?

Yieldify utilises the tag to send data through an iFrame via network requests that are triggered when an overlay is interacted with via “click” operators. These requests are sent encrypted over an SSL endpoint provided the host website is utilising the https protocol.

What data is stored and saved in a database?

• Order numbers

• Total Order Amount

• Data we have been asked to collect regarding sales

• Data that is willingly submitted by a user on an overlay.

What does Yieldify read in the session but not store in a database?

For more information:

start converting

Start Converting

Enter your website to receive a personalised demo.

start converting

Choose your country