This chapter covers the following topics:
Ensure that you have set up the mandatory dependencies as outlined in the chapter, Verify Mandatory Dependencies.
Complete the mandatory steps required to start the Oracle Web Analytics Engine and begin capturing visits.
Set the profile option, Web Analytics: Enable E-Business Suite Tracking, to "Yes", at site level.
In the Oracle Web Analytics Administration Application Setup tab, set the following tracking parameters:
Visit Inactivity Period: A visit automatically ends after the period of inactivity defined in this field, in minutes. Note that a visitor who navigates to pages outside of Oracle Web Analytics tracking accumulates inactivity time; thus, although the visitor may be actively navigating these other pages, the Oracle Web Analytics engine will consider the visit to have ended due to the specified period of inactivity in these other pages. When a visit ends (either through inactivity time-out or user actions), the duration of the last page view is excluded from the reporting. The default value for this field is 30 minutes.
Enable persistent browser cookies: Set to Yes or No. Administrators can choose to disable tracking of anonymous visitors using persistent cookies by setting this flag to No. In this case, every new visit made to an Oracle Web Analytics-tracked site is attributed to a new, unique visitor. In addition, when this flag is No, administrators can no longer define the duration during which anonymous visitors are tracked (see the Persistent Cookie Expiration bullet point, below). For more details on the impact of setting this flag, refer to the disabling persistent client-side visitor tracking information in the section, "Web Tracking Infrastructure", in the chapter, Introduction to Oracle Web Analytics.
Persistent Cookie Expiration: Set this to an integer (in minutes). For example, set it to 60 minutes. The integer must be greater than zero and no more than 999. The default value is 360 days. If the value for Enable persistent browser cookies is No, then this field is hidden.
Note: Any updates in the value of the visit and visitor information will only affect future visits and visitors. No changes will be made to recorded visits.
Using traffic filters, Oracle Web Analytics administrators can filter out any IP address from the reporting data. For example, administrators may wish to filter sites from within the corporate intranet. When an IP address is entered into the Traffic Filters screen, the tracking engine still tracks the IP address activity, but the activity is not reported on. Following is the high-level procedure:
Obtain the IP address(s).
Enter the IP address(s) in the Oracle Web Analytics Administration UI Setup page.
For sites for which you wish to enable traffic filters, enable the Traffic Filter flag in the Update Site page.
Refer to the chapter, Administering Tracking Features, for more information.
Each site collecting data on visitors is required to have a privacy policy and opt-in/opt-out options available to visitors. Guest visitors to a site will always be opted in until they opt out. The privacy policy is available via a hyperlink in the lower portion of Oracle iStore Customer Application pages. After reviewing the policy, visitors may opt in or opt out of being tracked. Each time the visitor leaves the site and the inactivity period has expired (for opted in users), or if the visitor has cleared cookies from his browser between visits, the visitor must re-select his privacy option. For registered users who are authenticated by a site, the opt-in/opt-out preference is picked up from the customer's preference setting, not from the cookie. If an anonymous user set his privacy preference and then registers, the preference is carried over his new account. When the user logs in, the system applies his last saved preference regardless of his behavior while in anonymous mode.
If the profile option, IBE: Display Privacy Statement, is Yes at site level, the Privacy Statement link displays on all Customer Application pages.
To enable the page that displays after the customer selects the Privacy Statement link, you must set up the following display template-JSP mapping using Oracle iStore Site Administration Application:
Template name: Web tracking preferences
Template Programmatic Access Name: STORE_IBW_PRIVACY_PREF_D
Map template to the JSP: ibwCWadPrivacyPref.jsp
If Oracle Web Analytics is implemented and you have mapped the above template, this page following the Privacy Statement link selection displays a link, Edit your privacy preferences. Selecting this link takes the user to an Oracle Web Analytics page where he can select his opt-in/opt-out preference.
For additional information on implementing a privacy policy, see the "Privacy Policy" section in the "Administering Tracking Features" chapter of this guide, and the "Privacy Policy" topic in the chapter, "Implementing Site Management", in the Oracle iStore Implementation and Administration Guide.
This section discusses the tasks required to set up the Oracle Daily Business Intelligence (DBI) framework for Oracle Web Analytics.
Before implementing DBI, you may wish to give some thought to the following:
For optimum accuracy in product category reports, add all published site products under the product hierarchy. For more information, refer to the topic about setting up the product catalog hierarchy in the Oracle Daily Business Intelligence Implementation Guide.
Before performing the Site Migration, find a mapping of sites and operating units. See the section, "Run Site Migration Program", below, for more information.
Before you perform the initial data load, you should verify that you have reviewed and met all of the implementation considerations and prerequisites for the features and intelligence products that you are implementing. For more information, refer to the topic about performing the initial data load in the Oracle Daily Business Intelligence Implementation Guide.
For functional currency conversion, you must set the profile option, BIS: Treasury Rate Type. For more information, refer to the Oracle Daily Business Intelligence Implementation Guide.
Set the profile options listed in this section.
Oracle Web Analytics reports rely on Oracle Supply Chain Management to internally report data on booked orders, and this dependency requires setting the OM: DBI Installation profile option. When the profile option is Yes, Oracle Order Management records modified lines into a log table. The Update Order Management Base Summary process then picks up the changed records from the log table. If the profile is No, incremental collection of the data will not occur properly.
The profile option is used only by the reporting framework. The profile option provides the No option so that users using only Oracle Order Management do not unnecessarily log modified lines. The DBI concurrent processes used by Oracle Order Management purge the log table after every collection from it.
The system administrator can update this profile option at the user, responsibility, application, or site level; however, it should be set at the site level, since incremental collection should happen at the that level. The default value of this profile option is No.
This profile option specifies the number of top carts, top orders, top customers, and top products to display in the drill-down reports accessible from the Site Top Sales Activity Dashboard. Set to an integer at site level. The default value is 25, and it is recommend to use the default value unless there exists a compelling business case to change the value.
If this profile is changed, implementers need to run the initial load again.
Oracle Web Analytics reports require that you run a semi-automated migration script -- available as the iStore Minisite Migration concurrent program -- to migrate customer data in pre-Release 11.5.9 Oracle iStore to higher versions and enable the appearance of historical data in intelligence reports. This script populates the site identifier (Minisite_ID) column at the header level in the ASO_QUOTE_HEADERS_ALL table. The script can be run in three modes.
Important: A user with the iStore Concurrent Programs responsibility should run the concurrent program.
Values from the list of values are:
Evaluate: This is the default value. It allows administrators to run the program in a mode that populates only the program output log. Since the data migration does not actually take place, this allows you the opportunity to view the results of the program before committing to the migration.
To view the concurrent program output: After the request is submitted, in Oracle Forms select View, Requests to retrieve the View Request screen. Input the request ID to see a specific request. On the View Request screen, select the View Output button to view the output of the concurrent request.
Execute: In this mode, the data migration actually takes place.
Get List of Stores and Organization Identifiers: Provides a list of site and operating unit identifiers. Names and numbers for both sites and operating units are displayed in the list.
Important: If "Only Use Auto Defaulting Rules" (see Use Migration Rules, below) option is not selected, run the program in this mode before running in either of the other two modes.
Values from the LOV are:
Only Use Auto Defaulting Rules: This is the default value. Three rules are used: Cart Line, Organization to Store Mapping, and Unique Price List.
Only Use Organization to Store Mapping: Only the Organization to Store Mapping input, prior to running the migration, is used.
Use Defaulting Rules and Organization to Store Mapping: Initially the three auto default rules are used, then for the remaining carts, the user defined Organization to Store Mapping rule is used.
Enter a string to map each operating unit with a default site, using the following convention:
<operating unit identifier>:<site identifier>
See the following examples:
Operating Unit 1 Identifier (204) followed by Site 1 Identifier (10000), with a colon separating the two numbers: 204:10000
Operating Unit 2 Identifier (301) followed by Site 2 Identifier (10008) 301:10008
Note: To determine the Operating Unit and Site identifiers, run the program in Get List of Store and Organization Identifiers mode.
This value is hidden by default, as this option should only be used if required to reduce the risk of overwriting valid Site IDs with incorrect ones. Values are:
No (default): The concurrent program updates only carts having no site identifier at the cart header level.
Yes: The concurrent program updates all carts.
Note: If the value is No, to use this feature, administrators need to change the concurrent program definition. To change the default value of a parameter, log into Oracle Forms as system administrator and navigate to Concurrent, Program, Define. Query for the program, iStore Minisite Migration Program, and then select the Parameters button. For more information, see the Oracle Applications System Administrator's Guide.
After this program is run, the following migration rules are executed in this order:
If the cart line level is populated, the program populates the site identifier at the header level with the same value. The first line created in the cart is used to retrieve the site identifier.
Each shopping cart is attached to an operating unit at header level (the operating unit is defined in the MO: Operating Unit profile, set at responsibility level to a customer responsibility). A site may be associated either none or an unlimited number of customer responsibilities (each related to one operating unit). By using this information, the concurrent program retrieves the site associated with the operating unit defined at the cart header level.
Each cart is attached to the price list that was used to price the cart for the given party and party type. If site-based pricing is used, the price list identifier is stored in the IBE_MSITE_CURRENCIES table. When using site-based pricing, four price lists are supported per currency: one for walk-in users, one for registered B2C users, one for registered B2B users, and one for users associated with Oracle Partner Management. Depending on party, party type, and price list identifier on the shopping cart, the concurrent program finds the candidate sites and price lists.
When a migration rule is executed for a cart, these things can happen:
The migration rule retrieves one site. The cart site identifier column is updated accordingly and the rule evaluation stops for the cart.
The migration rule retrieves no site. The next rule is evaluated for the cart.
The migration rule retrieves multiple sites. If one unique site identifier is common to the two rules, the concurrent program stops there. If not, the next rule is evaluated.
When the parameter, Use Migration Rules, is set to Use Defaulting Rules and Organization to Store Mapping, if no site is retrieved for the cart using the defaulting rules, the user-defined mapping rules (store-organization mapping) are used to find the Site ID.
To set up the Oracle Web Analytics Administrator, assign the Web Analytics Administrator responsibility to a user. The Oracle Web Analytics Administrator responsibility gives the user access to all of the administrative and reporting menus available in Oracle Web Analytics.
See the appendix, Seeded User Data, for more information.
Oracle Web Analytics reports utilize the request sets (concurrent programs) created within the Daily Business Intelligence Administrator responsibility to populate the initial load of data. Refer to the Oracle Daily Business Intelligence Implementation Guide for more information.
After you have set up the administration application and the tracking engine, you may wish to expand your implementation. An integral component in the 360-degree view provided by the Oracle E-Business Suite, Oracle Web Analytics can optionally integrate the with following applications to extend its functionality:
Oracle Marketing: Using Oracle Marketing, you can define, execute, and manage marketing campaigns, budgets, and segments across all channels, as well as define promotions. You also use Oracle Marketing to set up lead generation. See "Set Up Leads", below, for more information.
Oracle Applications Technology Foundation: Using Oracle Applications Technology Foundation, you can manage users, set session time out parameters, set cookie properties, and more. See the Oracle Applications CRM System Administrator's Guide for more information.
Oracle Supply Chain Daily Business Intelligence: Using Oracle Supply Chain Daily Business Intelligence (DBI), you can provide access to order base summary information.
Oracle Quoting Daily Business Intelligence: Using Oracle Quoting Daily Business Intelligence (DBI), you can provide access to quote and cart base summary information.
Order Information Portal: Use the order information portal to provide access to order details information from the Top Orders report.
Oracle Web Analytics reports contain counts on 'A' Leads retrieved from Oracle iStore orders and abandoned carts. Leads are generated for a specific time frame using the iStore Lead Import Concurrent Program Request Set, which pulls customer data (such as name, address, phone numbers, etc.) from:
Submitted Oracle iStore orders
Active shopping carts that have expired in an Oracle iStore specialty site -- so called "abandoned" carts
Saved shopping carts that have expired in an Oracle iStore specialty site
The concurrent program set populates the lead import data into tables utilized by Oracle Sales and Oracle TeleSales. Oracle Sales and Oracle TeleSales users then run the Import Sales Leads program to complete the data-load process.
For more information on Oracle Sales and Oracle TeleSales, see the Oracle Sales Implementation Guide and the Oracle TeleSales Implementation Guide, available on OracleMetaLink.
The ranking engine categorizes Oracle iStore-imported leads when the Import Sales Leads concurrent program is run. Refer to the Oracle iStore Implementation and Administration Guide for further details.
Mapping rules used to map ranked leads to 'A' leads for reporting are set up in Oracle Marketing. For instructions detailing how to set up lead qualification, refer to the Oracle Daily Business Intelligence Implementation Guide and the Oracle Leads Management Implementation and Administration Guide.
Oracle Marketing Daily Business Intelligence (DBI) provides the flexibility to determine 'A' leads from different types of leads (e.g., hot leads, cold leads, etc.) based on user (Marketing DBI/Web Analytics user) discretion. Refer to the Oracle Daily Business Intelligence Implementation Guide and the Oracle Leads Management Implementation and Administration Guide for additional information on setting up mapping rules for lead ranking.