Datasets Time-to-live (TTL) guardrails ttl-guardrail
As of February 2025, a time-to-live (TTL) guardrail is rolled out to Journey Optimizer system-generated datasets in new sandboxes and new organizations as follows:
- 90 days for data in the profile store,
- 13 months for data in the data lake.
This change is being rolled out to existing customer sandboxes in a subsequent phase.
Impacted datasets datasets
The table below lists all impacted datasets and their respective Time-To-Live in the data lake and the profile store.
Frequently Asked Questions faq
You will find below Frequently Asked Questions about datasets Time-to-live (TTL).
Need more details? Use the feedback options at the bottom of this page to raise your question, or connect with .
TTLs extensions are not currently supported. However, work is planned to optimize the TTL process to allow for these extension requests sometime starting the latter-half of 2025.
| note note |
|---|
| NOTE |
| Data stored in the profile is subject to the Total Data Volume entitlement. Therefore, any data storage increase on the profile as a result of a TTL extension would count against the Total Data Volume entitlement. Learn more |
-
Look-up store: No
-
Journey capping: No
-
Offer capping: No
-
Send Time Optimization (STO): No
-
Message frequency capping (i.e., Business rules): No
-
Reporting: No
note note NOTE A TTL is already implemented on the Customer Journey Analytics (CJA) connection, which reduces effective max look-back period of impacted dataset data to 13 months. -
Experience Platform data source: Not applicable - Experience event retrieval is not supported via data sources.
-
Computed attributes: Yes - Initial backfill calculation will be limited to last 90 days of data; computed attribute will be updated based on incremental events for subsequent updates. As soon as the subsequent updates reach the look-back period (max 6 months), the TTL essentially no longer affects the computed attribute. Learn more.
-
Segmentation and retargeting: Yes - Segmentation is dependent on data in the profile store; therefore, look-back is limited to 90 days on affected dataset data.
-
Tracking: Yes - Reduces effective max look-back period of impacted dataset data to 90 days. Data from impacted datasets resides for 13 months in data lake.