Data centers with custom scenarios

Your data center contains your custom demo scenario that you can use to evaluate or simply get more insights into Sitefinity Insight scoring models and features.

Still, you should be aware of the capabilities, as well as the limitations, of sample data centers with custom scenarios.

When you populate or repopulate data for a sample data center with custom scenario, the basic workflow is the following:

1. Previously generated data (if any) is deleted. This includes just the sample data, not the definitions of metrics or scoring models, such as conversion reports, scoring rules, and so on. The reason is that before importing data for visitors and interactions, no previous data should interfere with the newly generated one.
2. Data is generated for a predefined set of 300 contacts with the following contact information: first name, last name, email, company, address, country, phone, device, browser, web page and industry.
3. Generate sentences for the defined touchpoints, conversions, personalization reports, A/B test, persona and lead scoring rules.
4. Calculate the statistics, based on the newly generated sentences.

Keep in mind that data is generated for the minimum amount of rules required for a visitor to complete a conversion event. For example, if you define a conversion tracking with two rules: Country is Bulgaria OR Company is Progress, then data is generated only for the first rule since meeting either of the conditions matches the conversion event. The downside is that no data is generated for the second condition and you see a respective notification on the screen that this feature is unknown.

Sample data contains both anonymous visitors and registered contacts, distributed among reports for conversions, A/B tests, and persona and lead scoring models. Each time you populate or repopulate the data center with sample data, all data about visitors and contacts is deleted and then repopulated again. New interactions are generated, so that visitors and contacts:

• Pass the persona or lead scoring thresholds
• Be in the segment of visitors to track in the conversion report
• Hit touchpoints
• Visit page variations of the A/B tests and complete the goals defined (if any), and so on

Apart from anonymous visitors and registered contacts, the audience is allocated between converting and non-converting audience, otherwise all reports will show a 100% conversion rate.

Contacts are identified by their email address. If you use the email address as a segmentation filter for a conversion, only the predefined set of contacts will meet the condition and no new contacts that meet the condition are imported. The reason is when using rules that define audience segments, Sitefinity Insight uses the exact value of the filter, in that case the email address, for example @company.com. Thus, even if contacts are different, if they have the same emails because all email values are @company.com, contacts are mapped and the system treats them as one and the same contact due to the email mapping functionality. This functionality is turned on by default.

If you use any other personal data to define the audience segment of a conversion, new contacts that meet the conversion definition criteria are imported.

Therefore, filters for the Email identifier property are not supported in custom scenario data centers. 

In sample data centers with custom scenarios, the Defined on date of the conversion report is 30 days in the past from the date, on which you define the conversion.

Creating custom scenarios in sample data centers enables you to define conversions, touchpoints, persona and lead scoring rules that reflect the needs of your demo scenario or website. As a result, you get an idea of Sitefinity Insight features and types of reports, and later apply them in optimizing the digital experience on your actual website.

However, you need to be aware of several limitation points when exploring Sitefinity Insight with the Custom scenario data centers.