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.

Sample data generation workflow

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, campaigns, 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 BulgariaORCompany 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.

Visitors sample data

Sample data contains both anonymous visitors and registered contacts, distributed among reports for conversions, campaigns, 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)
  • Be part of the campaign audience, 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.

Audience defined by identifier property

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. 

Conversion definitions and campaigns timeframes

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. The reason is that you need to be able to define a campaign with a start date different than the current date, that is, in the past. The earliest possible date, on which you can set the campaign start is the date, on which the conversion is defined. You get data just for the past 30 days, independently of the time period, for which you want to track the campaign. As a result, when you populate the data center with data, you have reports with statistics for campaigns in status “Live”, which would not be the case if the campaign has the same starting date as the conversion report, equivalent to today.

Limitations

Creating custom scenarios in sample data centers enables you to define conversions, campaigns, 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.

General rules 
  • Up to 5 conversion definitions, each with 30 days calculation period are available
  • Up to 10 touchpoints are available
  • 1 A/B test with 3 page variations (one of which is the original page) with 2 goals defined
  • Data is imported for 30 days in the past
  • If you define a metric condition with Contains, StartsWith, or EndsWith, values are treated as equal. For example, if you define a touchpoint for contacts who played any video with .AVI file extension, all generated sentences are with an object “.AVI” and none has additional objects, such as “gettingStarted.avi” or “newFeatures.avi” objects.
  • Combinations with comparison rules, such as 'Any provided', 'Is not, 'Does not start with', 'Does not contain' and 'Does not end with' are not supported.
  • If you have multiple conditions with OR in the definition, imported sentences are only for the first one. For example, if you define a touchpoint with two conditions: visit progress.com OR visit telerik.com, imported data will be only for visit progress.com.
  • If you have more that 10 conditions in a definition, only the first 10 conditions will be processed.
  • If you have a Persona or Lead scoring with more that 10 rules, only the first 10 rules will be processed.
onversion tracking and campaigns 
  • Up to 2 campaigns for each conversion report
  • It is not recommended to use the email property for defining a conversion visitor segment to track and for defining the audience in the campaign. For details, see Audience defined by identifier property.
  • If you use one and the same interaction with positive and negative conditions for different features, you may get misleading reports. For example, you define a touchpoint as “visit progress.com“ and define a conversion by segmenting the audience to track with "did not visit progress.com". The attribution which you get in this case will be misleading.
  • To have any statistic in the New contacts summary, the conversion you define needs to include an interaction that prompts visitors to register and provide their email addresses.
    For the purposes of the demo generation data center, this excludes filling out a form or subscribing for a newsletter, for example. This metric will also be zero if no visitors completed the event. For details about this summary report, see New contacts.
  • Segmenting visitors to track or an audience with multiple rules for one and the same contact property is not supported. For example, if a rule states: "FirstName” starts with "P" AND “FirstName” ends with "son", a visitor can match just one of the rules and therefore will not qualify as part of the conversion or campaign. 
Lead scoring  If you define more that 4 lead scoring stages, statistics will be unrealistic due to data distribution.

 

 

Was this article helpful?