profile snapshot table details

[itsMeTechy]

if we have more than one merge policy, then there will be more than one profile snapshot table for individual profile. how can we differentiate which snapshot table is for which merge policy. any idea? please help.

[AnkitJasani29 · Accepted solution]

Hi @itsMeTechy ,

Yes, when multiple merge policies are defined in AEP, each profile snapshot table is created per merge policy, because each merge policy produces a different view of the unified profile. To differentiate which profile snapshot table corresponds to which merge policy, you can follow this process:

1) Use merge policy id in dataset name

When you generate a snapshot via AEP, it creates a dataset with a name containing the mergePolicyId or a reference to it.

Example: profile_snapshot_<mergePolicyId>_<timestamp>

2) Use dataset metadata via catalog api

Reference:

https://experienceleague.adobe.com/en/docs/experience-platform/profile/merge-policies/merge-policies

https://experienceleague.adobe.com/en/docs/experience-platform/catalog/api/list-objects

Thanks

Ankit

[itsMeTechy]

Thanks for the information.

Merge policy id (in UI) is not the same compared with a alpha numeric characters appended in dataset name of profile snapshot table. Not sure if there will be different id when we retrieve the merge policy using API.

[AnkitJasani29]

Hi @itsMeTechy ,

In the UI, merge policies have a user-friendly ID (human-readable name).

But in the profile snapshot dataset name, you’ll often see a suffix like numbers and dash included into it (real internal identifier).

Real internal identifier gets used when a snapshot is generated.

You can list all merge policies via api Reference: https://experienceleague.adobe.com/en/docs/experience-platform/profile/merge-policies/merge-policies

From there you can confirm id = real internal identifier & name = human-readable name

Also, do accept the solution if earlier or current answer worked for you so that anyone else also facing something similar can directly go to the right response.

Thanks

Ankit