|
|
-
The honest answer is, "Depends." Tracking a web site on a handheld or wireless device will depend upon the browser used to view the site and its ability to render pages with javascript. Most PDAs have browsers capable of displaying javascript, however, browsers blocking javascript or browsers incapable of reading javascript will not allow LoadStats to correctly display all of the pertinent data typically associated with a common web visitor. LoadStats will still track the Page Views, but visitor specific data will not be captured or tracked.
|
-
If you have any questions or need further assistance, please e-mail support@load.com.
|
-
Tracking an SSL site with LoadStats is no different that tracking any web site. Follow the steps below to begin tracking pages on your web site using LoadStats: - Select the LoadStats account you would like to manage from the "Active Services" page. You will be directed to the default "Dashboard" page.
- Click the
 icon located on the left-hand navigation to expand the menu. Click "Settings" from the list. - Click "Web Site Tracking Code" located under the section titled "Tracking Codes".
|
-
LoadStats is aware of frames and does not need to be placed in the frameset html files. We strive to provide the most accurate statistics that we can, our processes have been verified by third parties, and are constantly tested to protect against false or lost impressions. Things to keep in mind when using LoadStats: - LoadStats Code should NOT be Double-Spaced
LoadStats will not track report page impressions because the code has been modified from its original form and will not communicate with our servers. - False Reports from a Frameset or Default Page
These page views should not be counted as impressions because they only facilitate the viewing of other pages that are also counted. (Tip: If the page is a destination for your users you should place the LoadStats code on it. If it is a means to direct traffic to another location, you probably should not track it. - Frame Sites Under a Different Domain
Framed web sites will NOT track properly if the frame set is not hosted under the same domain as the web page. A good example of this would be Free web sites hosted a Yahoo! and DNS is cloaked by a third provider. The Entry Page will not track properly because the domain of the Free web site is located under the Yahoo! domain name.
|
-
Listed below are common reasons why accounts with LoadStats activated may not be tracking or reporting statistics. - LoadStats Tracking Code Is Not Implemented
Verify that you have implemented the LoadStats Web Site Tracking Code on the pages that you wish to have tracked. Please see the Related Articles below for more information. - Visitors Have Not Come to Your Site
Once the LoadStats Web Site Tracking Code has been implemented, statistics will be generated immediately upon visitors entering your web site.
(Note: If no reports have been generated and you have verified that the Web Site Tracking Code has been implemented, it is possible that new visitors have not viewed your web site.) - LoadStats is Undergoing Maintenance
Load attempts to schedule maintenance during off-peak hours. We apologize for any interruption of service and any inconvenience this may cause.
|
-
To begin tracking pages on your web site using LoadStats, please follow the steps below: - Select the LoadStats account you would like to manage from the "Active Services" page. You will be directed to the default "Dashboard" page.
- Click the
 icon located on the left-hand navigation to expand the menu. Click "Settings" from the list. - Click "Web Site Tracking Code" located under the section titled "Tracking Codes".
|
-
For protection of our members and to maintain the integrity of an account, Load requires account holders to contact a Load representative to activate multiple instances of services in the Load system. Account managers can activate additional instances of any Load service under an existing Load account. For instance, if LoadStats is already in use under a given account/login, another instance of LoadStats may be activated for a new domain name using the same Load account. Please contact a representative by writing support@load.com for additional information.
|
-
Data collected by the LoadStats servers is stored for the initial term of the contract and any extensions of the contract. Therefore, all reports and data collected by LoadStats are available at any time by logging into the LoadStats administrative console. Accounts that do not maintain a current account status, whether through cancellation or payment default, will have their data immediately removed from the system upon cancellation of the service.
|
-
Modification of/or changes to the LoadStats Web Site Tracking Code may result in false web statistics being reported. Listed below are common changes made with Web Site Tracking Code, often times, unbeknownst to the user. - Word Wrap
The Web Site Tracking Code has been modified and wraps incorrectly on the web page due to settings in an HTML editor. - Double Spaced
Some Web page creation tools automatically double space code that has been pasted into a page. - All On One Line
explanation from here. - Web Page Application Modified LoadStats Code
explanation from here.
|
-
For each instance of LoadStats, a unique Web Site Tracking Code is generated. For this reason, clients will not be able to accurately differentiate or allocate unique visitors/page views across multiple web sites with only one tracking code. Fortunately, LoadStats can be set up to track multiple web sites under one (1) account. To set up multiple instances of LoadStats under your Load account, please contact a Load representative.
|
-
Web sites designed entirely in Flash require specific set up instructions to implement the LoadStats service. DO NOT confuse this type of site with an HTML page on which Flash may be embedded. HTML Pages with Flash
If your web site is designed in HTML and requests multiple pages from the server for site navigation, the standard Web Site Tracking Code will track your site when properly inserted. Flash / DHTML / Java
If your web site is designed in Flash, DHTML, or Java and makes one (1) request to the server for the entire duration of the user session, special LoadStats code is required for proper tracking. Please see the Related Articles below for more information.
|
-
Proper Web Site Tracking Code placement is imperative for accurate statistics and reports. Please see the example below for proper insertion of the tracking code. After <body> Tag
Placing the Web Site Tracking Code after the <body> tag (at the beginning) has a couple of inherent benefits: - Pages Are Tracked More Accurately
Web Pages with a lot of content may take longer to download and users may click on a link in your site and leave the page before it has completed downloading. With the tracking code immediately after the <body> tag, LoadStats will be able to accurately identify your user's behavior. - Limits Impact of Java Script Errors
LoadStats may not track web pages correctly if Java Script errors occur before the Web Site Tracking Code. Please see the Related Article below for more information.
Before </body> Tag
Placing the Web Site Tracking Code before the </body> tag (at the end) allows you to identify if visitors to your site had an opportunity to view all the elements on your web pages. However, placing the Web Site Tracking Code directly before the </body> tag could leave you susceptible to a few problems: - Inaccurate Page View Count
This can happen due to Java Script errors occurring before the Web Site Tracking Code, which may render LoadStats unable to communicate with the servers. At the same rate, any web pages that do not fully download on a user's browser may not be tracked by LoadStats if the Tracking Code is placed at the bottom of the page. - False Site Navigation Reports
Navigations Paths reports may be skewed if the Web Site Tracking Code is not downloaded by the user's browser. This is most likely to occur on pages with large amounts of content, whereby users know where they want to go on your site, and click the appropriate link before the page is completely downloaded.
|
-
Data collected by the LoadStats servers is stored for the initial term of the contract and any extensions of that contract. Therefore, all reports and data collected by LoadStats are available at any time by logging into the LoadStats administrative console. Be careful! Accounts that do not maintain a current account status, whether through cancellation or payment default, will have their data immediately removed from the system upon cancellation of the service.
|
-
Good question. Before LoadStats can begin tracking statistics for your web site, you must insert the LoadStats Web Site Tracking Code on each page your wish to have tracked. Every instance of LoadStats has uniquely generated tracking code designated for a specific web site. Please follow the steps below to implement LoadStats for your site. 1. Login to Load Admin
Go to http://www.load.com/. Click Client Login
2. Select a LoadStats Account
Click the instance of LoadStats you would like to manage.
3. Click System Settings
Located on the left-hand navigation in the LoadStats menu.
4. Select a Web Site Tracking Code
Follow the instructions as outlined on the page.
If you have any questions or need further assistance, please e-mail support@load.com.
|
-
Web pages with Java Script errors may cause LoadStats to function improperly. In most testing scenarios conducted by Load's development team, LoadStats reported statistics and page views accurately. However, in a few instances under testing, Web pages with Java Script errors occuring before/above the Web Site Tracking Code did not communicate with the LoadStats servers. In other instances, Java Script errors did not allow Web pages to load properly and failed to report data to the LoadStats servers.
Please verify that all Java Script code placed on your Web pages works properly to insure the greatest accuracy for your web site statistics. If you have any questions please contact us by writing to support@load.com.
|
|
|
|