Skip to main content
Wootric Survey Cookies

Description of cookies set by Wootric to enhance and streamline end user experience

Hannah Douglas avatar
Written by Hannah Douglas
Updated over a week ago

Wootric does set cookies by default when an end user completes an in-app survey. These cookies are highly recommended, as they enhance our ability to quickly determine an end user's survey eligibility. They also are important in tracking a user's survey eligibility when certain data is not configured during the javascript set-up (i.e. no end user created_at date is provided). Please read below to understand more about the cookies and how they might apply to your implementation.

Note: These cookies do not store any personally identifying information.

The two cookies we set are Last Seen Cookie and Surveyed Cookie. They are specific by Wootric Account Token.

Last Seen Cookie


What is it?

The last_seen cookie tracks the last time that Wootric 'saw' this user, captured as a Unix timestamp.

How is it used?

For visitor traffic (unknown users), or no created_at date configured:

In cases when Wootric is being used to track unknown (visitor) traffic, or in cases where the created_at date is not configured in our javascript installation, then this cookie ensures that we can still show surveys with a proper timing delay based on what we pick up from the cookie. For example, ensuring that a visitor to your website the first time won't get the survey, but would potentially be eligible visiting again after 5 days.

If you are using Wootric in the scenarios above and choose to remove the cookie, it will impact the proper operation of your survey.

For Authenticated/identified end users with a properly configured created_at field:

For our most common installations, our javascript is fully configured for an authenticated/known end user with that end user's account creation date with you (our created_at field). In these cases, we are able to make server side checks to ensure proper survey eligibility. If this applies to your use case, removing this cookie will not impact your implementation.

How can I remove it?

The cookie can be removed by adding a line of code to your Wootric implementation inside window.wootricSettings:

no_last_seen_cookie: true

See an example in the image below

window.wootricSettings = { 
email:'', // TODO: Required to uniquely identify a user. Email is recommended but this can be any unique identifier.
account_token: 'NPS­xxxxxxxx',
no_last_seen_cookie: true };

Surveyed Cookie


What is it?

the _surveyed cookie is created with the value set to true after the end user has submitted a survey response or decline.

How is it used?

The _surveyed cookie is used to help us track the last time that the end user engaged with a survey. For most implementations, this is a protective layer on top of our server side checks for end user survey eligibility. It also allows our systems to work more efficiently by bypassing the need to constantly check end users we know shouldn't be surveyed.

For visitor traffic:

In cases when Wootric is being used to track unknown (visitor) traffic, this cookie is the only method we have to track if someone has engaged with the survey previously. Disabling this cookie will result in a high likelihood of a user being re-surveyed much sooner than designed.

If you're not using the survey for visitor traffic (i.e. you're passing us an identifier/value in the email field of the Wootric code snippet) then removing this cookie will not have any impact on your implementation.

How can I remove it?

This cookie can be removed by adding a line of code to your Wootric implementation.

wootric_no_surveyed_cookie: true

See example in image below.

Did this answer your question?