Skip to Content
Last modified by Admin User on 2025/06/27 12:15
From version 33.1
edited by Admin
on 2022/05/13 11:43
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
... ... @@ -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.** _
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -66715808
1 +77496791
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/66715808/Widget Implementation
1 +https://info.onecount.net//wiki/spaces/OD/pages/77496791/Widget Implementation