Cookie States and Tracking Behavior
- 06 May 2020
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Cookie States and Tracking Behavior
- Updated on 06 May 2020
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
| Tag functionality | Cookie state | wtid.js | Cookie setting and detection | Session functionality | Parameters and events |
|---|---|---|---|---|---|
| New cookie configuration state for EU Privacy Act | 1st party disabled, 3rd party disabled | No request made | No 1st party cookie set | Only WT.vt_f=4 is sent, to signify that first party cookies are explicitly disabled. | No WT.co_f should be included in events No WT.vtid should be sent unless the tag is configured to specify a vtid value |
| Standard | 1st party enabled, 3rd party enabled | No request made, users have same ID across domains | 3rd party cookie detection occurs unless overridden by TPCConfig.cfgType. (dcsredirect occurs if the request does not contain an ACOOKIE) | Standard session and timing functionality | n/a |
| Standard with 3rd party cookies disabled | 1st party enabled, 3rd party disabled | No request made, user ID is generated client side | All events should include dcscfg=1 to instruct the collection server to not try and set a third party cookie in the response | Standard session and timing functionality | No dcsredirect requests should occur |
| Unsupported | 1st party disabled, 3rd party enabled | n/a | n/a | n/a | n/a |
Was this article helpful?