The following cookies present on your pages are categorized as essential cookies:
| Name | Provider | Purpose | Expiry | Type | What happens if the cookie is blocked? |
| _it_ | Instapage Web Analytics | This is a third-party cookie that is used to set Snowplow’s network_userid identifier that would identify a visitor across different domains. |
365 days (NOTE: third-party cookie creation is blocked by most of the users, which means that some people won’t see it) |
Http, Secure |
The network user ID can’t be assigned to the visitor - that means that we won’t be able to track visitors across different pages. Because it is a third-party cookie it is nowadays usually blocked anyway. If the creation of the cookie would be blocked because the script execution would be blocked - the tracker won’t work. That means that no web analytics events would be collected. |
|
instap-spses.*
|
Instapage Web Analytics |
This cookie is a Snowplow session cookie. It helps us count visitors' sessions on the client-side.
|
30 min | JavaScript Secure |
If this cookie would be blocked, the Snowplow tracker cannot stitch different visitors' events into a session. If the creation of the cookie would be blocked because the script execution would be blocked - the tracker won’t work. That means that no web analytics events would be collected. |
| instap-spid.* | Instapage Web Analytics | This cookie is a first-party Snowplow’s domain cookie. It sets the domain_userid - identifier that identifies a user on the particular domain. With that, we distinguish if a user’s visit is unique or not. |
2 years (NOTE: ITP 2.1 introduced a 7-day cap on the client’s side (JavaScript) created cookies, so some users might have these cookies deleted sooner than at expiration time) |
JavaScript Secure |
If the creation of the cookie is blocked somehow a tracker cannot assign a domain user ID to the visitor. That means that the system won’t be able to distinguish new and returning visitors. If the creation of the cookie would be blocked because the script execution would be blocked - the tracker won’t work. That means that no web analytics events would be collected. |
| instapage-variant-<page_id> | Instapage Page Proxy | Cookie used for A/B testing purposes (Experiments). The cookie contains a randomly chosen variation name for the given experiment ID. It allows us to provide consistent behavior by serving the proper variation for a given user. | 365 days | Http, Secure | The A/B test lottery would be performed each time the client visits the landing page. That means that each time a visitor would revisit a page, he would get a random variation. |
| snowplowOutQueue_instapageSp_instapage-sp_post2 | Instapage Web Analytics | The cookie is created only if there was no Internet connection on the client side. It helps to save web analytics events to send them after the connection is restored. | |||
| snowplowOutQueue_instapageSp_instapage-sp_post2.expires | Instapage Web Analytics | The cookie is created only if there was no Internet connection on the client side. It helps to save web analytics events to send them after the connection is restored. | |||
| cf_clearance | Cloudflare | It is used to handle the security functionality that Cloudflare provides (SSL certificates and other page security measures) |
Instapage essential cookies are collected by default. Instapage collects them to ensure the proper basic functionality of the landing pages and they should not be blocked.
Optional cookies are used to track the actions and behavior of individuals. A cookie opt-out banner solution allows you to turn on the optional cookies based on an individual's consent.
To block any custom tracking that you might use on your landing page from firing until the visitor consents to being tracked, you can use our cookie bar: https://d.pr/WlYyw4
______________________