Profile snapshot dataset

Hey ​@Michael_Soprano
 

Yes, one snapshot dataset gets created per merge policy. So if you have 3 merge policies in your sandbox, you'll see 3 of these datasets in your inventory — each named after the merge policy ID.

The reason is simple: different merge policies can produce a different version of the same profile (different attribute precedence, different identity stitching), so each needs its own snapshot.

A couple of practical things to keep in mind:

• Batch segments run against these snapshots, not the live profile store — so segment results are only as fresh as the last snapshot job, which typically runs every 24 hours
• If you delete a merge policy, the dataset doesn't always get cleaned up automatically, so worth doing a manual check periodically
• You can query them in Query Service if you ever need to inspect what's in there

SELECT * FROM "Profile Snapshot Export - <merge_policy_id>" LIMIT 10

​@Michael_Soprano yes that is right each merge policy creates a separate Profile snapshot dataset most likely applying the rules set in the merge policy.