Installation and Deployment Installing and Deploying the Webtrends WSP Feature Package Deployment of the WSP will copy all the JS files from the .WSP file’s \Layouts\WebtrendsAssets\ directory into the server’s layouts directory, usually located in: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\XX\TEMPLATE\LAYOUTS\WebtrendsAssets where XX is the appropriate number for your SharePoint version, e.g. 15. Log on to the SharePoint server with a local administrator account. Copy the WAA_2013_<SCOPE>.WSP to the desktop, where <SCOPE> is the desired scope version ( Farm , WebApp , Site , Web ). Open Windows Run ( Win + R ). Type services.msc and press Enter . Ensure that the SharePoint Administration service is running. Ensure that the SharePoint Timer Service is running. Return to the Desktop . Open SharePoint 20XX Management Shell as an Administrator . Run the following command, using the proper file name and path of the scoped

profile, mouse over the profile and click Reanalyze . When you are prompted to confirm the deletion, select the After clearing analysis data, start analysis immediately check box. Alternately, mouse over the profile and click Analyze Now in the Profiles dialog after you confirm the deletion. If you do not reanalyze, your custom report will not include the data from the time frame that was analyzed before you added the new report. Using Preconfigured Custom Reports Webtrends Analytics provides a large number of preconfigured custom reports. To use preconfigured custom reports, enable them in the profile and in the template as described in steps 7-16 in “How to Configure Custom Reports Details,” above. Using Custom Report Filters You create custom report filters using the Report Configuration options for custom reports, and apply them to individual custom report tables. For more information, see “Creating Custom Report Filters.” Using Performance Dashboards

About Features are optional WSP (Windows SharePoint) files that can be installed in the SharePoint servers to provide additional functionality. These often provide custom web parts or other desirable customizations. The Webtrends Advanced Analytics WSP Feature provides the ability to add the tracking JavaScript files to the environment via server-side scripting. The code is primarily responsible for adding a <script> block to the pages that pulls in the webtrends.load.js file which provides the tag configuration, and then loads the additional Webtrends related scripts. This can be scoped at the Farm , Web Application , Site Collection , or Web scope. Note: The original Features were created using SharePoint 2013 and contain references to 2013 file names. This is inconsequential, and the same package is supported on SharePoint 2013 , 2016 , and 2019 (classic view) environments. Farm Scope When using the Farm scope, the feature is available in the Central Administration

Release 2.0.3 (2022-04-04) Enhancement: Improve Tracking Performance Updated logic to eliminate unnecessary calls to the SharePoint API (Issues 2991, 2992, 2993) The process of retrieving user properties has been updated to reduce the amount of data being requested. Extraneous API calls have been removed when determining the web parts on a page and when determining the site collection title. Fix: Correct Search Results Page Tracking Updated code to prevent duplicate page view events when moving from a SharePoint Online homepage to a search results page (Issue 3089) Previously, SharePoint Online did not fire the navigatedEnd event when starting on the homepage and moving to the search results page. Microsoft has corrected this behavior, so the tracking code was updated accordingly. Fix: Correct Tracking of Search Refiners in SharePoint 2019 Updated code to track usage of search refiners and scope changes in SharePoint 2019 (Issue 3089

The sample applications that ship with the Android Analytics SDK are designed to give you, the developer, real-world examples of how to use the libraries. The app shows off how to use the Analytics parts of the SDK with your app. Setting Up the Sample App The sample applications can be found Here . Within this zip you will find the WTSampleApp folder. Download the application to your local machine. Ensure you have the latest Android Studio installed on your system. For more information on installing and using Android Studio, see "Instrumenting an Android Application" for details. Install JDK 1.7 or above in your local machine and make it available for Android Studio by setting under File -> Project Structure -> SDK location -> JDK location Import Sample App Project into the Android Studio under Import project ->your-folder-path/mobile-sdk-sample-apps/WTSampleApp Install the Android Webtrends SDK from

s Analytics software, but do not use SmartSource tags to configure Webtrends, you can use this method to track scenarios. Alternatively, you can configure Scenario Analysis using SmartSource tags, which is the best practice for those using Webtrends Analytics On Demand. For more information, see “Configuring Scenario Analysis Using SmartSource Tags,” above. To create a Scenario Analysis definition: In the left pane, click Administration > Web Analysis > Report Configuration > Scenario Analysis . Click New . In the Name text box, type the name to identify this Scenario in the Administration interface. Leave the SmartSource Identification String text box clear. Type a title for this definition in the Report Title text box. When you add or edit a template, the report title identifies the scenario in the list of available reports. In the Short Description text box, type an informative description for report users. In the Help Card text box, provide explanatory information for

Data Source Time Zone The Web server time zone field contains the time zone of your web server. Webtrends uses this time zone to translate date and time fields in your web activity data to local time. A day’s worth of data is determined by the time zone selected, setting the boundaries for daily unique visitors. JavaScript Example: window.webtrendsAsyncInit = function () { var dcs = new Webtrends.dcs(); dcs.init( { dcsid: "dcs9x99xxxx9xxx9xx9xxxx9x_9x9x", timezone: -8 }); dcs.track(); }

"false" forConfigKey:kWTConfigDebug persists:YES]; For a full list of configurable settings, see the Analytics Advanced Configuration Guide. Pausing/Resuming Event Sending Here’s an example of how to pause then resume event sending: Swift WTDataCollector.sharedCollector().pause() WTDataCollector.sharedCollector().resume() Objective-C [[WTDataCollector sharedCollector] pause]; [[WTDataCollector sharedCollector] resume];

profiles/{Profile ID}/periods returns the time periods for a given report. Method: GET URI: /profiles/{Profile ID}/periods/ Note: Add any optional parameters to the end of the URI. If you change the order of URI or required parameters, or place optional parameters before them, the call will not work. Version number The version number you will use is dependant upon the version of Analytics you have installed. Analytics versions 9.5 and below, use v2_0. Analytics versions 9.5.1 and above will use v2_1. Example Request https://myDomain.com/{version}/ReportService/profiles/K729vc8Qqj5/periods/?format=xml Example Response 2023m12d08 2023m12d09 2023m12d10 2023w50 2023m12 2023q04 2023 2023m12d11 2023m12d12 2023m12d13 2023m12d14 2023w51 ... 2024m03d21 2024m03d22 2024w12 2024m03 2024m03d23 2024m03d24 2024w13 2024m03d25 2024m03d26 2024m03d27 2024m03d28 2024m03d29 2024m01d12 Parameters: Format format = return data format Example: specifying data formats Data format Parameter and value JSON format=json XML format=xml

Local Policies > User Rights Assignment. Add the service account to the following local security policies (regardless of whether the user already belongs to existing groups in these policies). Act as part of the operating system Allow log on locally Debug programs Log on as a service Add the service account to the Local Administrators group: Open the Server Manager. Navigate to Local Users and Groups/Groups. Add the service account to the Administrators group. Turn off User Account Control (UAC) Note User Account Control must be disabled to install Webtrends Analytics. If you do not disable UAC, the installation fails and returns an error code (1001, 1603) or a message about account restrictions. Open Control Panel. Click User Accounts. Click User Accounts. Click Change User Account Control Settings. Drag the slider bar to Never Notify. Click OK. Run Windows Update to get the latest patches for the installed components

If your web site content is dynamically generated, URL Parameter Analysis helps you understand requests for content more effectively by creating reports that show which parameters are used in page requests. Note Webtrends Analytics has several features that affect reporting on dynamic page URLs. If you want to decide what parameters to include in your URLs so you can improve the standard page reports such as the Pages report, you should use URL Rebuilding. If you have problems reporting on non-standard URLs and you want to modify your URL data by searching and replacing strings of data, you should use URL Search and Replace. Understanding URL Parameter Analysis The following diagram shows the structure of a URL. In addition to the protocol, the domain name, and a path or directory, a URL frequently includes several query parameters that define a dynamically created page request. URL parameters are typically

Analytics - Embedded Browser Events Guide Document The Webtrends SDK provides a method of sharing session information between a parent application, and an embedded UIWebView. After following the steps outlined in Implementation, any app implementing the iOS SDK will be able to see and log events generated by the Webtrends JavaScript tag. Requirements The native app must implement the Webtrends Mobile Library for iOS, the web content must be tagged with the Webtrends JavaScript tag, and you must be familiar with iOS UIWebViews. Implementation Using WKWebview When using WKWebview, conform to WKNavigationDelegate, and implement -webView:decidePolicyForNavigationAction:decisionHandler: Include the following inside your method: Swift func webView(webView: WKWebView, decidePolicyForNavigationAction navigationAction: WKNavigationAction, decisionHandler: (WKNavigationActionPolicy) -> Void) { let shouldStart = WTWebViewDelegate.shouldStartLoadWithRequest(navigationAction.request) if !shouldStart { decisionHandler(.Cancel) return } // Any custom decision policy code. Make sure your code calls decisionHandler with your chosen action policy. } Objective-C - (void)webView:(WKWebView *)webView decidePolicyForNavigationAction:(WKNavigationAction *)navigationAction

YYYY]-[MM]-[DD-3]" will be interpreted as "2008-09-11" If today is October 15, 2008. "[YYYY]-[MM-1]-01" will be interpreted as "2008-09-01" If today is November 16, 2008. "[YYYY+5]-[MM+3]-[DD]" will be interpreted as "2014-02-16" If today is January 1, 2008. "[YYYY]-[MM]-[DD-1]" will be interpreted as "2007-12-31" Schedule and Date Macro HINTS: To get an end-of-month report, schedule a report to run on "1" (first day of month), set the Start Date to "[YYYY]-[MM-1]-01" and set the End Date to "[YYYY]-[MM]-[DD-1]" To get an end-of-week (ending on Saturday) report, schedule a report to run on "Sunday", set the Start Date to "[YYYY]-[MM]-[DD-7]" and set the End Date to "[YYYY]-[MM]-[DD-1]" To get "daily" reports that cover yesterday's activity

/profiles/{Profile ID}/reports/{Report ID}/?period={Period} returns the report data for a given period. Method: GET URI: /profiles/{Profile ID}/reports/{Report ID}/?period={Period} Note: Add any optional parameters to the end of the URI. If you change the order of URI or required parameters, or place optional parameters before them, the call will not work. Version number The version number you will use is dependant upon the version of Analytics you have installed. Analytics versions 9.5 and below, use v2_0. Analytics versions 9.5.1 and above will use v2_1. Example Request https://myDomain.com/{version}/ReportService/profiles/CxoSsHxKlF6/reports/42df19b6d9f2/?period=current_month&format=xml Example Response 18079 CxoSsHxKlF6 42df19b6d9f2 Cities false dimensional false false true topcities true all false 3/17/2009 0:10:08 engine 4031.25 Visits Users-0 0 true false 107538 10600 10056 9466 7368 1

If you use Webtrends Analytics software, you can use the Intranet Domains feature to track usage of your corporate intranet and to identify the activity on your web site generated by internal users. Typically within large organizations, certain subnets or ranges of IP addresses represent a department, area, or location within an organization. Using intranet domains, you can define the domains that identify an area of your organization by country, state, city, department, or even individual workstation. Webtrends includes this information in geographic reports and in the Organizations and Domains reports. To configure intranet domains: In the left pane, click Administration > Web Analysis > Report Configuration> Intranet Domains . Click New . In the Domain Name text box, specify a name to identify this intranet domain definition in reports. In the Description text box, provide a description to identify this intranet domain definition in Webtrends Administration. Select the location of the domain

Web analytics is about making business sense out of web visitor behavior – the same common-sense analysis that business professionals have been applying to traditional offline business for decades. Gaining the appropriate insight to enable your organization to make smarter business decisions means understanding your site’s business objectives and determining the appropriate web metrics to provide that information. Today’s business environment typically involves working at remote and off-site locations. Consequently, the people responsible for the web site and those analyzing visitor activity on the web site to measure web metrics often do not work side-by-side. That is, they are frequently in different groups and locations. This situation necessitates coordination between developing and delivering content, and reporting and analyzing the activity results. To facilitate interaction between departments, locations and individuals, Webtrends provides a feature designed to place the power of analysis into the hands of

Each data collection event sent by the Webtrends Library automatically includes a collection of parameters, described here. Understanding Webtrends Parameters Webtrends parameters are the basis of many Webtrends reports. Many of these parameters are populated automatically when you use the methods supported by the Mobile Library. Although you do not need these parameters to implement the Webtrends Mobile Library and instrument your application, they can help you understand the report output generated by the data you collect and to create reports and profiles in Webtrends. For information about how each query parameter is used in Webtrends reporting and the values it supports, see the Query Parameter Reference. Parameters Sent for Every Event Every event type sends different values for a set of Webtrends Parameters. These are set either manually (using manual events) or automatically (when using automatics). In addition to these, all events contain the following Webtrends parameters: Device

General Regardless of the installation method chose, the end result of the tagging implementation is the insertion of multiple JavaScript files into the site that are loaded by the visiting client browser. These JavaScript files gather the desired data and send it to Webtrends SDC logging servers as a 1x1 pixel image request, known as a web beacon . Each page load or link click can trigger a new beacon to the logging servers, to be analyzed by the Webtrends Analytics engine. Additional events for video tracking or similar technologies may also occur. JavaScript Files The JavaScript files can be seen in the web browsers Developer Tools Debugger or Sources (Chrome) tab. The list of JavaScript files may vary on each installation method slightly. However, you should always expect the webtrends.js and webtrends.sp.js to appear in the debugger sources at a minimum. The webtrends.load.js file

ecognize the first-party cookie method that you use. By default, the JavaScript tag generates the first-party cookie for you. For more information, see “Using the JavaScript Tag to Track Cookies,” below. If you use Webtrends software without SmartSource Data Collector , you simply need to create a Session Tracking definition configured to use your cookie. Using the JavaScript Tag to Track Cookies If you use Webtrends On Demand or Webtrends software with SmartSource Data Collector, the JavaScript tag is configured to track first-party cookies by default. Use the Tag Builder to create your tag and specify any additional cookie settings. The following procedure has four main steps. Use the following steps in sequence to configure first-party cookie tracking. Step 1: Build a JavaScript tag. Use the Tag Builder at tagbuilder.webtrends.com to create your tag and specify any additional cookie settings. Step 2: Implement the JavaScript

Removing the Webtrends App Extension from a Single Site Navigate to the desired Site. Open site Settings (the gear icon in the upper right). Open the Site contents . Switch to classic experience if necessary. Hover over the Webtrends SharePoint App Extension 2019 icon. Click the ... link in the upper right. Click DELETE in the hover card. Repeat for additional sites as needed. Note: Application Extensions are web scoped, and you will need to remove the extension from each sub site as well as the site collection as needed. Removing the Webtrends App Extension from Multiple Sites Removal of the Webtrends SharePoint 2019 Modern View Extension from multiple sites simultaneously requires the use of PowerShell scripting. Note: Please see various online blog articles on retracting extensions via PowerShell. Note: Technical Support may be able to offer an officially unsupported PowerShell script for you to customize for your environment. Removing the