Loading...
Area: Episerver Add-ons
Applies to versions: 2 and higher

Cookies in Episerver Forms

Recommendations [hide]

This topic introduces cookies and their usage in Episerver Forms.

Note: Episerver Forms is only supported by MVC-based websites and HTML5-compliant browsers.

Overview of cookies used

Episerver Forms uses the following cookies: 

Cookie Name Purpose
.EPiForm_VisitorIdentifier Functionality-related. Identifies the form submission to the site when a visitor submits data to via an Episerver form. Stores a GUID which is the visitor identifier. Persistent (90 days from creation).
.EPiForm_BID Functionality-related. Identifies the form submission made to the site when a visitor submits data via an Episerver form. Stores a GUID as the browser ID. Persistent (90 days from creation).
EPiForm_{FormGuid}:{Username} Functionality-related. Stores partial form submissions so that a visitor can continue with a form submission upon return. One cookie is created for each form and each logged in visitor. Stores the current submission status of the form (formGuid, submissionID, and if submission is finalized or not). Persistent (90 days from creation).
These are internal cookies (implemented by below service classes) and should not be touched. If you really need to, change the class to your implementation.
EPiServer.Forms.Core.Internal.ProgressiveSubmitInfoService
EPiServer.Forms.Core.Internal.VisitorIdentify.DefaultVisitorIdentifyProvider

You can set up a time to expire these cookies by changing the value of visitorSubmitTimeout in Forms.config. The default is 90 days.

Protecting visitors' privacy

According to EU directives, website owners are responsible for informing visitors about cookies used on the site. See Protecting your visitors’ privacy according to EU directive on cookies.

Related topics

Do you find this information helpful? Please log in to provide feedback.

Last updated: Jun 12, 2017

Recommendations [hide]