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. chris1 +XWiki.melanie@one-count_com - Content
-
... ... @@ -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. ... ... @@ -103,21 +103,27 @@ 103 103 {{/layout-cell}} 104 104 105 105 {{layout-cell}} 106 -{{panel borderStyle="solid" title="Search all Documentation:"}} 76 +{{panel borderStyle="solid"}} 77 +**Search all Documentation:** 107 107 108 108 80 + 109 109 {{livesearch/}} 110 110 {{/panel}} 111 111 112 -{{panel borderStyle="solid" title=" Search System and Setup Information:"}} 84 +{{panel borderStyle="solid"}} 85 + **Search System and Setup Information:** 113 113 114 114 88 + 115 115 {{pagetreesearch rootPage="System and Setup Information"/}} 116 116 {{/panel}} 117 117 118 -{{panel title="On this page:"}} 92 +{{panel}} 93 +**On this page:** 119 119 120 120 96 + 121 121 {{toc style="square"/}} 122 122 {{/panel}} 123 123
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 233317751 +67392 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://info.onecount.net//wiki/spaces/OD/pages/ 23331775/ONEcount Cookies1 +https://info.onecount.net//wiki/spaces/OD/pages/67392/ONEcount Cookies (v. 12.x)