This chapter covers the following topics:
Oracle Web Analytics concurrent programs include:
Purge Tracking Data
Change Tracking Sequence Definition
Fact Population Program
Recategorize Referral
The Oracle Web Analytics Purge Tracking Data concurrent program allows administrators to purge raw click stream data generated from visits. Within specified dates, the program deletes all visit, visitor, and page view data that occur for visits in that period. After the program runs, there is no way to recover reporting data for the purge period. Use the Oracle Web Analytics Administrator responsibility to run this concurrent program.
Administrators can run the program in two modes, either in execution or in evaluation mode. In execution mode the actual data purge is processed, whereas in evaluation mode, only the statistics of the data that would be purged are reported without the actual purge operation.
This concurrent program allows a period input (start and end dates). The default start date is populated with an editable end date of the most recent purge. The end date is left empty. If no purges have been run, the start date is left empty. Both the start and end dates are required fields.
The concurrent program generates a report output with the following information about the data purge:
Date: This is the date the program was executed.
Mode: This displays whether the program was run in evaluation or execution modes. True means execution mode, and False means evaluation mode.
From: This shows the start and end dates of the purge.
Report statistics area showing the following:
Number of page views purged
Number of visits purged
Number of visitors purged
This program sets the increment factor by which highest unique visit and visitor identifiers are determined. Rather than hitting the database each time a unique visit and visitor identifier is generated, Oracle Web Analytics caches a series of identifiers in the Web server and increments the visit and visitor identified until it reaches the upper bound. Reducing the database calls improves the efficiency of the tracking code and reduces the impact on the tracked Web applications.
The following are the input parameters for the program:
Visit ID: The value indicates the number of visit IDs cached by the tracking engine. The value is updated as the incremental factor for the database sequence, IBW_VISIT_COUNTER_S1.
Visitor ID: The value indicates the number of visitor IDs cached by the tracking engine. The value is updated as the incremental factor for the database sequence, IBW_VISIT_COUNTER_S1.
This program generates the unique visit and visitor identifiers to track and identify each unique visit and visitor.
This program migrates the data from temporary schema to the Oracle Web Analytics fact/transaction schema. The fact population program extracts, formats, and loads the raw click stream data and links it to the Oracle E-Business Suite metrics, enabling analysis along the conversion pipeline. Broadly, it does the following:
Calculates page view metrics
Validates and stores events
Propagates campaigns and referrals along visits
Note: For Oracle Web Analytics to pick up all Express Checkout orders, the iStore - Express Checkout Order Submission concurrent program must be run before running Web Analytics: Fact Population Program concurrent program.
This program re-categorizes referrals. Referrals are mapped to categories based on the referral URL specified. Referral URLs can be modified and associated with new categories. The changes are only affected for visits captured after the changes applied to the referral categories. To associate past referral URLs to new categories, administrators need to run the Recategorize Referral concurrent program. See the chapter, Administering Tracking Features, for more information on entering and updating referral categories.