Changes for page ONEcount Cookies
Last modified by rayaan@one-count_com on 2023/11/20 16:42
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -ONEcount Cookies 1 +ONEcount Cookies (v. 12.x) - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Admin1 +XWiki.melanie@one-count_com - 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 ... ... @@ -12,36 +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 -== **First-Party Cookie Setting** == 16 - 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 - 19 -(% align="center" %) 20 -\\ 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 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 - 24 -\\ 25 - 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 - 28 -\\ 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 - 38 -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. 39 - 40 -\\ 41 - 42 -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. 43 - 44 -(% class="western" %) 45 45 == **Central Domain Cookies** == 46 46 47 47 These cookies are set on the ONEcount domain. ... ... @@ -48,11 +48,11 @@ 48 48 49 49 **~_~_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. 50 50 51 - \\21 + 52 52 53 53 **~_~_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"]]) 54 54 55 - \\25 + 56 56 57 57 **~_~_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"]]. 58 58 ... ... @@ -61,44 +61,38 @@ 61 61 62 62 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. 63 63 64 - \\34 + 65 65 66 66 **~_~_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. 67 67 68 - \\38 + 69 69 70 70 **~_~_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. 71 71 72 - \\42 + 73 73 74 74 **~_~_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. 75 75 76 - \\46 + 77 77 78 78 **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. 79 79 80 - \\50 + 81 81 82 82 **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. 83 83 84 - \\54 + 85 85 86 86 **_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. 87 87 88 - \\58 + 89 89 90 90 **_gcnb**: used as part of the visit id generation process. 91 91 92 - **_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.62 + 93 93 94 - \\64 + 95 95 96 -\\ 97 - 98 -\\ 99 - 100 -\\ 101 - 102 102 (% align="CENTER" %) 103 103 104 104 \\ ... ... @@ -153,11 +153,11 @@ 153 153 {{/expand}} 154 154 {{/panel}} 155 155 156 - \\120 + 157 157 158 - \\122 + 159 159 160 - \\124 + 161 161 {{/layout-cell}} 162 162 {{/layout-section}} 163 163 {{/layout}}
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -1 053491241 +11927756 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://info.onecount.net//wiki/spaces/OD/pages/1 05349124/ONEcount Cookies1 +https://info.onecount.net//wiki/spaces/OD/pages/11927756/ONEcount Cookies (v. 12.x)