Changes for page ONEcount Cookies

Last modified by rayaan@one-count_com on 2023/11/20 16:42
From version 25.1
edited by chris
on 2018/12/26 11:12
Change comment: There is no comment for this version
To version 23.1
edited by melanie@one-count_com
on 2016/12/13 14:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -ONEcount Cookies
1 +ONEcount Cookies (v. 12.x)
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.chris
1 +XWiki.melanie@one-count_com
Content
... ... @@ -12,39 +12,6 @@
12 12  (% style="color: rgb(128,128,128);" %)//Below is a list of the cookies and their description~://
13 13  
14 14  (% class="western" %)
15 -== ==
16 -
17 -(% class="western" %)
18 -== **First Part Cookie Setting** ==
19 -
20 -ONEcount sets 2 types of cookies: A temp cookie on the first visit- and an OCID cookie when the user is identified by registering, logging in, or when OC performs a cookie sync. All ONEcount cookies are first-party cookies, which means they are supported by all web browsers.
21 -
22 -(% align="center" %)
23 -
24 -
25 -When a user visits the site for the first time, he or she will have no ONEcount cookies for that site.  In order to facilitate multi-site tracking, targeting and gating, ONEcount will do an initial redirect to the [[onecount.net>>url:http://onecount.net||shape="rect"]] domain to determine if the user has a cookie in the [[onecount.net>>url:http://onecount.net||shape="rect"]] domain, meaning, he or she has already been identified on another site within the customer’s group of sites
26 -
27 -
28 -
29 -If the user is already identified in the [[onecount.net>>url:http://onecount.net||shape="rect"]] domain, ONEcount will set a cookie in the local domain identifying that user. When the user returns to the local site, they will no longer be redirected.
30 -
31 -
32 -
33 -The One-Time redirect will happen //only// when you visit a page for the 1^^st^^ time of a brand and is considered an industry standard.
34 -
35 -
36 -
37 - Upon registering, clicking on a smartlink, or being identified through a cookie-sync with a third-party, ONEcount sets an OCID cookie showing that we have identified the person as a known user.
38 -
39 -
40 -
41 -This helps a brand that has multiple sites. If a customer has 40 sites and a user is identified on Site A, then ONEcount will first set the temp cookie and then OCID cookie and store that data as a known user.
42 -
43 -
44 -
45 -If a user visits Site B, then OCID will be able to retrieve that user’s identity, which is stored in cookies on the [[onecount.net>>url:http://onecount.net||shape="rect"]] domain. At this point, the user is known and his or her activity can be tracked across all brand sites that the user has registered for.
46 -
47 -(% class="western" %)
48 48  == **Central Domain Cookies** ==
49 49  
50 50  These cookies are set on the ONEcount domain.
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -19038285
1 +11927756
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/19038285/ONEcount Cookies
1 +https://info.onecount.net//wiki/spaces/OD/pages/11927756/ONEcount Cookies (v. 12.x)