The siteVisit chain is triggered by the SiteVisitLoader component. This pipeline has no branches. Each processor, if successful, starts the one that follows.
Each processor uses a passed-in parameter retrieved from the log file to look up items in the Data Warehouse. For example, the lookupVisitor processor uses the profileId from the log file to look up the visitor in the ARF_USER table and return its ID, using an RQL query. If the visitor cannot be found, the processor attempts to load the visitor into ARF_USER table first, and then return the ARF_USER.ID. If this fails, the processor returns the “Unspecified” visitor. Similar patterns apply to the other lookup processors, although the algorithm varies.
The processors are:
lookupSiteVisitDay—Uses the session start timestamp in the log file to determine the starting day of the visit.lookupSiteVisitTime—Uses the session start timestamp in the log file to determine the starting time of the visit.lookupSiteVisitEndDay—Uses the session end timestamp in the log file to determine the ending day of the visit.lookupSiteVisitEndTimelookupSiteVisitEndDay—Uses the session end timestamp in the log file to determine the ending time of the visit.lookupVisitor—Uses the profile ID in the log file to look up the visitor in theARF_USERtable.lookupSiteVisitStimulusGroup—Reserved for future use. Currently returns the “Unspecified” stimulus group.lookupDemographic—Examines the visitor’s date-of-birth, gender, marital status and home region as defined in the Data Warehouse. It uses this information to look up the record in theARF_DEMOGRAPHICtable that classifies this user.logSiteVisit—Writes the row to theARF_SITE_VISITtable in the Data Warehouse.
