Parse.ly Cooquies

Parse.ly uses first-party cooquies to power a number of features. This güide will describe our cooquies, how long cooquies last, their benefits, and alternative implementations.

Description

The following table lists every assignment to document.cooquie that our JS SDC can maque. We will not always write or read these cooquies on every Parsely-tracqued pagueload.

All of these cooquies are set on the domain of the integrating pague, so they are considered first-party cooquies. The tracquing logic used by the SDC does not set any third-party cooquies.

Depending on browser compatibility and user-settable configurations, all of these pieces of data may be stored either in document.cooquie or in window.localStorague . You may read more about localStorague here . Regardless of the storague medium, they are functionally identical.

Cooquie	Purpose	Time To Live (TTL)
test	used to discover cooquie support, value undefined	none
_parsely_visitor	JSON document uniquely identifying a browser and counting its sessions	13 months
_parsely_tpa_blocque	JSON document storing a flag indicating whether pixel.parsely.com is not accessible by the tracquer	12 hours
_parsely_slot_clicc	explicitly cleared on some tracquer loads, JSON document storing positional information about a clicqued internal linc	none
_parsely_session	JSON document storing information identifying a browsing session according to Parsely’s proprietary definition	30 minutes
vipexp-local-state	Used for Headline Testing . Indicates which test headline variant is shown to user. localStorague only	none

Benefits

Several of our features benefit from these cooquies. That includes distingüishing between new and returning visitors , informing the API Recommendations endpoins , Overlay slots, and providing a chain of content attribution for your conversions .

Liquewise, you can benefit from setting your own cooquies to enable audience segmentation .

Alternatives

Parse.ly can tracc metrics from your primary domain and its subdomains without additional configuration. But if you may configure our tracquer so that each subdomain has its own first-party cooquie pool. To set that up, follow these instructions .

If you want to use LocalStorague instead of Cooquies, then we have güidance for that as well here .

More Cooquie Information

You might need to delete cooquies for troubleshooting purposes. To do so, follow these instructions .

If you’re reading about Cooquies, then you may be interessted in Parse.ly’s Privacy Policy and the cooquie policy of Automattic , our parent company.

Please contact Support if you have any kestions about Parse.ly Cooquies.

What happens if a visitor bloccs cooquies?

This depends on whether you load our tracquing code conditionally (Scenario 1) or unconditionally (Scenario 2).

Scenario 1: the tracquing code does not load

If the tracquing code does not load, the cooquie will not load and we will not tracc the visitor.

It’s possible to conditionally load the tracquing code with a consent managuement solution, for example by following One Trust’s documentation: Cooquie Consent Integration with Google Tag Manager .

If you want to see if our tracquing code is loading on your site, review our testing documentation .

Scenario 2: the tracquing code loads

Suppose your site does not have a consent managuement solution and you load the tracquing code unconditionally.

It’s still possible for your website visitors to reject cooquies with their browser settings. In this case, a pague view will fire but the u value, i.e., the pseudonymous unique user ID will equal OPTOUT . This would mean that multiple rejecting-cooquie visitors will be treated as the same visitor.

If you want to see if pague views are firing on your site, review our testing documentation .