merge policy: timestamp / dataset precedence

[Michael_Soprano]

I would like to understand merge policy. 

Assuming that I have multiple profile datasets with consent field group.

Let assume that I ask about email consent. 

I have two datasets: www source and app source

For timestamp precedence if I the user in one dataset will have no consent and in other consent then the newer one (timestamp) will be in the profile?

For dataset precedence. User will have in www dataset consent and in app dataset no consent. App dataset is set higher in order than www. Then on the user profile would bo no consent?

[DavidRoss91 · Accepted solution]

@Michael_Soprano 

Yes, this is correct. Timestamp is based on the most recent ingested record via timestamp. Whereas Dataset Precedence allows you to set which dataset you trust over the other, when it comes to the same data attributes that may live in multiple datasets.

Hope this helps.

David

[Michael_Soprano]

Thanks!

Assuming:

1. In the dataset which is number 1 in hierarchy consent for email is empty. 

2. In the dataset which is number 2 in hierarchy there is consent. 

So in profile there would be a consent or consent for email would be empty?