Solution Overview for Business Users / Version 2506.0
Table Of ContentsBy default, CoreMedia service operates in "Opt-In" mode. In this mode, a "first-party" cookie ("byside_webcare_tuid") is created on the client's domain with a visitor identifier that, during the lifetime of the cookie, allows the visitor to be recognized between visits.
If desired, CoreMedia can change this behavior and initiate sessions in "Opt-Out" mode (for example: session start until the client accepts the cookie policy). On each new visit, the visitor will be counted as a new visitor. To start the service in this mode, the CoreMedia tag must be loaded with the parameter "bysideWebcare_privacy = 1".
| Opt Out | Opt In |
|---|---|
|
"BySide Privacy = 1 Cookie Level Service = Required" |
"BySide Privacy = 0 Cookie Level Service = Targeting" |
|
"All campaigns will be presented without segmentation or intelligence" |
"All campaigns will be presented with segmentation or intelligence" |
Table 18.1. Table of error codes and Messages
<script>
var bysideWebcare_webcare_id = "A82B12DB68";
var bysideWebcare_lang = “en";
var bysideWebcare_privacy = 1;
</script>
<script src="//www.clientdomain.com/assets/external/byside_webcare.js" type="text/javascript"></script>Example 18.2.
The method used to set cookies for new visitors ("var bysideWebcare_privacy = 1;") only impacts the creation of the visitor. After this moment, changing the cookie level is only possible through the function mentioned here ("bysideWebcare_setDoNotTrack").
Once the client accepts cookies, the following function must be called to allow the client to move to the respective cookie acceptance level (analytics):
bysideWebcare_setCookieServiceLevel( 'LEVEL',
false, function () \{ bysideWebcare_reloadAgentContent(); } )
Example 18.3.
The value [LEVEL] can be one of the following:
DO_NOT_TRACK;
FUNCTIONAL;
PERSONALIZATION;
TARGETING.
