What are cookies?

Why do Teleperformance websites use cookies?

Which cookies does Teleperformance use?

Which cookies do third parties use via our websites?

How can you manage your cookie settings?

 

What are cookies?

A cookie is a small file downloaded on to and/or read by a device (for instance a computer or smartphone) when a user accesses a website. Cookies typically enable websites to work, or work more efficiently. They can also be used to recognize a user’s device.

Why does Teleperformance use cookies?

The information collected by cookies on our websites is used for various purposes, including the following:

  • Strictly Necessary: These technical cookies are essential for the operation of our website and for enabling you to use its features, for example logging into secure areas.
  • Customization: these cookies are used to recognize you when you return to our websites in order to speed up your experience (for instance by remembering the information provided in our online forms), and to offer you personalized content and preferences (for instance your choice of language or region).
  • Analytics and Performance: these cookies are used to analyze the frequency of visits to our websites and what visitors do on our websites. This helps us to improve the way our websites work, for example, by ensuring that you can find what you are looking for easily, or that our websites remain up and running.
  • Advertising: these cookies are used to record your online activity and help to identify your preferences in order to provide you with advertising that is relevant to you.

Further information on the specific cookies used on Teleperformance websites can be found under the ‘Which cookies does Teleperformance use?’ and ‘Which cookies do third Parties set on our websites’ sections of this policy.

 

Which cookies does Teleperformance use?

Teleperformance and its subsidiaries use the following cookies on the websites.

Strictly Necessary Cookies
NamePurposeDescriptionStorage Period
ASP.NET_SessionIdWEBSITE – Store Session ID for webserverThe value is the ID of the user session.End of browser session
PHPSESSIDBLOG – Store Session ID for webserverThe value is the ID of the user session.End of browser session
tp-frontendLeader InsightsUsed to distinguish users and sessions.End of browser session
Customization Cookies
NamePurposeDescriptionStorage Period
Analytics and Performance Cookies
NamePurposeDescriptionStorage Period
__utmaGoogle AnalyticsUsed to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.2 years from set/update
__utmtGoogle AnalyticsUsed to throttle request rate10 minutes
__utmbGoogle AnalyticsUsed to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.30 mins from set/update
__utmcGoogle AnalyticsNot used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visitEnd of browser session
__utmzGoogle AnalyticsStores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.6 months from set/update
__utmvGoogle AnalyticsUsed to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.2 years from set/update
_gidGoogle AnalyticsUsed to distinguish users.24 hours
_gaGoogle AnalyticsUsed to distinguish users.2 years
__aucAlexaAlexa analytics cookies are used to track and report information to the Alexa analytics service30 mins from set/update
__ascAlexaAlexa analytics cookies are used to track and report information to the Alexa analytics service1 year from set/update
_mkto_trkMarketoThis tracking cookie allows a website to link visitor behaviour to the recipient of an email marketing campaign, to measure campaign effectiveness.2 years from set/update
__smTokenSumoThe __smToken is set once you login to Sumo and is checked to verify whether you are logged into Sumo or not.1 year from set/update
__smVIDSumoThird party (Sumo) cookie used for marketing purposes

More details: https://help.sumo.com/hc/en-us/articles/115004671147-How-Sumo-Cookies-Work

Immediately
__atuvsAddThisEnsures that the updated counter is displayed to the user if a page is shared with the social sharing service, AddThis.30 minutes
__atuvcAddThisUpdates the counter of a website’s social sharing features.1 year from set/update
Advertising Cookies
NamePurposeDescriptionStorage Period
IDE.googleleadservicesAd trackingBy Session
tr.facebook.comAd trackingBy Session
lidcLinkedin.comUsed for routing1 day
bcookieLinkedin.comBrowser ID cookie1 year
bscookieLinkedin.comSecure browser ID cookie1 year
L1cLinkedin.comBrowser ID cookieCurrent Session
BizoIDLinkedin.comLinkedIn Ad analytics6 months
BizoDataLinkedin.comLinkedIn Ad analytics6 months
BizoUserMatchHistoryLinkedin.comLinkedIn Ad analytics6 months
BizoNetworkPartnerIndexLinkedin.comLinkedIn Ad analytics6 months
tokenLinkedin.comAccess token4 hours
Player_settings_0_3Linkedin.comPlayer settings3 weeks
LyndaLoginStatusLinkedin.comLogin status10 years
throttle-XXXLinkedin.comThrottling on Lynda6 months
NSC_XXXLinkedin.comLoad balancing5 minutes

 

Which cookies do third parties set on our websites?

Teleperformance allows some third parties to set and access their own cookies on your device.

Third parties place the following cookies on Teleperformance’s websites.

Strictly Necessary Cookies
NamePurposeDescriptionStorage Period
Customization Cookies
NamePurposeDescriptionStorage Period
Analytics and Performance Cookies
NamePurposeDescriptionStorage Period
__utmaGoogle AnalyticsUsed to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.2 years from set/update
__utmtGoogle AnalyticsUsed to throttle request rate10 minutes
__utmbGoogle AnalyticsUsed to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.30 mins from set/update
__utmcGoogle AnalyticsNot used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visitEnd of browser session
__utmzGoogle AnalyticsStores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.6 months from set/update
__utmvGoogle AnalyticsUsed to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.2 years from set/update
_gidGoogle AnalyticsUsed to distinguish users.24 hours
_gaGoogle AnalyticsUsed to distinguish users.2 years
__aucAlexaAlexa analytics cookies are used to track and report information to the Alexa analytics service30 mins from set/update
__ascAlexaAlexa analytics cookies are used to track and report information to the Alexa analytics service1 year from set/update
_mkto_trkMarketoThis tracking cookie allows a website to link visitor behaviour to the recipient of an email marketing campaign, to measure campaign effectiveness.2 years from set/update
__smTokenSumoThe __smToken is set once you login to Sumo and is checked to verify whether you are logged into Sumo or not.1 year from set/update
__smVIDSumoThird party (Sumo) cookie used for marketing purposes

More details: https://help.sumo.com/hc/en-us/articles/115004671147-How-Sumo-Cookies-Work

Immediately
__atuvsAddThisEnsures that the updated counter is displayed to the user if a page is shared with the social sharing service, AddThis.30 minutes
personalization_idTwitterThis cookie is set due to Twitter integration and sharing capabilities for the social media.2 Years
tfw_expTwitterThis cookie is set due to Twitter integration and sharing capabilities for the social media.14 Days
__atuvcAddThisUpdates the counter of a website’s social sharing features.1 year from set/update
Advertising Cookies
NamePurposeDescriptionStorage Period
IDE.googleleadservicesAd trackingBy Session
tr.facebook.comAd trackingBy Session
lidcLinkedin.comUsed for routing1 day
bcookieLinkedin.comBrowser ID cookie1 year
bscookieLinkedin.comSecure browser ID cookie1 year
L1cLinkedin.comBrowser ID cookieCurrent Session
BizoIDLinkedin.comLinkedIn Ad analytics6 months
BizoDataLinkedin.comLinkedIn Ad analytics6 months
BizoUserMatchHistoryLinkedin.comLinkedIn Ad analytics6 months
BizoNetworkPartnerIndexLinkedin.comLinkedIn Ad analytics6 months
tokenLinkedin.comAccess token4 hours
Player_settings_0_3Linkedin.comPlayer settings3 weeks
LyndaLoginStatusLinkedin.comLogin status10 years
throttle-XXXLinkedin.comThrottling on Lynda6 months
NSC_XXXLinkedin.comLoad balancing5 minutes

For example, Google Analytics is used to identify your visit to the site. Google Analytics help Teleperformance to understand how visitors engage with their sites or apps. When Google Analytics is used, the web browser automatically sends certain information to Google. For further information, please visit https://support.google.com/analytics/answer/6004245?hl=en-GB

To learn more about third party cookies, please refer to third party websites.

 

How can you manage your cookie settings?

By continuing browsing the websites, you agree to provide consent to the use of cookies. You can withdraw consent at any time. You can change this by using browser settings, or cookie settings. For third party cookies, please refer to further information on ‘Which cookies do third parties set via our websites?’ section above.