Changes for page ONEcount Cookies

Last modified by rayaan@one-count_com on 2023/11/20 16:42
From version 28.1
edited by rayaan@one-count_com
on 2023/11/20 12:47
Change comment: There is no comment for this version
To version 26.1
edited by chris
on 2018/12/26 11:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.rayaan@one-count_com
1 +XWiki.chris
Content
... ... @@ -3,7 +3,7 @@
3 3  {{layout-cell}}
4 4  ----
5 5  
6 -\\
6 +
7 7  
8 8  (% style="color: rgb(128,128,128);" %)//ONEcount uses first-party cookies to track users. The cookies are set in the ONEcount domain and on the customer's site(s).//
9 9  
... ... @@ -17,19 +17,27 @@
17 17  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.
18 18  
19 19  (% align="center" %)
20 -\\
20 +
21 21  
22 -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 set **~_~_tempcookie.**
22 +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
23 23  
24 -\\
24 +
25 25  
26 -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.
26 +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.
27 27  
28 -\\
28 +
29 29  
30 +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.
31 +
32 +
33 +
34 + 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.
35 +
36 +
37 +
30 30  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.
31 31  
32 -\\
40 +
33 33  
34 34  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.
35 35  
... ... @@ -40,11 +40,11 @@
40 40  
41 41  **~_~_ocgt**: This is the global token. It's used to track users across all sites where the ONEcount widget is deployed. The value is a 64-character hash. This cookie is set under [[onecount.net>>url:http://onecount.net||shape="rect"]] domain.
42 42  
43 -\\
51 +
44 44  
45 45  **~_~_ocid**: set when a user is logs in on one of the Customer's sites. The value is a 64-character hash that represent sthe user in that customer's installation of ONEcount. It's set under **client**-[[reg.onecount.net>>url:http://reg.onecount.net||shape="rect"]] domain. (ie: if client is **foo**, then the cookie will be set under **foo**-[[reg.onecount.net>>url:http://reg.onecount.net||shape="rect"]])
46 46  
47 -\\
55 +
48 48  
49 49  **~_~_ocusername**: Similar to ~_~_ocid, it's set when the user logs in on the client's system. The value, is the user's **username** on that client's system. The domain for this cookie **client**-[[reg.onecount.net>>url:http://reg.onecount.net||shape="rect"]].
50 50  
... ... @@ -53,44 +53,38 @@
53 53  
54 54  These cookies are set on the customer's site(s). If the customer has multiple sites, these cookies will be set as first-party cookies in each domain.
55 55  
56 -\\
64 +
57 57  
58 58  **~_~_tempcookie**: used track users on the client's site. The value is the same as **~_~_ocgt** from the central domain. It's set under the client's site domain.
59 59  
60 -\\
68 +
61 61  
62 62  **~_~_ocid**: set when a user is logged in on the client's site. The value is the same as **~_~_ocid** from the central domain. It's set under the client's site domain.
63 63  
64 -\\
72 +
65 65  
66 66  **~_~_ocusername**: set when a user is logged in on the client's site. The value is the same as **~_~_ocusername** from the central domain. It's set under the client's site.
67 67  
68 -\\
76 +
69 69  
70 70  **cookieValid**: this is a daily cookie. It's set on the first visit of the day if **~_~_ocid** is present. It's used as a flag that can be used to determine whether **~_~_ocid** is still valid or not.
71 71  
72 -\\
80 +
73 73  
74 74  **realReferer**: used to preserve the original referer when a redirect to [[onecount.net>>url:http://onecount.net||shape="rect"]] happens for setting the Central Domain Cookies. This can be passed to Google Analytics or other platforms.
75 75  
76 -\\
84 +
77 77  
78 78  **_gcna**: this represents the visit id. The value is a combination of the **~_~_ocid** and **~_~_tempcookie** cookies as well as the visit timestamp and the visit counter.
79 79  
80 -\\
88 +
81 81  
82 82  **_gcnb**: used as part of the visit id generation process.
83 83  
84 -**_ocfreepass**: counts pages that are part of a gating product. So if [[domain.com/articles/>>url:http://newrepublic.com/articles/||shape="rect"]] is the URL of the product, ocfreepass will increment on each page view if domain[[.com/articles/>>url:http://newrepublic.com/articles/||shape="rect"]], but it will not increment on a page view of [[domain.com>>url:http://newrepublic.com||shape="rect"]] because it is not a gated product. The name of the cookie includes a unique customer ID for each ONEcount customer, and a uniqe # for the product. In this way, if the same URL is in two different products, there will be two different cookies, one for each product. The number is the product_Id.
92 +
85 85  
86 -\\
94 +
87 87  
88 -\\
89 -
90 -\\
91 -
92 -\\
93 -
94 94  (% align="CENTER" %)
95 95  
96 96  \\
... ... @@ -140,15 +140,16 @@
140 140  Email Engine and Sender Score>>url:http://bos-jira01-cl01.onecount.net:8090/display/OD/Email+Engine+and+Sender+Score||shape="rect"]][[
141 141  \\>>url:http://bos-jira01-cl01.onecount.net:8090/pages/viewpage.action?pageId=65735||shape="rect"]][[Global Features>>url:http://bos-jira01-cl01.onecount.net:8090/pages/viewpage.action?pageId=65905||shape="rect"]][[
142 142  >>url:http://bos-jira01-cl01.onecount.net:8090/pages/viewpage.action?pageId=65735||shape="rect"]][[
143 ->>url:http://bos-jira01-cl01.onecount.net:8090/pages/viewpage.action?pageId=65751||shape="rect"]][[ >>url:http://bos-jira01-cl01.onecount.net:8090/pages/viewpage.action?pageId=65751||shape="rect"]]
145 +>>url:http://bos-jira01-cl01.onecount.net:8090/pages/viewpage.action?pageId=65751||shape="rect"]][[
146 +>>url:http://bos-jira01-cl01.onecount.net:8090/pages/viewpage.action?pageId=65751||shape="rect"]]
144 144  {{/expand}}
145 145  {{/panel}}
146 146  
147 -\\
150 +
148 148  
149 -\\
152 +
150 150  
151 -\\
154 +
152 152  {{/layout-cell}}
153 153  {{/layout-section}}
154 154  {{/layout}}
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -105349126
1 +23331775
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/105349126/ONEcount Cookies
1 +https://info.onecount.net//wiki/spaces/OD/pages/23331775/ONEcount Cookies