Using and controlling cookies with TwentyThree
The TwentyThree platform, webinars and video players use cookies as a part of the service. These cookies are part of managing security, performance, analytics and more, and when you deploy the platform for your organization you will have high degree of control of how cookies are set and used.
Categories: Necessary cookies or analytics cookies?
The platform uses a number of necessary cookies as a part of the product. These required cookies are used, for example, when a video editor logs in to the product; to remember when a video collector has been filled; or to secure access to webinars for registrants. The platform also uses necessary cookies to load balance traffic and optimize performance. Below and in the product these cookies are labeled as “necessary cookies”.
Additionally, the platform can be set up to make use of analytics cookies to track visitor usage patterns to use for example in contact profiles and for detailed video analytics. This includes visitor across across sessions along with referrer tracking and compilation of embed sources. If you choose only to use necessary cookies, some analytics information may become inaccurate. Below and in the product these cookies are labeled as “analytics cookies”.
These additional cookies serve not only to provide more accurate analytics, but can also greatly improve the user experience on the platform. For example, a user will be able to join a webinar directly even if registered days earlier.
In some cases the expiration time of a cookie determines whether it is functions as a necessary cookie for a single session – or as a long-lasting analytics cookie used to track usage across browsing sessions.
Types: Visitor cookies or login cookies
Cookies are used for three types of contexts:
- Login cookies: We use cookies for authentication and to secure access when editors and admins log in to work with video content and webinars. These cookies are set when logging in either with username and password or when using single sign-on. The cookies only apply to users that have access to log in to the platform. Login cookies are always necessary and never serve as analytics cookies.
- Visitor cookies: Cookies are also used to service web site, webinar and video visitors. A subset of cookies are necessary for the service while others are used for tracking and analytics.
- Load balancing cookies: The platform also uses necessary cookies to load balance traffic and optimize performance. Load balancing cookies are always necessary and never serve as analytics cookies.
Selecting category: Cookie settings for a workspace
Workspace administrators can select cookie settings for a workspace using the Privacy and GDPR Dashboard. It is possible to choose between two different modes:
- Necessary cookies only: When this option is selected, only cookies necessary for the functionality of the platform are used. In addition, all cookies will be set as session cookies unless the end-user explicitly opts to persist them for longer.
- Both necessary cookies and marketing cookies: In this mode, additional cookies are set for analytics and visitor tracking purposes, for example to remember the user identity and preference across browsing sessions.
When these settings are changed, the selected option start will having effect for future visits to platform.
Cookies set by the platform
Visitor cookies
| Cookie name | Target | Category | Purpose | Duration in "Necessary cookies" mode | Duration in "Analytics cookies" mode |
|---|---|---|---|---|---|
| uuid | Visitors | Necessary | Stores a unique identifier for current visitor, used for authentication to for example webinars and gated videos. When a workspace has Analytics cookies enabled, this cookie is remembered across sessions and used to build usage information across visits. | Session | 90 days |
| session_referer | Visitors | Analytics | Stores the website address that referred traffic to the video player. | - | Session |
User login cookies
| Cookie name | Target | Category | Purpose | Duration | Duration when user checks "Keep me logged in" |
|---|---|---|---|---|---|
| ad_user_login | Users | Necessary | Set when a user logs in using username/password or single sign-on | Session | 90 days |
| ad_user_login_secure | Users | Necessary | Set when a user logs in using username/password or single sign-on | Session | 90 days |
| api_base_url | Users | Necessary | The base URL for loading API content for the logged in user. | Session | 90 days |
| ad_secure_token | Users | Necessary | Set when a user logs in using username/password or single sign-on | Session | Session |
| ajs_anonymous_id | Users | Necessary | Used by TwentyThree to deliver onboarding and help within the administration portal. | Session | Session |
| ajs_group_id | Users | Necessary | Used by TwentyThree to deliver onboarding and help within the administration portal. | Session | Session |
| ajs_user_id | Users | Necessary | Used by TwentyThree to deliver onboarding and help within the administration portal. | Session | Session |
| tt_spots | Users | Necessary | Used by TwentyThree to make in page editing of Spots available to logged-in editors. | Session | 90 days |
Load balancing cookies
| Cookie name | Target | Category | Purpose | Duration |
|---|---|---|---|---|
| ad_session_id | Load balancing | Necessary | Technical cookie used to load balance traffic between servers. | 30 minutes |
Additional cookies when using Connect
The platform offers the ability to integrate with third-party products through Connect. A number of the integrated services use cookies as well. For example, Google Analytics, HubSpot, Marketo and other marketing services will be setting cookies when enabled. This means that you will need to ensure that additional services used alongside TwentyThree also adhere to your cookie policy.