What is the importance of the profile_export_for_destination_merge_policy__XXX dataset in AEP ?

[Indra]

What is the importance of the profile_export_for_destination_merge_policy__XXX dataset in AEP?  How different is it from Profile_Snapshot__XX?

[DavidRoss91]

Hi @Indra 

My understanding of the 2 datasets is as follows:

Profile Export for Destination Merge Policy would be useful for the data export based on specific merge policies. I.e. Timestamp vs Dataset Precedence

Profile Snapshot is useful for any type of historical analysis you may need, or auditing any changes of a profile over time

[PratheepArunRaj]

Dear @Indra,

Profile Export for Merge Policy will help you to export the profile data based on the merge policy. Suppose you have two datasets (CRM and Web), which are ingesting first names into your Profile Store, then the time-based merge policy will have the most recent update irrespective of the datasets. On the other hand, if you select the dataset precedence (say, CRM), and even if the Web dataset is injecting the first name at the most recent, it won't be taken into account. So, irrespective of the merge policies, the profile data can have only 1 first name when you export.

On the other hand, Profile Snapshot will take a copy of your Profile Store every day so that we can understand when and how the profile attributes are changed. So, the profile snapshot dataset can have more than 1 first name because the first name can be different at a specific point in time irrespective of the datasets.

Assume the below first names are injected into the AEP Profile Store at different point in time:

Day 1 (Web): ARUN

Day 2 (CRM): PRATHEEP

Day 3 (Web): RAJ

Profile Export (Time Based) will have only one value, which is RAJ, the recent.

Profile Export (Data Precedence, say CRM), will have only one value, which is PRATHEEP, CRM precedence.

Profile Snapshot will have 3 values: ARUN, PRATHEEP and RAJ based on the specific point in time the snapshot was taken. So, this will help us to understand when and how the attribute was changed.

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

[Indra]

Thanks David & Pratheep for the response

If we have default merge policy, Both datasets all attributes values data should match Right ?  

[brekrut]

Hello @Indra 

The profile_export_for_destination_merge_policy is updated on periodic basis as profile attributes are updated.

The Profile_Snapshot is updated 1 x / day after the segmentation evaluation job completes.

[Indra]

Thanks for the response @brekrut

We currently update profile data through a daily ingestion job, which runs only once a day. However, we’ve noticed that batches for the profile export for destination -Merge Policy -xxx dataset are being ingested approximately every 10 minutes.

I’m trying to better understand:

The source of data for this dataset.

The reason for such frequent batch ingestion, even though the job is scheduled to update once daily.

Has anyone encountered a similar scenario, or could provide insights into the potential cause or configuration settings that might explain this behavior? Your help would be greatly appreciated!

[brekrut]

The source of the profile_export_for_destination_merge_policy__XXX is all record based datasets which have been marked for profile.

[kautuk_sahni]

@Indra Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!