Your data center is to contain your custom demo scenario that you can use to evaluate or simply get more insights into Digital Experience Cloud 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:
Keep in mind that data is generated for the minimum amount of rules required for a contact to pass a conversion tracking condition. 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 condition. 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 known and unknown contacts, distributed among reports for conversion tracking, campaigns, A/B test, and persona and lead scoring models. Each time you populate or repopulate the data center with sample data, all data about known and unknown contacts is deleted and then repopulated again. New interactions are generated, so that known and unknown contacts:
Apart from known and unknown contacts, contacts are allocated between converting and non-converting audience, otherwise all reports will show a 100% conversion rate.
Known contacts are identified by their email address. If you use the email address as a segmentation filter for a conversion tracking report, 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 conditions that define audience segments, Digital Experience Cloud 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 tracking report, new contacts that meet the report conditions 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 tracking report is 30 days in the past from the date, on which you define the conversion tracking report. 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 tracking report 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 tracking report, equivalent to today.
Creating custom scenarios in sample data centers enables you to define conversion tracking reports, 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 Digital Experience Cloud 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 Digital Experience Cloud with the Custom scenario data centers.
Back To Top