�۶���Ƶ

Select Harmonized data from the left rail.

Select Dataset rules from the top bar. You see a table of the dataset rules.

In Dataset details, select a dataset from Select dataset to begin configuration. In the list, datasets are categorized in Consumer Experience Events, �۶���Ƶ Analytics, Experience Event and, Summary.

Select a day for the Start of the week.

Select Daily, Weekly, Monthly or Yearly for Granularity.

When you have selected a dataset of the Summary category, select Aggregation or Replacement for Data restatement is by.

Reporting data from publishers is very important to marketing analysts since working with publishers often implies significant spend, and changes in the reporting data may result in very different insights and investment plans. Furthermore, marketing analysts need accurate data to derive the right insights and present convincing proposals to gain stakeholder confidence. However, these publishers, such as Google and Facebook, often restate or delete reporting data as they reconcile their data. The time frame for most of the changes is within 7 days of the reported media performance. Additional changes in the data are possible within 30 days. In general, after 30 days, books are considered closed and data complete.

Mix Modeler supports data restatement. To ensure that the data that is used for reporting, modeling, and planning is accurate. And that the data is able to support the brand and marketing analyst’s expectations and needs.

You can send restated rows of summary data as incremental rows in an Experience Platform dataset and the harmonization service updates the harmonized dataset with that restated data. Similarly, you can also remove rows of summary data that needs to be reflected in the harmonization service.

In the Map to harmonized fields section:

1. Select a harmonized field from Standard harmonized field.

2. When the selected harmonized field is of type metric:

   1. Select Count or Sum from Mapping type.

   2. Select an AEP dataset field that you want the harmonized field to map to by default.

3. When the selected field is of type dimension:

   1. Select Map Into or Case from Mapping type.

   2. When you have selected Map Into, select Field and AEP dataset field or Value and a default value to map the harmonized field by default to the dataset field or entered value.

   3. When you select Case, select Field and AEP dataset field or Value and a default value to map the harmonized field by default to the dataset field or entered value.

      1. To set values explicitly, you define one or more cases, consisting of one or more conditions. Each condition can check for a specific AEP dataset field whether it Exists or Not Exists or whether it Contains, Not Contains, Equals, Not Equals, Starts With, or Ends With a value entered at Enter input value.

      2. To add another case, select Add case, to add another condition, select Add condition.

      3. To delete a case or condition, select in the corresponding container.

      4. To select whether any or all the conditions should apply for a case, select Any of or All of.

      5. To set the outcome value for a case, enter the value at Then.

   The example below

   • uses a Map Into Mapping type to map the Channel Type At Source harmonized field to the channel_type field from the Luma Transactions dataset.

   • uses a Case Mapping type to map conditionally the value of the marketing.campaignName field in the Luma Transactions dataset to the Campaign harmonized field. The Campaign harmonized field is set to:

     • Black Friday when the marketing.campaignName is _black_friday or BlackFriday.
     • to the value of the marketing.campaignName in all other cases.

     

   When you map a standard harmonized field from a summary dataset, Mix Modeler tries to deduce the corresponding Experience Platform dataset field. When successful:

   • If the field is of type dimension, Map into is selected as Mapping type.
   • If the field is of type metric, Sum is selected as Mapping type.
   • Field is selected as the Default mapping type.
   • The corresponding Experience Platform dataset field is inserted automatically for AEP Dataset Field.

   You can change any of the proposed values if these are incorrect or not supporting your specific use case.

Select Add field to define additional fields.

Select Sync data.

From the Sync data for dataset rules dialog, either select

• Refresh harmonized data for summary datasets,
• Refresh harmonized data for event datasets, or
• Refresh harmonized data for both summary + event datasets.

To start the synchronization based on the defined dataset rules between harmonized data and data in datasets, select Sync. To cancel the synchronization, select Cancel.

Select [beta]{class="badge informative"}.

In the Data merge preferences [beta]{class="badge informative"} dialog:

• Select a Default metric preference. The selected default metric preference is applied when, during harmonization, multiple sources of data update a metric field for a given channel. The preference is applied at the sandbox level, unless overridden for specific metric based preferences. You can select between Summary data, Event data and Sum of summary and event data.

• To add specific metric based preferences:

  1. Select Add a metric.

     1. Select a metric from the Metric selection list.
     2. Select CHANNELS or CONVERSION TYPES. From the list, select All or a specific channel or conversion type.
     3. Select Summary or Event to specify whether summary data or event data is preferred for the metric (and all or selected channel) when merging data.

     To add one or more additional channel or conversion types:

     1. Select Add a channel or Add a conversion type.
     2. Select Summary or Event.

     To delete a channel or conversion type, select .

  2. To add more specific metric based preferences, repeat the previous step.

• To delete an existing specific metric based preference, select .

Select Save to save the data merge preferences. A re-sync of the data is initiated.
Select Cancel to cancel.