Data captured due to site visitors’ interactions with RPI landing and other web pages, and stored in the realtime cache, can then be persisted in a series of tables in the RPI data warehouse.
The following tables are used to record data gathered in respect of visitors’ submission of web forms:
•RPI_WebForm
Stores details of RPI web forms.
o FormID: unique identifier of a web form.
o FormName: name of a web form.
•RPI_WebFormSubmission
Stores records of visitors’ submissions of RPI web forms.
o FormSubmissionID: unique ID representing a visitor’s submission of a web form.
o FormID: unique identifier of a web form.
o SubmissionDate: date and time at which a web form was submitted.
o EmailAddress: email address captured at web form submission.
o ChannelExecutionID: unique ID representing an instance of outbound fulfilment having been undertaken by RPI.
o RPContactID: unique ID referencing an RPI offer history record.
o VisitorID: ID uniquely identifying a site visitor.
o PublishHistoryID: unique ID representing the publishing of an RPI web form.
o Fields: when system configuration setting FormSubmissionPersistFieldsAsJSON set to true, this field is used to persist form fields as JSON.
•RPI_WebFormFieldSubmission
o Stores records of values captured for specific RPI web form fields at web form submission.
o FormFieldSubmissionID: unique ID associated with capture of data within a specific form field.
o FormID: unique identifier of a web form.
o FieldName: name of the field.
o FieldValue: data captured in the field.
Data in these contexts is collated using the Web Form Processor system task.
The following tables are populated by the Web Cache Data Importer task:
•RPI_WebVisitors
Persists details of RPI Realtime visitors.
o VisitorID: ID uniquely identifying a site visitor.
o FirstVisitDate: date and time of first visit by a visitor.
o LastVisitDate: date and time of most recent visit by a visitor.
•RPI_WebVisitorsDecisions
Persists details of decisions made in respect of RPI Realtime visitors.
o VisitorID: ID uniquely identifying a site visitor.
o DecisionID: publish ID uniquely identifying the RPI file in respect of which a decision was made.
o ContentName: RPI file name.
o DecisionResult: ordinal number of content served.
o PageInstanceID: unique ID of instance of landing page in which decision made, or unique ID of interaction activity if decision made in outbound realtime mode.
o DecisionDate: date and time when decision was made.
o DeviceID: ID of the device to which content was served.
o ResultID: unique ID representing the instance of the content’s being served to the visitor.
o DecisionContent: stores text content published to the cache (up to a maximum of 100 characters). If more than 100 characters are returned, nothing is stored in this column.
o ContentPath: populated if content published to a web publish site.
o ContentFormat: one of TEXT, HTML, JSON or XML.
o ContextName: populated if content published using a context.
o ContextSlotName: populated if content published using a context slot (if only a context supplied, set to ‘rpidefault’.
o DefaultResult: ordinal number of default content to be served (if appropriate).
o Source: e.g. landing page name, ‘API’.
o ImpressionID: ID representing a visit to e.g. a web page. Note that a given impression may reference multiple results.
•RPI_WebVisitorsParameters
Persists details of parameters passed in respect of RPI Realtime visitors when making calls to API endpoints.
o VisitorID: ID uniquely identifying a site visitor.
o FieldName: name of parameter.
o Value: parameter value.
o UpdateDate: date and time of capture of parameter value.
o DeviceID: ID of the device to which content was served.
A CacheOutputExclusions array property within the RPI Realtime appSettings file allows you specify one or more parameter names. Inclusion of a parameter name within the setting results in its being ignored when the Web Cache Data Importer task populates RPI_WebVisitorsParameters.
•RPI_WebVisitorsScores
Persists details of RPI Realtime visitors’ decision scorecard scores.
o VisitorID: ID uniquely identifying a site visitor.
o ScorecardIdentifier: identifier property, captured at decision scorecard toolbox.
o PublishID: ID of smart asset in which decision scorecard utilized.
o Score: score assigned to the visitor in this context.
o UpdateDate: date and time of score’s being captured.
o DeviceID: ID of the device to which content was served.
•RPI_WebPages
Persists details of landing or external web pages visited by RPI Realtime visitors.
o VisitorID: ID uniquely identifying a site visitor.
o PageName: name of the page.
o PageInstanceID: RPI landing pages only; represents unique instance of publishing of the same.
o VisitDate: date and time of page visit.
o DeviceID: ID of the device to which content was served.
o ImpressionID: typically a unique viewing of a page by a visitor.
o HostDomain: domain of site hosting the web page.
•RPI_WebGoals
Persists details of goal smart asset goal attainment by RPI Realtime visitors.
o VisitorID: ID uniquely identifying a site visitor.
o GoalName: name of the goal.
o PageInstanceID: RPI landing pages only; represents unique instance of publishing of the same.
o AttainedDate: date and time at which the goal was attained.
o DeviceID: ID of the device to which content was served.
•RPI_WebEvents
Persists details of RPI web events. The table is populated if system configuration settings WebCacheOutputEventData is set to True.
o VisitorID: ID uniquely identifying a site visitor.
o DeviceID: ID of the device to which content was served.
o ImpressionID: typically a unique viewing of a page by a visitor.
o EventTime: date and time of the event’s occurrence.
o EventName: name of the event.
o EventDetail: additional detail captured along with an event (e.g. the URL associated with a Link Click event).
o MetricValue: numerical value captured along with an event.
o RPContactID: unique ID referencing an RPI offer history record.
o ChannelExecutionID: unique ID representing an instance of outbound fulfilment having been undertaken by RPI.
o PageInstanceID: RPI landing pages only; represents unique instance of publishing of the same.
o SourceReference: URL (external page only)
o EventMetadata: any metadata associated with the event (list of name/value pairs).
•RPI_WebDevices
Stores details of devices upon which RPI Realtime content viewed.
o VisitorID: ID uniquely identifying a site visitor.
o IPAddress: the visitor’s IP address.
o UserAgent: user agent string, as provided by the visitor’s device.
o FirstVisitDate: date and time of first visit by a visitor.
o LastVisitDate: date and time of most recent visit by a visitor.
The following tables are used to persist file metadata captured at publish:
•RPI_WebForm_Meta
o PublishHistoryID: unique ID representing the publishing of an RPI web form.
o PublishDate: date and time at which the web form was published.
o FormName: name of the web form.
o FormMeta: any RPI file metadata captured in respect of the web form (list of name/value pairs).
•RPI_WebPages_Meta
o PageInstanceID: RPI landing pages only; represents unique instance of publishing of the same.
o PublishDate: date and time at which the landing page was published.
o FileName: file name of the landing page.
o PageName: page name of the landing page.
o SiteName: name of the RPI web publish site to which published.
o SiteFolderName: name of the folder within the same.
o PageMeta: any RPI file metadata captured in respect of the landing page (list of name/value pairs).
•RPI_WebDecisions_Meta
o PublishHistoryID: unique ID representing the publishing of a smart asset.
o DecisionID: publish ID uniquely identifying the RPI file in respect of which a decision was made.
o DecisionResult: ordinal number of content served.
o LastPublishDate: date and time of asset’s most recent publishing.
o DecisionMeta: any RPI file metadata captured in respect of the smart asset (list of name/value pairs).