When Visitor data is pushed from the Send2CRM client, this automatically populates a number of Visitor-related objects in Salesforce.
Visitor
The Visitor object is the master record for each unique identified Visitor. It stores:
Date/time first and last seen
Total session count, durations, and Goal values
A lookup to the relevant form target object(s)
All analytics data can be related back to the Visitor object.
Visitor Facets
A unique list of Facets applied to the Visitor.
Visitor Goals
The total value for each Goal the Visitor triggered.
Visitor Stats
The total count of each type of Session Event for the Visitor, by interaction date.
Session
Stores the summary of a single visit. The following general information is collected for each Session where possible:
Unique id shared with the browser client
Start and end date/time
Browser, device, operating system
IP address, country, timezone, language
First and last page visited
Session Stats
The total count of each type of Session Event for the Session. For Goal events, the total Goal value is stored rather than the count.
Data retention
Session Events are not stored in Salesforce as individual records , as this could be a vast amount of information. Summaries are automatically created into the Visitor and Session Stats objects. You may also set automation to process any Event values.
Session data is automatically limited by the Maximum Sessions setting (10 by default). When a single Visitor has more than this number of Sessions, the oldest is removed. Change the setting to 0 to disable Session deletion.
All Visitor objects retain data indefinitely. The summary values in these objects still include Session data that has been deleted; it may even include Sessions that were never pushed to Salesforce if the Visitor accrued data for a long period before becoming identified.
If the Store Event Data setting is enabled, events are saved as JSON against the Session. We recommend against disabling Session deletion if this is enabled.