Setting Time to Live (TTL) for Customer Profiles

[MichaelBailey]

We are looking to set a TTL for Customer Profiles within a specific Namespace. For example we want all profiles created within our SecondaryCustomerID namespace to be deleted 30 days after creation.

I don't know if this detail is important, but these Customer Profiles are created using a Streaming Experience Event.

Any information is appreciated!

[Michael_Soprano]

You mean streaming API?

Does this namespace will be in different datasets? Are these datasets enabled for profile?

Is it event or profile data?

[MichaelBailey]

Yes Streaming API.

It is currently only a single dataset.

Dataset is enabled for profile.

It is event data. But since the event data contains an ID and triggers the creation of the profile, it also causes the creation of an Identity Map attribute on the profiles. For example the event comes through with primary identity of SecondaryCustomerID = "1234" which creates the attribute on the profile of "identityMap.SecondaryCustomerID.0.id" with value "1234".

Thanks for your reply and hope this answers your questions!

[brekrut · Accepted solution]

TTL is enabled at the dataSet level.  You can enable/set TTL at the dataSet level, but it not applied at a namespace level.  A namespace is applied across multiple schemas.

You may be able apply this logic using Data Distiller to write records which meet this criteria.  

If the data is streaming you may consider using two dataSets with different TTL's to capture the data.