Skip to Content

Wiki source code of ONEcount Cookies

Last modified by Admin User on 2025/10/31 14:01
Show last authors
1 {{layout}}
2 {{layout-section ac:type="two_right_sidebar"}}
3 {{layout-cell}}
4 ----
5
6
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).//
8
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).//
10
11 (% style="color:#808080" %)//Below is a list of the cookies and their description~://
12
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" %)
31 == **Central Domain Cookies** ==
32
33 These cookies are set on the ONEcount domain.
34
35 **~_~_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.
36
37
38 **~_~_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"]])
39
40
41 **~_~_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"]].
42
43
44 (% style="color:#202124" %)**~_~_ocgt-//client-id//**(%%): This is (% style="color:#333333" %)used to identify the user.
45
46 (% id="HLocalCookies" class="western" %)
47 == **Local Cookies** ==
48
49 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.
50
51
52 **~_~_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.
53
54
55 **~_~_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.
56
57
58 **~_~_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.
59
60
61 **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.
62
63
64 **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.
65
66
67 **_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.
68
69
70 **_gcnb**: used as part of the visit id generation process.
71
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.
73
74
75 //**ocaction-segment_id**: used as part of targeting process.//
76
77
78
79
80
81
82
83
84
85 {{/layout-cell}}
86 {{/layout-section}}
87 {{/layout}}