List of partners for which we operate a cookie synchronization (cookie sync) in order to match users and activate them on partners networks.
AB Tasty
Criteo
Freespee
Appnexus
Realytics
Optimizely
Adventori
Yahoo
PublicIdees
Effinity
RhythmOne
Prediggo
Experian
Zendesk
Bluekai
Google DBM / Adwords
IBM
Adotmob
Sirdata
Squadata
Temelio
Eperflex
Axciom - Liveramp
Adition
Rakuten - Nextperf
Cabestan
Graphinium
Vortex
Adobe
Deutschepost
Golden Bees
Invibes
The Trade Desk
Taboola
An overview of cookies used by the Commanders Act platform.
The technical session cookies for First party domain tracking have been renamed. ("PHOENIX" replaced by "FIRST" in the cookie name) - 06/05/2024 16:01
Following cookies are used automatically in depending on the installed Commanders Act products.
Users can create custom cookies with TMSCommander. For example it is possible to store a URL parameter on a landing page in a cookie to make it available for further pageviews in the session. Users can choose their own name and storage duration for these cookies. Therefore it is not possible to include them in this list.
Product | Type | Name | Domain | Lifetime | Value | Owner | Storage purpose |
---|---|---|---|---|---|---|---|
DATA
Cookie
TCAUDIENCE
Customer domain
365 days
Audience segment storage.
Commanders Act
Used to store the user segment for user targeting.
DATA + TMS + CMP + CAMPAIGN
Cookie
WID
Session
DataCommander session ID.
Commanders Act
Used to identify when the browser is closed in order to split page views into multiple functional sessions.
DATA
Local Storage (default)
_TCCookieSync
/
/
Last cookie sync date.
Commanders Act
Used to store the date of the last cookie synchronisation with the partner (set in local storage by default, and cookie if local storage not available).
DATA
Cookie (if Local Storage not available)
_TCCookieSync
Customer domain
365 days
Last cookie sync date.
Commanders Act
Used to store the date of the last cookie synchronisation with the partner (set in local storage by default, and cookie if local storage not available).
CAMPAIGN
Cookie
TCSESSION
Session
CAMPAIGNCommander session ID.
Commanders Act
Used to calculate CAMPAIGN metrics based on the session.
CAMPAIGN
Cookie
TCREDIRECT
Customer domain
Session
CAMPAIGNCommander redirect flag.
Commanders Act
Used to deduplicate clicks (if redirect, just store the page view and ignore the click).
CAMPAIGN
Cookie
TCREDIRECT
Session
CAMPAIGNCommander redirect flag.
Commanders Act
Used to deduplicate clicks (if redirect, just store the page view and ignore the click).
CAMPAIGN
Cookie
TCLANDINGURL
Session
Landing page URL.
Commanders Act
Used to store landing page URL for CAMPAIGN raw data.
CAMPAIGN + DATA+ TMS + CMP
Cookie
TCID
365 days
Commanders Act ID.
Commanders Act
Visitor identifier used to compute deduplicated statistics per user (for campaign and on-site tracking, segmentation, ...). CMPCommander uses this cookie to measure statistics for privacy banner performance after a visitor provided consent. Before users provided consent CMPCommander uses the TCPID cookie to measure anonymous statistics for privacy banner.
CAMPAIGN + DATA+ TMS + CMP
Cookie
CAID
domainfirstClient
365 days
Commanders Act users ID
Commanders Act
The CAID is the user identifier for cookie 1st
CAMPAIGN + DATA+ TMS + CMP
Local Storage
tC_Sync
/
/
Timestamp.
Commanders Act
Technical cookie that is used to store the timestamp of the last cookie sync that was performed for this user agent. A cookie sync matches the visitor ID of Commanders Act solutions (TCID) with the visitor ID of other solutions. Cookie sync is optional and can be deactivated by Commanders Act users via the Commanders Act support. (cookie exempted)
CAMPAIGN + TMS
Cookie
tc_cj_v2
365 days
Deduplication CJ storage ("&chn=" and "&src=" parameters)
Commanders Act
Used for user customer journey storage for TMS deduplication (channel and source storage).
CAMPAIGN + TMS
Cookie
tc_cj_v2_cmp
365 days
Deduplication CJ storage ("&cmp=" parameter).
Commanders Act
Used for user customer journey storage for TMS deduplication (campaign storage).
CAMPAIGN + TMS
Cookie
tc_cj_v2_med
365 days
Deduplication CJ storage ("&med=" parameter).
Commanders Act
Used for user customer journey storage for TMS deduplication (medium storage).
TMS
Cookie
TCREDIRECT_DEDUP
Session
CAMPAIGN redirect flag (used for deduplication).
Commanders Act
Used when the deduplication is based on CAMPAIGN tracking (so the CAMPAIGN tracking is taken into account and not the landing page tracking)
TMS
Cookie
tc_sample_{idsite}_{idrule}
Customer domain
Session
TMS sampling done in the container rules.
Commanders Act
Used for visitor and session sampling in the TMSCommander rules.
TMS
Cookie
tc_cj_v2
Customer domain
365 days
Deduplication CJ storage ("&chn=" and "&src=" parameters).
Commanders Act
Used for user customer journey storage for TMS deduplication (channel and source storage).
TMS
Cookie
TC_CHECK_COOKIES_SUPPORT
Customer domain
Session
1 if true
Commanders Act
Technical cookie, TMS verification of Cookies deposit (exempted)
CMP V1 + V2
Cookie
TCPID
Customer domain
365 days
CMP Commander ID.
Commanders Act
Used to identify visitors exposed to the privacy banner. CMPCommander uses this cookie to measure statistics for privacy banner usage until visitors provide consent for the TCID cookie. With this 2-cookie system, CMPCommander is the only CMP that has been granted the right of exemption from consent for statistical measurement by the French CNIL. https://www.cnil.fr/fr/solutions-pour-les-cookies-de-mesure-daudience
(cookie exempted)
CMP V1 (Previous Privacy)
Cookie
TC_OPTOUT (default)
Customer domain (default, can be customized)
396 days
Privacy: optin/optout user, privacy version and optin categories.
Commanders Act
Used for user status storage (optin or optout) and Privacy banner display. (cookie exempted)
CMP V1 (Previous Privacy)
Cookie
TC_OPTOUT_categories (default)
Customer domain (default, can be customized)
396 days
Privacy optin categories.
Commanders Act
Used to display the optin/optout categories in the Privacy Center if the user re-open it. (cookie exempted)
CMP V2
Cookie
TC_PRIVACY (default)
Customer domain (default, can be customized)
396 days
Privacy: optin/optout user, privacy version and optin categories.
Commanders Act
Used for user status storage (optin or optout) and Privacy banner display. (cookie exempted)
CMP V2
Cookie
TC_PRIVACY_CENTER (default)
Customer domain (default, can be customized)
396 days
Privacy optin categories.
Commanders Act
Used to display the optin/optout categories in the Privacy Center if the user re-open it. (cookie exempted)
CMP V2
Cookie
tc_test_cookie
Customer domain (default, can be customized)
396 days
Banner display
Commanders Act
Cookie linked to the display of the privacy banner, it allows to check whether cookies can be deposited and not to redisplay the consent banner when consent is given. Deposited then disappears, cannot be deleted. Technical cookie (exempted)
CMP V2
Local Storage
TC_PRIVACY_IAB_VENDORLIST
Customer domain
Unlimited
IAB Global Vendor List
Commanders Act
Used to cache the IAB TCF Global Vendor List to optimise the response time of the IAB TCF consent API.
CMP V2
Local Storage
TC_PRIVACY_TCF
Customer domain
Unlimited
IAB Global Vendor List
Commanders Act
Used to cache the IAB TCF Consent API Response to optimise the response time of the APII.
First domain tracking
Cookie
FDLBCTLYOXA FDLBFIRSTAPI FDLBFIRSTDATA FDLBFIRSTCAMPAIGN FDLBFIRSTCAMPAIGNEF FDLBCAMPAIGNCDOM FDLBFIRSTTMS FDLBFIRSTCMP FDLBFIRST FDLBCTLY FDLBFIRSTEVENTS
Customer domain
Session
Technical cookies for load balancing purposes
Commanders Act
Used for internal infrastructure dispatch.Example value : s11|YNwyo|YNwxd
First-party cookies are stored by the domain (website) you are visiting directly. They allow website owners to collect analytics data, remember language settings, and perform other useful functions that help provide a good user experience.
Third-party cookies are created by domains other than the one you are visiting directly, hence the name third-party. They are used for cross-site tracking, retargeting and ad-serving.
Until now all the data collected on a website was done mainly by tags, 3rd party tags, because the data is pushed to external servers (not owned by the brand but by some partners).
Major browsers, such as Safari or Google Chrome, decided to not allow anymore 3rd party cookies. That means they will block cookies not coming from the brand itself but coming from partners (such as Commanders Act). They will detect all data flux pushed to a domain not related to the brand (3rd party domains).
As a result, the workaround to continue to track and push data from websites to partners, is to use a domain owned by the brand, a first party domain. And the cookies should be set by this domain, this is what is called ‘1st party cookie’ because it seems to be generated by the brand itself and not from partners.
There is a technical setup to do to initialize this 1st party tracking (on the domain level first and then on the cookie level).
In the customer's DNS, the use of a CNAME pointing to a Commanders Act server allows to set cookie as a first party.
The customer should create a subdomain and setup CNAME entries to point to our server (and create as many subdomains as existing domains). Example:
client.com creates a subdomain XYZ.client.com pointing to Commanders Act server. From now on, our tags will now call XYZ.client.com instead of our 3rd party domain (commander1) and response will set a cookie on main domain .client.com which is allowed by main web browsers.
Then please indicate the subdomain on our platform: Administration > Domain Management.
The customer must decide if the SSL encryption on the new subdomain they created is done with ‘Let’s Encrypt’ or with their own certificate. In the former case, nothing to do; in the latter case follow the instruction on the domain management page.
Moreover change on every tag the URL to specify the 1st party domain.
Put in place the Mixcommander tags as you would normally do, but this time use the the tags marked COOKIE 1ST V1.0
In the #CUSTOMER_SUBDOMAIN# placeholder you need to enter the subdomain agreed with the customer.
At this point it’s time to test the hits . ATTENTION the structure of the redirection URL is different from the usual MixCo.
before it was : http://client.commander1.com/c3/?tcs=13&chn=sem&src=google&url=https://domain.client.com/en/13/campaign/trafficking
Now it is : https://client.subdomain.com/mix/c3/?tcs=13&chn=sem&src=google&url=https://domain.client.com/en/13/campaign/trafficking
There are 2 possible situations that we can encountered:
Users with an existing cookie 1st
This is the target configuration when cookies 3rd will disappear.
The browser will push the cookie to the 1st party domain, this one will recognize the cookie and update it and then push it to the browser. Then the data related to the cookie is sent to our system.
Users without an existing cookie 1st
This case is hybrid, as we will work with both 1st and 3rd party domains to keep a continuity of shared information between the 2 servers.
For this case we have users without cookies known by the 1st party domain.
The browser will push the data to the 1st party domain, and we will request on the 3rd party domain all the information we have regarding this user (does a cookie already exist?). The 3rd party domain will push this information (if it exists). Then the 1st party domain will setup the cookie (or create a new one) and the data is pushed to our system.
Now it’s possible to use a combination of first and third party cookies (create a ticket to ask MIX team to activate this option) - available only for the transition.