Cookie Policy

Jobs in Ministry Limited (“we”, “us”, “our”) is responsible for the website www.jobsinministry.co.uk

Our website uses cookies and other similar technologies, which may include pixels, plugins, scripts, tags and device fingerprinting (which we collectively refer to as “cookies” in this Cookie Policy).

We use cookies for many reasons, for example to distinguish you from other users of our website or to see how you interact with our website. This helps us to provide you with a good experience when you browse our website, it also allows us to improve our website and it allows us to re-engage with our audience through advertisements on other websites.

This Cookie Policy describes:

  • What are cookies;
  • Our use of cookies;
  • How you can manage cookies used on our website;
  • Privacy;
  • Further information; and
  • Changes to this Cookie Policy.

What are cookies?

A cookie is usually a small file of letters and numbers that we store on your browser or the hard drive of your computer, smart phone, tablet or other electronic device. However, they can take a number of different forms, such as pixels, plugins, tags scripts and combinations of these technologies to allow ‘device fingerprinting’. Cookies use information that is transferred to or read from your device’s hard drive. Some cookies may collect personal data about you. You can find out more information about cookies and pixels on the Information Commissioner’s Officer (ICO) website (www.ico.org.uk).

First Party and Third Party Cookies and Pixels

Some cookies and pixels are referred to as “first party” which means they are placed by the website you are visiting – so in our case first party cookies and pixels are placed by Jobs in Ministry’ own website. “Third party” cookies and pixels are placed by other organisations (with our permission) via the Jobs in Ministry’ website, such as advertisers and social media platforms. They work by collecting information from your device and passing it directly back to the third party.

Our use of cookies

We want you to understand the different types of cookies that are used on our website. These may be set by us, or by third parties who provide functionality embedded in or connected to our website. We use a variety of types of cookies for the following purposes:

  • Strictly necessary (essential) cookies: these are cookies strictly necessary for the provision of our website to you, for example, cookies that enable website content to be delivered securely and efficiently. Without these cookies, the website may fail to operate properly.
  • Functionality cookies: these cookies are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region, search preferences, or your login details, if you choose this). Without these cookies, some parts of the website may not work as we intend them to.
  • Performance cookies: these cookies allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily. Typically, these cookies do not seek to identify a particular visitor and the analysis is done at an aggregate and therefore anonymous level. However, in some cases you may remain identifiable because of the inclusion of one or more pieces of information.  For instance, a member ID is assigned to you and we may use this to associate you with your use of the website where we need to resolve a complaint.  For more information on how we process any personal data collected on the site, please read our privacy policy.
  • Targeting & advertising cookies (including ad measurement): these cookies are used to deliver adverts more relevant to you and your interests, both on and off our website. They are also used to limit the number of times you see an advertisement as well as help measure the effectiveness of the advertising campaign. These cookies are usually placed by trusted third parties (such as advertising networks) who we have a relationship with. They remember that you have visited a website and this information is shared with other organisations such as advertisers. These third parties combine data that we share with them with data from other sources, such as their own websites. This combined data can then be used to ensure that we can better target our visitors with advertisements for roles on our website that are more relevant to you and others. For more information, visit www.youradchoices.com. Please note that by opting out of receiving targeted advertisements on one browser, device or app will not necessarily opt you out of all such adverts from all browsers, devices or apps.

You can find more information about the individual cookies we use on our website and the purposes for which we use them in the table at the end of this policy.

How to withdraw your consent to the use of cookies

You may withdraw your consent to targeting and advertising cookies at any time by selecting the appropriate settings in our consent management platform.

You can block most cookies (except for Flash cookies) by activating the setting on your browser that allows you to refuse the setting of all or some cookies. However, if you block all cookies (including essential cookies) you may not be able to access all or parts of our services, or you may experience reduced functionality when accessing certain services. The procedure to block cookies depends on which internet browser you are using:

Internet Explorer: To prevent new cookies from being installed and delete existing cookies:

 http://windows.microsoft.com/en-GB/internet-explorer/delete-manage-cookies

 Firefox: To prevent new cookies from being installed:

https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences

 Or to delete existing cookies:

https://support.mozilla.org/en-US/kb/delete-cookies-remove-info-websites-stored

Google Chrome:  To prevent new cookies from being installed and delete existing cookies:

https://support.google.com/chrome/answer/95647?hl=en

Safari:  To prevent new cookies from being installed and delete existing cookies:

http://help.apple.com/safari/mac/8.0/#/sfri11471

Where can I find more information about cookies?

Find out more about cookies, including how to disable/enable and delete them, at the following website www.aboutcookies.org.You can opt-out of receiving cookies from a range of ad servers by visiting www.youronlinechoices.com and following the instructions provided.

Privacy

We are committed to using cookies fairly and in accordance with applicable privacy rights. Please read our Privacy Policy for further information on how our use of cookies may involve processing your personal data.  Our Privacy Policy can always be accessed at the foot of our website landing page www.jobsinministry.co.uk).

Further information

If you have any queries relating to this Cookie Policy, please contact us via the email address clementina@jobsinministry.co.uk or by writing to us at:

Data Protection Officer, 20-22 Wenlock Road, London. England N1 7GU

Changes to this Cookie Policy

If this Cookie Policy changes, the revised policy will include a new effective date and will be posted on this page. Please check back regularly to keep informed of updates.

Last Updated: 09 Mar 2023

Table of Cookies used on our website

Essential Cookies

Cookie Name

Duration

Purpose

CONSENTMGR

1 year

Used to capture that the cookie consent prompt has been shown and closed.

SoftLoginCookie

1 year

Encrypted value to identify returning users

SoftLoginDiagnostics

1 year

Encrypted soft login diagnostics

AWSELB

Session

Cookies from AWS load balancer, for sticky sessions(client will be routed to the same server, which was used for the previous requests)

AWSELBCORS

Session

Cookies from AWS load balancer, for sticky sessions(client will be routed to the same server, which was used for the previous requests)

AWSALBTGCORS

Session

cookies from AWS load balancer, for sticky sessions(client will be routed to the same server, which was used for the previous requests)

BIGipServerccstore-prod-zdba_oracleoutsourcing_com_http

Session

The BIGIP cookie is an HTTP Only cookie that maintains a connection to a single application instance. This cookie is not accessible from scripts and contains no personal data. This cookie expires at the end of the session.

BIGipServercloud-commerce-visit_oracleoutsourcing_com_http

Session

The BIGIP cookie is an HTTP Only cookie that maintains a connection to a single application instance. This cookie is not accessible from scripts and contains no personal data. This cookie expires at the end of the session.

BrowserId

1 year

Used to log browser sessions/visits for internal-only security use cases.

Inst

Session

Used to optimize routing to the user’s instance.

JSESSIONID

Session

The JSESSIONID cookie, which has a life that lasts only until the user’s browsing session ends, helps the server to manage user sessions. It is a standard Java servlet container cookie. While not accessible to scripts, this cookie can be deleted from the client-side. However, the cookie will be re-sent during the next request from the user.

This cookie tracks each request from the same browser, ensuring that the same session data is available on the server side. It does not contain any personal data. You must include this cookie in the necessaryCookies list, or else WebLogic will create new sessions for every request that comes in.

oauth_token_secret-storefrontUI

Session

The oauth_token_secret-storefrontUI cookie is necessary for storefront user interface operations, as it is used to store the OAuth token of the user that is logged in and keeps the shopper’s login token active during page reloads and multiple tab access. This cookie does collect personal data in the form of the profileID. While the cookie is accessible from scripts, it cannot be deleted from the client-side. If you delete this cookie, shoppers may have to log in again after opening new tabs or refreshing pages. Deleting this cookie would also cause some checkout payment flows to fail when a shopper gets redirected to an external payment site like PayPal. When the browser gets returned to the storefront, the shopper’s authentication state is lost and the checkout process cannot proceed. You should add this cookie to the necessaryCookies list.

occsRecCurrencyCode

Session

These hold the current price list group and currency code for this user. This is sent to the Recommendations service so it can know that a price value of 50 is USD$50 or EUR€50, which are very different. Recommendations use prices as part of its recommendations algorithm. These do not contain personal information: if our site only has one price list and one currency, all requests will have the same value.

occsRecPricelistGroupId

Session

These hold the current price list group and currency code for this user. This is sent to the Recommendations service so it can know that a price value of 50 is USD$50 or EUR€50, which are very different. Recommendations use prices as part of its recommendations algorithm. These do not contain personal information: if our site only has one price list and one currency, all requests will have the same value.

RecruiterAuthCookie

Session

An expression of authentication and identity, encrypted, identifies the user (by member ID), company ID & identifies the user roles, used by apps eg CVDB reporting.

_abck

12 months

This is a long-term session cookie that controls data collection and detects clients attempting to replay cookies.

Ak_bmsc

2 hours

Akamai Antibot adds some fields to request (traffic originating from customer) upon bot detection

SoftLoginCookie

1 year

Encrypted value to identify returning users

SSOSessionIndex

01/01/2125

Set when user logged through SSO provider which contains the session Index + MemberId which has base64 encoded GUID and uses “FormsAuthentication.Encrypt” to encrypt the values

AuthCA

15 minutes

The hard login token is a JWT which lasts for a short time, and does not require connection to a database to validate the users login session. This token identifies who the user is, and is cryptographically signed to allow detection of tampering. This token is essential to maintaining a logged in state.

AuthCARefresh

30 minutes

The refresh token is used to generate a new Hard login token. The refresh token is long life and is an identifier linking to data stored in the database relating to a users “session”. This token is essential to maintaining a logged in state.

SoftLoginCA

90 days

The soft login cookie is a JWT with a long life and limited use cases. It allows the system to recognize who the user is, and is cryptographically signed to detect tampering.

Functionality Cookies

Cookie Name

Duration

Purpose

Applications_counter

42 days

Increments the applications made on this browser

appliedJobs

Session

used on details and results pages to show users that they have already applied for these jobs

INEU

1 year

Stores if user is in EU

IsFirstCvUpload

Session

Stores if session resulted in first CV upload for candidate

isMobile

Session

Flags if session is on Mobile device

JBM_COOKIE

1 year

Stores Saved Jobs locally to device

LOCATIONJOBTYPEID

1 year

Stores country location based on IP

OCAActive

Session

Encrypted value to determine if user has One click apply enabled

PJBJOBSEEKER

1 year

Tracks user as a JobSeeker

SavedJobsDoneInitialMergeOnLogin

30 years

Controls the sync with server side storage of SavedJobs

SearchKeywords

Session

Stores the search keywords

SearchResults

Session

Stores list of jobs returned form search

TravelTimeUsage

Session

“Stores users interaction with Travel time functionality on job details

TravelTimePostCode

1 year

Stores users postcode for Travel time calculation on job details

atgRecVisitorID

Expires 01/01/2038

This is a persistent cookie that contains an opaque ID and is used to recognize a visitor across separate visits to your website.

bm_sv

2 hours

Akamai bot manager / Fraud prevention.

bm_sz

4 hours

is a short-term session cookie (4 hrs) that identifies user session and duration, and records user behaviour.

EETrViID

Session

The EETrViID cookie is an Oracle WebLogic cookie that stores the Visitor ID. It does not contain any personal data.
This cookie cannot be deleted, and therefore cannot be modified by JavaScript in the browser. This cookie does not need to be added to the necessaryCookies list.

intercom-idipgwe0mp

270 days

Anonymous visitor identifier cookie.

intercom-sessionipgwe0mp

7 days

Identifier for each unique browser session.

JSAUTH

Session

Used to decide if user is logged in

SessionCookie

Session

Stores SSA session. Tracks user session for behaviour

read_posts

1 year

Stores editorial pieces read

percentage_

1 year

Stores the percentage an editorial piece has been read

post_completed_exclude

1 year

Stores editorial pieces that have been 100% read and excludes them from “Popular” and “Trending” lists

posts_read_exclude

1 year

Stores editorial pieces a user has chosen to exclude from “Continue or read again” list

RecogniserCA

90 days

The recogniser token allows us to recognise a register user who is not signed in to the site. It will be issued on login along with the hard / soft login tokens.

MagicLinkCA

30 mins

The magic link token most likely will not actually be set as a cookie. This is a JWT token which is cryptographically signed and can be exchanged for a set of login tokens (hard / refresh / soft) providing the signature is valid. This token is designed to be sent in emails and has a short lifetime to minimize risks.

SetPasswordCA

90 mins

The set password token will also most likely not be a cookie. This token is only used for the purpose of changing a forgotten password. It is cryptographically signed and can be verified by the endpoint responsible for changing the password. It has a relatively short lifetime to minimize risks, yet long enough that if email delivery is slow the token will still be valid long enough to be useful.

Performance Cookies

Cookie Author

Cookie Name

Duration

Purpose

Hotjar

_hjAbsoluteSessionInProgress

30 minutes

This cookie is used to detect the first page view session of a user. This is a True/False flag set by the cookie.

_hjFirstSeen

30 mins

identifies a new user’s first session on a website, indicating whether or not Hotjar is seeing this user for the first time.

_hjid

365 days

Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behaviour in subsequent visits to the same site will be attributed to the same user ID.

_hjTLDTest

Session

When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.

_hjIncludedInPageviewSample

30 minutes

This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s pageview limit.

Adobe target

check

Session

A simple test value used to determine if a visitor supports cookies. Set each time a visitor requests a page.

mbox

2 years

Adobe Target uses cookies to give website operators the ability to test which online content and offers are more relevant to visitors.

Adobe analytics

gpv_pn

30 minutes

Stores analytics variable value from previous page.

s_cc

Session

Adobe Site Catalyst, determines if cookies are enabled in browser.

s_fid

5 years

Fall-back for s_vi cookie. Used to identify visitors.

s_ppv

Session

Adobe Site Catalyst, contains name, highest percentage of page viewed, initial percentage viewed and highest number of pixels (heightwise) seen on previous page.

s_ppvl

Session

Adobe cookie to store percentage of page displayed to user

s_sq

Session

This cookie is set and read by the JavaScript code when the ClickMap functionality or the Activity Map functionality are enabled; it contains information about the previous link that was clicked on by the user.

s_vi_PWFSPWLMFVHWLWBOILAPBSSOJx40BWJLMWFPW

2 years

Same as s_vi – Unique visitor ID time/date stamp.

sc_vid

5 years

Visitor ID for Adobe analytics.

Tealium

TAPID

1 year

Sends visitor data from the website and app to our customer data platform for processing. These data collection requests rely on the first-party cookie, utag_main_v_id , but might also use a third-party cookie named TAPID.

Oracle CommerceCloud

xdpzdba0c0

01/01/2038

xdpzdba0c0_100003

xdpzdba0c0_1000038

xdpzdba0c0_100005

xdpzdba0c0_100006

xdpzdba0c0_100007

xdpzdba0c0_2200173

xdpzdba0c0_900012

xdpzdba0c0_900047

xdpzdba0c0_900048

xdpzdba0c0_900050

xdpzdba0c0_siteUS

xdszdba0c0

xdszdba0c0_100005

xdszdba0c0_800006

xdszdba0c0_siteUS

xdtzdba0c0

xdtzdba0c0_100003

xdtzdba0c0_100005

xdtzdba0c0_100006

xdtzdba0c0_siteUS

xvpzdba0c0_siteUS

These cookies are generated by Visitor ID services and track the visits, which are site-specific.

Other

TJG-Engage

42 days

Fresh Engaged Retargetable User (FERU) cookie updated every time user views results or details page.

TJG-Accnt-Type

7 days

Used to store whether the user is a self-serve customer or has an account managed contract

Utag_main

1 year

Stores Tealium data

AnalyticEventsToBeTriggered

Session

This cookie contains the AA event names that is added when recruiter login successful.

AnonymousUser

30 years

Tracks anonymous users to record behaviour data.

FreshUserTemp

1 hour

Flag for users fresh to site.

user_cookie

10 years

This has been set when user successfully logged in, which determines user is an existing customer and mainly used for AB Testing.

Targeting or Advertising Cookies (including ad measurement)

The following cookies are set by our trusted third parties for the purposes of serving you advertisements away from our site.

Cookie Author

Cookie Name

Duration

Purpose

Adalyser

__adal_ca

6 months

__adal_cw

30 days

__adal_id

2 years

__adal_ses

session

These Adalyser (TV) cookies take a snapshot of web traffic around the time an advert is aired on television. These cookies allow us to effectively measure the resulting change in traffic volumes from our TV advertising to measure Ad effectiveness.

Google

__gads

390 days

Advertising cookies (e.g., cookies named ‘__gads’ or ‘__gac’) may be set on the domain of the site you’re visiting. Unlike cookies that are set on Google’s own domains, these cookies can’t be read by Google when you’re on a site other than the one on which they were set. They serve purposes such as measuring interactions with the ads on that domain and preventing the same ads from being shown to you too many times.

_ga

2 years

Used to distinguish users.

_gid

24 hours

Used to distinguish users.

G_ENABLED_IDPS

Expires 31/12/9999

Used for Google Single Sign On.

IDE

2 years

One of the main advertising cookies on non-Google sites is named ‘IDE‘ and is stored in browsers under the domain doubleclick.net.

NID

6 months

Google uses cookies like NID and SID to help customize ads on Google properties, like Google Search. For example, we use such cookies to remember your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This helps us to show you customized ads on Google.

ANID

12 months

One of the main advertising cookies stored in google.com is called ANID. We use other cookies with names such as DSID, FLC, AID, TAID, and exchange_uid. Other Google properties, like YouTube, may also use these cookies to show you more relevant ads.

OTZ

1 month

A cookie used by Google Analytics that provides an aggregate analysis of Website visitors.

UULE

6 hours

These cookies are used to collect information about how visitors use our Site. We use the information to compile reports and to help us improve the Site. The cookies collect information in an anonymous form, including the number of visitors to the Site, where visitors have come to the Site from and the pages they visited. If you do not allow these cookies we will not be able to include your visit in our statistics. You can read the full Google Analytics privacy policy at:
http://www.google.com/policies/privacy/.

Facebook

_fbp

90 days

When the Facebook pixel is installed on a website, and the pixel uses first-party cookies, the pixel automatically saves a unique identifier to an _fbp cookie for the website domain if one does not already exist.

fr

90 days

This cookie is used to deliver, measure and improve the relevancy of ads, with a lifespan of 90 days.

Verizon

A3

12 months

Used to track the post-click experience of users coming to totaljobs.com via Verizon advertisements and enable Jobs in Ministry to understand which audience segments are best to target for Jobs in Ministry.

Microsoft

ANON

6 months

Contains the ANID, a unique identifier derived from your Microsoft account, which is used for advertising, personalisation, and operational purposes. It is also used to preserve your choice to opt out of interest-based advertising from Microsoft if you have chosen to associate the opt-out with your Microsoft account.

MUID

390 days

Microsoft Advertising uses the Microsoft User Identifier (MUID) to help count valid clicks.

NAP

99 days

Contains an encrypted version of your country, postcode, age, gender, language and occupation, if known, based on your Microsoft account profile.

_uetsid

1 day

This cookie is used by Bing to determine what ads should be shown that may be relevant to the end user perusing the site.

_uetvid

18 days

A unique, anonymized visitor ID, assigned by UET, representing a unique visitor. UET stores this data in a first-party cookie named “_uetvid”.

Lotame

_cc_aud

269 days

_cc_aud collects and stores Lotame audience data.

_cc_cc

269 days

_cc_cc collects anonymous user session data related to the user’s website visits, such as the number of visits, average time spent on the website and what pages have been loaded.

_cc_dc

269 days

_cc_dc collects and stores anonymous statistical data related to the user’s website visits, such as the number of visits, average time spent on the website and what pages have been loaded.

_cc_id

269 days

_cc_id is a Lotame persistent unique user identifier.

Awin

aw21134

30 days

Set when you click on one of our links. Stores IDs for referring website, advertisement on which you clicked, group of advertisements to which the advertisement belongs, time you clicked on it, ID for the type of advertisement, ID for the product and any reference the referring site adds to the click.

bId

1 year

Sets a browser-specific ID to identify a new click on the same browser. Cookie expires after one year.

Adobe Audience Manager

demdex

180 days

Audience Manager sets the demdex cookie to assign a unique ID to a site visitor. The demdex cookie helps Audience Manger perform basic functions such as visitor identification, ID synchronization, segmentation, modeling, reporting, etc.

dpm

180 days

DPM is an abbreviation for Data Provider Match. It tells internal, Adobe systems that a call from Audience Manager or the Adobe Experience Cloud ID Service is passing in customer data for synchronization or requesting an ID. This is the most common demdex.net call you’ll see from Audience Manager or the Adobe Experience Cloud ID Service.

Twitter

guest_id

879 days

This domain is owned by Twitter. The main business activity is: Social Networking Services. Where Twitter acts as a third party host, it collects data through a range of plug-ins and integrations, that is primarily used for tracking and targeting.

personalization_id

730 days

This domain is owned by Twitter. The main business activity is: Social Networking Services. Where twitter acts as a third party host, it collects data through a range of plug-ins and integrations, that is primarily used for tracking and targeting.

Bombora

pi

1 year

pi is the Bombora cookie ID which is stored for 1 year and allows us to aggregate behaviour data under a single device profile.

tp

24 hours

tp is a temporary cookie stored for 24 hours to assist with daily unique user counting.

u

15 seconds

u is a temporary cookie stored for 15 seconds that helps us with unique page view counting.

Trade Desk

TDCPM

1 year

Trade desk cookie partner mapping: It contains data denoting whether a cookie ID is synced with our partners. ID syncing enables our partners to use their data from outside our trading platform on the platform.

TDID

1 year

Trade Desk write an ID called TDID into the toplevel cookie in the Adserver.org domain and its sister ad-serving domain Adsrvr.org along with the metadata describing the status of mapping that cookie to partners. In H2 2017, TTD started making the TDID available for other parties to use it as their primary ID to better reflect the collaborative intent of the domain. The implementation is identical, and TTD continues to own and operate the domain. It is a Google AdX-approved fourth-party domain, it is included in the National Advertising Initiative (NAI) optout tool, and it has a privacy policy to which all adopters must adhere.

Tealium

TealiumCampaignPersist

Session

Used to store the latest marketing campaign code so that we can optimise based on traffic channels.

Xandr

anj

90 days

This cookie contains data denoting whether a cookie ID is synced with our partners.ID syncing enables our partners to use their data from outside the Platform on the Platform. (See our platform privacy page for more info.)

uids

90 days

The uids cookie contains a base 64 encoded JSON object which contains external unique randomlygenerated values that enable other Prebid Server demand partners to distinguish browsers and mobile devices. This information is used by our Prebid Server demand partners to select advertisements for delivery by the Platform and to measure the performance of, and attribute payment for, those advertisements. Note the cookie is a cookie used by prebid.org, the open source heading bidding project and is not our proprietary cookie. We run an instance of prebid.org software on our infrastructure.

usersync

90 days

The usersync cookie contains data denoting whether a cookie ID is synced with our partners. ID syncing enables our partners to use their data from outside the Platform on the Platform. (See our platform privacy page for more info.)

tcs.adnxs_uid

6 months

Xandr Cookie Matching Service (formerly AppNexus) enables a buyer to associate the cookie that identifies a Tealium visitor and the cookie that identifies the user for Xandr.

icu

90 days

The icu cookie is used to select ads and limit the number of times a user sees a particular ad. It contains information such as the number of times an ad has been shown, how recently an ad has been shown, or how many total ads have been shown.

uuid2

90 days

This cookie contains a unique randomly-generated value that enables the Platform to distinguish browsers and devices.

Mediamath

uuid

13 months

In order for a data provider to send audience data to MediaMath, there must be a user sync process in place. This means that the provider can refer to a user by a MediaMath Unique User ID (MM UUID).

Lead Forensics

Lfuuid

Expires 01/02/2030

The _lfuuid cookie allows a website to track visitor behaviour on the sites on which the cookie is installed. Tracking is performed anonymously until a user identifies himself by submitting a form.

Selligent

Sbt_i

1 year

Unique site identifier

Sbt_p

1 year

This tracks users behavior on the website which can trigger Selligent landing pages (for example show banners) or email campaigns (example: abandoned basket email). And the cookie specifically keeps the information to link back to the behavior

Other

UULE

6 hours

These cookies are used to collect information about how visitors use our Site. We use the information to compile reports and to help us improve the Site. The cookies collect information in an anonymous form, including the number of visitors to the Site, where visitors have come to the Site from and the pages they visited. If you do not allow these cookies we will not be able to include your visit in our statistics. You can read the full Google Analytics privacy policy at:http://www.google.com/policies/privacy/

Criteo

uid

13 months

Identifier of a Criteo cookie that we have assigned to your web browser

LinkedIn

UserMatchHistory

30 days

LinkedIn Ads ID syncing

AnalyticsSyncHistory

30 days

Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries

li_oatml

30 days

Used to identify LinkedIn Members off LinkedIn for advertising and analytics outside the Designated Countries and, for a limited time, advertising in the Designated Countries

lms_ads

30 days

Used to identify LinkedIn Members off LinkedIn in the Designated Countries for advertising

lms_analytics

30 days

Used to identify LinkedIn Members in the Designated Countries for analytics

li_fat_id

30 days

Member indirect identifier for Members for conversion tracking, retargeting, analytics

li_sugr

90 days

Used to make a probabilistic match of a user’s identity outside the Designated Countries

U

3 months

Browser Identifier for users outside the Designated Countries

_guid

90 days

Used to identify a LinkedIn Member for advertising through Google Ads

BizographicsOptOut

10 years

Determine opt-out status for 3rd party tracking