Skip to Content
Last modified by Admin User on 2025/06/27 12:15
From version 31.1
edited by santosh
on 2020/12/14 12:08
Change comment: There is no comment for this version
To version 32.1
edited by Admin
on 2022/05/13 11:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.santosh
1 +XWiki.Admin
Content
... ... @@ -18,10 +18,54 @@
18 18  
19 19  This widget also tracks all web activity.
20 20  
21 -This widget must be embedded inside the head section(<head></head>) of the website and should be placed BEFORE any other third party trackers (like Google analytics) or ad network codes and AFTER the title meta tag.
21 +==== ONEcount Library/Tracker Placement: ====
22 22  
23 +The main ONEcount widget, (all.min.js) is responsible for loading most of the code that ONEcount uses when a user visits your web site. It also takes the first step in identifying visitors to your web site, so it’s important it be placed properly on the site.
24 +
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 +
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.
28 +
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 +
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.
32 +
33 +~*~*Please note that these central domain cookies are //customer-specific//, and we do not share those cookies between customers.
34 +
35 +The main ONEcount widget is as follows:
36 +
37 +<script id="oc-widget-main" src="https:~/~/validate.onecount.net/js/all.min.js#%%%%%%%%%%%%%%%%"></script>
38 +
39 +It includes a unique customer identifier that will be unique to your installation of ONEcount. You should place the widget in the header of the root template of your web site(s) so it can load on every page you would like ONEcount to track.
40 +
41 +The main widget should be placed in the document header, after the Title and Meta Keywords tags so that these values can be available to the ONEcount widget when a user visits a page.
42 +
43 +If you are using any third-party tracking or measuring pixels (ie., Google Analytics, Adobe,  etc.), you should place these pixels after the ONEcount pixel.
44 +
45 +This is to avoid double-counting page views from first time visitors.
46 +
47 +In other words, the following order:
48 +
49 +Google Analytics Widget
50 +ONEcount Widget
51 +
52 +Would result in Google Analytics recording two page impressions for a first-time site visitor, because GA would count the initial load, and then record an additional page load after the redirect.
53 +
54 +This order:
55 +
56 +ONEcount Widget
57 +Google Analytics Widget
58 +
59 +Will allow ONEcount to reload the page for first-time visitors prior to the GA widget loading, resulting in a single impression.
60 +
61 +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.
62 +
63 +\\
64 +
23 23  (% 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.//
24 24  
67 +\\
68 +
25 25  === Automation Widget ===
26 26  
27 27  Automation scripts are snippets of javascript code that allow ONEcount to target actions (like ad target, popup target etc). This piece of javascript determines and outputs any automated action to the browser.
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -66715803
1 +66715805
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/66715803/Widget Implementation
1 +https://info.onecount.net//wiki/spaces/OD/pages/66715805/Widget Implementation