Skip to Content
Last modified by Admin User on 2025/06/27 12:15
From version 35.1
edited by Admin
on 2022/05/18 11:47
Change comment: There is no comment for this version
To version 36.1
edited by Admin
on 2023/01/04 20:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -24,11 +24,11 @@
24 24  
25 25  Tag management platforms can be used as long as you can control where the ONEcount widget loads. Because order and placement is often difficult for users to configure, we recommend placing the ONEcount widget directly on the page.
26 26  
27 -ONEcount uses first-party cookies to track user behavior and target users. There are two main cookies that are important here: the OCID cookie, which identifies a user who exists as a user in the ONEcount database (ie., a “known” user), and the tmp-cookie, which is a tracking cookie assigned to all users, known and unknown. If a user has a tmp-cookie in their browser, ONEcount can track and target the user. If the user also has an OCID cookie in their browser, ONEcount can match that browser to a record in your database.
27 +ONEcount uses first-party cookies to track user behavior and target users. There are two main cookies that are important here: the OCID cookie, which identifies a user who exists as a user in the ONEcount database (ie., a “known” user), and the tmpcookie, which is a tracking cookie assigned to all users, known and unknown. If a user has a tmpcookie in their browser, ONEcount can track and target the user. If the user also has an OCID cookie in their browser, ONEcount can match that browser to a record in your database.
28 28  
29 29  These cookies exist in two domains: the “local” domain for your web site or one of your web sites, and the “central” domain ([[onecount.net>>url:http://onecount.net||shape="rect"]]). ONEcount is designed for multi-site identification; a user who logs in on your Site A, can also be logged in on your Site B via the central domain cookie.
30 30  
31 -When the page loads, the ONEcount widget checks the local domain for the tmp cookie. If the user is visiting your site for the first time, he or she may not have a local domain tmp cookie. The ONEcount widget then check the ONEcount central domain ([[onecount.net>>url:http://onecount.net||shape="rect"]]) to see if the user has a first-party tmp cookie in that domain. If there is a tmp cookie in the central domain, the ONEcount widget reloads the page and sets a tmp cookie in the local domain. When a user is identified through a registration, cookie-sync or link-click, the OCID cookie is created in both the local and central domains.
31 +When the page loads, the ONEcount widget checks the local domain for the tmpcookie. If the user is visiting your site for the first time, he or she may not have a local domain tmpcookie. The ONEcount widget then checks the ONEcount central domain ([[onecount.net>>url:http://onecount.net||shape="rect"]]) to see if the user has a first-party tmpcookie in that domain. If there is a tmpcookie in the central domain, the ONEcount widget reloads the page and sets a tmpcookie in the local domain. When a user is identified through a registration, cookie-sync or link-click, the OCID cookie is created in both the local and central domains.
32 32  
33 33  ~*~*Please note that these central domain cookies are //customer-specific//, and we do not share those cookies between customers.
34 34  
... ... @@ -50,6 +50,9 @@
50 50  
51 51  In other words, the following order:
52 52  
53 +<HTML>
54 +<HEAD>
55 +<TITLE>title</TITLE>
53 53  Google Analytics Widget
54 54  ONEcount Widget
55 55  
... ... @@ -57,15 +57,22 @@
57 57  
58 58  This order:
59 59  
63 +<HTML>
64 +<HEAD>
65 +<TITLE>title</TITLE>
60 60  ONEcount Widget
61 61  Google Analytics Widget
62 62  
63 63  Will allow ONEcount to reload the page for first-time visitors prior to the GA widget loading, resulting in a single impression.
64 64  
65 -Once the widget is placed on your pages, you will see a number of pixels load from the [[onecount.net>>url:http://onecount.net||shape="rect"]] domain each time the page loads. Most of these pixels load asynchronously, meaning in paralle, and should not impact your page load at all.
71 +If you're concerned about how the page reload impacts user experience, keep in mind two things:
66 66  
67 -\\
73 +1) The redirect only happens once per user, per device.
68 68  
75 +2) If the widget is placed properly, the user won't experience the redirect. As you can see from the placement above, the ONEcount widget is delivered prior to any content, so the user experience won't be interrupted.
76 +
77 +Once the widget is placed on your pages, you will see a number of pixels load from the [[onecount.net>>url:http://onecount.net||shape="rect"]] domain each time the page loads. Most of these pixels load asynchronously, meaning in parallel, and should not impact your page load at all.
78 +
69 69  (% style="color: rgb(255,0,0);" %)//*****//(% style="color: rgb(0,0,0);" %)//A smartlink is any link that has parameters for identifying the user appended to the end of the URL. These parameters vary based on the email marketing platform you use (e.g. ONEcount's integrated Email Engine, Real Magnet/Magnet Mail, Exact Target, Silverpop, etc.) Upon clicking on a smartlink, two things will happen: 1) the user will be authenticated automatically for access-controlled content; and 2) the user will be identified in the system as a ONEcount user and a cookie will be set, allowing you to track as a Known user all activities across your online properties. //(%%)//*See Smartlinks and Other Form Linkouts// //documentation for more information on smartlinks.//
70 70  
71 71  \\
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -77496791
1 +77496811
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/77496791/Widget Implementation
1 +https://info.onecount.net//wiki/spaces/OD/pages/77496811/Widget Implementation