Changes for page ONEcount Cookies

Summary

• Page properties (3 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Parent

...	...	@@ -1,0 +1,1 @@
	1	+System Setup Detail and Technical Information

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.melanie@one-count_com
	1	+XWiki.admin

Content

...	...	@@ -1,14 +1,33 @@
	1	+{{layout}}
	2	+{{layout-section ac:type="two_right_sidebar"}}
	3	+{{layout-cell}}
1	1	----
2	2
3		-
4	4
5		-//ONEcount uses first-party cookies to track users. The cookies are set in the ONEcount domain and on the customer's site(s).//
	7	+(% style="color:#808080" %)//ONEcount uses first-party cookies to track users. The cookies are set in the ONEcount domain and on the customer's site(s).//
6	6
7		-//Cookies on the ONEcount domain are called Central Domain Cookies (CDC). Those on the client's site are called Local Cookies (LC).//
	9	+(% style="color:#808080" %)//Cookies on the ONEcount domain are called Central Domain Cookies (CDC). Those on the client's site are called Local Cookies (LC).//
8	8
9		-//Below is a list of the cookies and their description~://
	11	+(% style="color:#808080" %)//Below is a list of the cookies and their description~://
10	10
11		-(% class="western" %)
	13	+(% id="HFirst-PartyCookieSetting" class="western" %)
	14	+== **First-Party Cookie Setting** ==
	15	+
	16	+ONEcount sets 2 types of cookies: A temp cookie(**~_~_tempcookie**) on the first visit- and an OCID cookie(**~_~_ocid**) 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.
	17	+
	18	+
	19	+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.**
	20	+
	21	+
	22	+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.
	23	+
	24	+
	25	+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.
	26	+
	27	+
	28	+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.
	29	+
	30	+(% id="HCentralDomainCookies" class="western" %)
12	12	== **Central Domain Cookies** ==
13	13
14	14	These cookies are set on the ONEcount domain.
...	...	@@ -15,55 +15,54 @@
15	15
16	16	**~_~_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.
17	17
18		-
19	19
20	20	**~_~_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"]])
21	21
22		-
23	23
24	24	**~_~_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"]].
25	25
26		-(% class="western" %)
	43	+
	44	+(% style="color:#202124" %)**~_~_ocgt-//client-id//**(%%): This is (% style="color:#333333" %)used to identify the user.
	45	+
	46	+(% id="HLocalCookies" class="western" %)
27	27	== **Local Cookies** ==
28	28
29	29	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.
30	30
31		-
32	32
33	33	**~_~_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.
34	34
35		-
36	36
37	37	**~_~_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.
38	38
39		-
40	40
41	41	**~_~_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.
42	42
43		-
44	44
45	45	**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.
46	46
47		-
48	48
49	49	**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.
50	50
51		-
52	52
53	53	**_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.
54	54
55		-
56	56
57	57	**_gcnb**: used as part of the visit id generation process.
58	58
59		-
	72	+**_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.
60	60
61		-
62	62
63		-(% align="CENTER" %)
	75	+//**ocaction-segment_id**: used as part of targeting process.//
64	64
65		-\\
66	66
67		-(% align="CENTER" %)
68	68
69		-\\
	79	+
	80	+
	81	+
	82	+
	83	+
	84	+
	85	+{{/layout-cell}}
	86	+{{/layout-section}}
	87	+{{/layout}}

Confluence.Code.ConfluencePageClass[0]

id

...	...	@@ -1,1 +1,1 @@
1		-65734
	1	+65727

url

...	...	@@ -1,1 +1,1 @@
1		-https://info.onecount.net//wiki/spaces/OD/pages/65734/ONEcount Cookies
	1	+https://info.onecount.net//wiki/spaces/OD/pages/65727/ONEcount Cookies