If you're using Ethnio web intercepts, this article contains details about exactly how Ethnio cookies work. Note that screeners that you send out as links, it's generally much simpler.
Chrome SameSite and ITP2.1
Here's what Chrome is changing. Ethnio will be adding two headers to the _ethnio_displayed cookie (info below) to ensure full compliance with the changes.
- SameSite=None – this tells Chrome that the Ethnio cookie does not belong to the site you are visiting.
- Secure – specifies that HTTPS is the only allowed type of site/URL.
Apple rolled out Intelligent Tracking Prevention (ITP 2.1) in 2019, which were updates to WebKit / Safari that block 3rd party cookies from being set and placed limits on 1st party cookies that are written by the document.cookie file. Ethnio fully supports this update, conceptually and technically, and retains 100% Safari compatibility for web intercepts.
Now on to Ethnio cookie technical info
By default, ethnio sets a cookie to prevent anyone from ever seeing a screener twice within 30 days for a given domain. But often for testing, it's easier to disable the cookies so you can test a screener a bunch without having to clear your cookies every time. Otherwise, you probably always want to leave this on. Keep in mind it also applies to direct links, so people can't fill out your screener multiple times. Here's some technical information about the cookie:
Cookie Name: _ethnio_displayed
Purpose: This cookie is set once a visitor sees an Ethnio screener on a given domain (for ex, customer.com) to prevent that visitor from seeing another Ethnio screener on that domain for 30 days. The main purpose of this cookie is to make sure site visitors aren’t annoyed by multiple screener invites. You can disable cookies under Screeners >> Publish
Duration: 30 days
This setting is under screeners >> publish.
All Ethnio cookies are set with 'secure' and 'httpOnly' attributes