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

Summary

Details

Page properties
Content
... ... @@ -14,7 +14,7 @@
14 14  
15 15  Access protection: Pages or sections of pages that are defined as a resource in ONEcount and that require registration/ signup are handled by this widget. If a resource is being accessed and the user that is trying to access it is not logged in or doesn't have access to that particular resource, then they will be directed to the lookup/ login page (or if lookup/login is set to "off", to the registration form enabled with progressive lookup functionality) where they can log in or complete registration.
16 16  
17 -This widget also allows users who have clicked on a smartlink(% style="color: rgb(255,0,0);" %)*(%%) to automatically be logged in to ONEcount. The system will identify the user and set a cookie for her/him. Any subsequent action by that user on the site will then be tracked and attributed to that user (via tracking widget). These users are included in statistics for Known Users. Note that if a user goes directly to the website (not directed there by a smartlink) and is NOT logged in, he/she will NOT be identified and tracked as a Known User. A user must be logged in to be identified.
17 +This widget also allows users who have clicked on a smartlink(% style="color: rgb(255,0,0);" %)*(%%) to automatically be logged in to ONEcount, as well as users identified by a ONEcount cookie-sync with other third-party identification systems you may use.  In either case, ONEcount will identify the user and set a cookie for her/him. Any subsequent action by that user on the site will then be tracked and attributed to that user (via tracking widget). These users are included in statistics for Known Users. Note that if a user goes directly to the website (not directed there by a smartlink) and is NOT logged in, he/she will NOT be identified and tracked as a Known User. A user must be logged in to be identified.
18 18  
19 19  This widget also tracks all web activity.
20 20  
... ... @@ -36,8 +36,12 @@
36 36  
37 37  <script id="oc-widget-main" src="https:~/~/validate.onecount.net/js/all.min.js#%%%%%%%%%%%%%%%%"></script>
38 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.
39 +Most US-based customers will get the fastest response downloading the widget from our data centers in New Jersey and Illinois using the URL above. Customers with a presence outside the United States may experience lower latency by downloading the main ONEcount widget from our global CDN. To do that, simply substitute the hostname "cdn.onecount.net" for "validate.onecount.net in the URL above. As illustrated here:
40 40  
41 +<script id="oc-widget-main" src="https:~/~/cdn.onecount.net/js/all.min.js#%%%%%%%%%%%%%%%%"></script>
42 +
43 +The widget 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.
44 +
41 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 42  
43 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.
... ... @@ -66,14 +66,16 @@
66 66  
67 67  \\
68 68  
69 -=== Automation Widget ===
73 +=== NO LONGER USED: The following widget is no longer needed, 05/15/2022 ===
70 70  
71 -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.
75 +=== --Automation Widget-- ===
72 72  
73 -This snippet is placed inside head (<head></head>) and SHOULD BE PLACED AFTER any ad network slot definition code (DFP).
77 +--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.--
74 74  
75 -See Widget Bulder documentation for more information.
79 +--This snippet is placed inside head (<head></head>) and SHOULD BE PLACED AFTER any ad network slot definition code (DFP).--
76 76  
81 +--See Widget Bulder documentation for more information.--
82 +
77 77  === IVT Tracker and Noscript Tag ===
78 78  
79 79  _**The IVT tracker snippet identifies potential IVT traffic, and the noscript tag is needed to track requests when javascript is disabled.** _
... ... @@ -84,20 +84,12 @@
84 84  
85 85  === Banner Trackers ===
86 86  
87 -Banner widgets are used to track and report banner activity.
93 +Banner widgets are used to track and report banner activity. The banner widgets also track whether banner ads are "in view" on the user's screen. This is accomplished by a specific pixel that "checks-in" with ONEcount every three seconds to report whether the banner is still in view. This URL (v_js.php) may appear in the lower-left of your browser screen each time it is called, making it appear that v_js.php is loading and potentially slowing down the loading of the web page. This is not the case. If you view the load time in the developer tools of your browser, you will see this pixel is firing repeatedly, usually taking less than 10ms. Also, this pixel fires asynchronously, meaning in parallel with other elements on the page. So there is no impact on site performance from this pixel.
88 88  
89 89  There are two banner platforms supported within ONEcount: OpenX and DFP (Premium and Small Business).
90 90  
91 91  Widget Builder documentation provides widgets and directions for both platforms.
92 92  
93 -=== Third Party Trackers Modifications ===
94 -
95 -Usually websites will have third party trackers like Google Analytics, etc. installed on their website. A small piece of code needs to be added to those third party trackers so that ONEcount can pass the original referrer to those systems.
96 -
97 -We provide the code that needs to be added to your Google analytics code. See Widget Builder documenation.
98 -
99 -If any other third party trackers are being used on your website, please let your ONEcount account manager know ahead of time.
100 -
101 101  === ONEcount Pixel for Moat ===
102 102  
103 103  ONEcount can collect ad viewability data from Moat's realtime pixel. In order to send data to ONEcount, Moat can fire a pixel like like that in the Widget Builder to send data to ONEcount.
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -66715805
1 +77496791
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/66715805/Widget Implementation
1 +https://info.onecount.net//wiki/spaces/OD/pages/77496791/Widget Implementation