Setting Time to Live (TTL) for Customer Profiles | Community
Skip to main content
M
MichaelBailey
Level 2
October 28, 2024
Solved

Setting Time to Live (TTL) for Customer Profiles

  • October 28, 2024
  • 2 replies
  • 1367 views

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!

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by brekrut

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.

 

 

2 replies

Michael_Soprano
Michael_Soprano
Level 10
October 29, 2024

You mean streaming API?

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

Is it event or profile data?

 

M
MichaelBaileyAuthor
Level 2
October 29, 2024

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
Adobe Employee
brekrutAdobe EmployeeAccepted solution
Adobe Employee
October 29, 2024

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.

 

 

A
Adobe Employee
alberto-decaroAdobe Employee
Adobe Employee
March 25, 2025

Hey Michael.
"to set a TTL for Customer Profiles within a specific Namespace"
There are 2 features you can consider:
- Events datasets TTL: this is mostly meant to unload un-necessary historical events from the profile. EG: for a given industry typical returning engament is withing 30 days. Hence it is not necessary to store events older than 30 days in the profile. This helps on the total storage occupation entitlement.
- Pseudonymous profiles data expiration: this is meant to avoid anonymous interactions without return to consume profiles (hence affecting the license usage).

Terms & ConditionsAccessibility statement

Loading footer...