Preventing Re Sync of Deleted Records from Marketo

Hi ​@mustufam5967803 ,

This is a known issue we are also facing, as of now we can see two approach :

Approach 1 :
a)Make sure isDeletedFlag is not overwritten by any other source, and add this as a filter criteria in your audience definition that will prevent the fragment from qualifying hence downstream activation is blocked.

b)If Marketo is the driving system (if your campaign execution engine is Marketo) and you want to consider Marketo as the source of truth, we can have a query either in data distiller or in Notebook which you can run and then submit a data hygiene request to remove those fragments (isDeleted=True) out of the system which will ensure it is removed from Datalake, UPS and other AJO native data stores.

Approach 2:

Make use of the consent policy principle of Adobe’s DULE framework where you can define attribute level consent data check and it will be auto applied based on the Marketing action tagged to the destination during downstream activation.

Advantage of this is that you do not need to add the filter inside every audience since it is prone to error.

Details - Manage Data Usage Policies in the UI | Adobe Experience Platform, Consent Policy Rule Building Reference | Adobe Experience Platform.

​​​​​​​However the data hygiene part would be still necessary if you want this data removed from the UPS, even with the consent policy approach it just filters out the profiles from your audiences