Cookies

An overview of cookies used by the Commanders Act platform.

Predefined Cookies

Following cookies are used automatically in depending on the installed Commanders Act products.

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 + TAG + TRUST + MIX

Cookie

WID

.commander1.com

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).

MIX

Cookie

TCSESSION

.commander1.com

Session

MixCommander session ID.

Commanders Act

Used to calculate MIX metrics based on the session.

MIX

Cookie

TCREDIRECT

Customer domain

Session

MixCommander redirect flag.

Commanders Act

Used to deduplicate clicks (if redirect, just store the page view and ignore the click).

MIX

Cookie

TCREDIRECT

.commander1.com

Session

MixCommander redirect flag.

Commanders Act

Used to deduplicate clicks (if redirect, just store the page view and ignore the click).

MIX

Cookie

TCLANDINGURL

.commander1.com

Session

Landing page URL.

Commanders Act

Used to store landing page URL for MIX raw data.

MIX + DATA+ TAG + TRUST

Cookie

TCID

.commander1.com

365 days

Commanders Act ID.

Commanders Act

Visitor identifier used to compute deduplicated statistics per user (for campaign and on-site tracking, segmentation, ...). TrustCommander uses this cookie to measure statistics for privacy banner performance after a visitor provided consent. Before users provided consent TrustCommander uses the TCPID cookie to measure anonymous statistics for privacy banner.

MIX + DATA

Cookie

CAID

domainfirstClient

365 days

Commanders Act users ID

Commanders Act

The CAID is the user identifier for cookie 1st

MIX + DATA+ TAG + TRUST

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.

MIX + TAG

Cookie

tc_cj_v2

.commander1.com

365 days

Deduplication CJ storage ("&chn=" and "&src=" parameters)

Commanders Act

Used for user customer journey storage for tag deduplication (channel and source storage).

MIX + TAG

Cookie

tc_cj_v2_cmp

.commander1.com

365 days

Deduplication CJ storage ("&cmp=" parameter).

Commanders Act

Used for user customer journey storage for tag deduplication (campaign storage).

MIX + TAG

Cookie

tc_cj_v2_med

.commander1.com

365 days

Deduplication CJ storage ("&med=" parameter).

Commanders Act

Used for user customer journey storage for tag deduplication (medium storage).

TAG

Cookie

TCREDIRECT_DEDUP

.commander1.com

Session

MIX redirect flag (used for deduplication).

Commanders Act

Used when the deduplication is based on MIX tracking (so the MIX tracking is taken into account and not the landing page tracking)

TAG

Cookie

tc_sample_{idsite}_{idrule}

Customer domain

365 days

Tag sampling done in the container rules.

Commanders Act

Used for visitor and session sampling in the TagCommander rules.

TAG

Cookie

tc_cj_v2

Customer domain

365 days

Deduplication CJ storage ("&chn=" and "&src=" parameters).

Commanders Act

Used for user customer journey storage for tag deduplication (channel and source storage).

TRUST V1 + V2

Cookie

TCPID

Customer domain

365 days

TrustCommander ID.

Commanders Act

Used to identify visitors exposed to the privacy banner (not encoded contrary to TCID, so visitors can be retrieved in the privacy raw data export). TrustCommander uses this cookie to measure statistics for privacy banner usage until visitors provide consent for the TCID cookie. With this 2-cookie system, TrustCommander 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

TRUST 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.

TRUST 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.

TRUST 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.

TRUST 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.

TRUST 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.

TRUST 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.

Custom Cookies

Users can create custom cookies with TagCommander. 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.