Type at least 2 characters.

AI generatedAI generated This record is generated by AI from the cited source. How AI is used

JO

Dataset TTL guardrail enforcement on existing sandboxes

GA since 1 Oct 2026 under review

Journey Optimizer enforces the dataset TTL guardrail (90 days in the profile store, 13 months in the data lake) on existing sandboxes and organizations from October 1, 2026.

Read vendor source (opens in a new tab)
experienceleague.adobe.com Evidence for GA · 1 Oct 2026 Additional source: experienceleague.adobe.com ↗ (opens in a new tab)
Platform
Adobe Journey Optimizer
Capability
Data retention & lifecycle · Governance
Vendor's name
Dataset Time-to-live (TTL) guardrail
First recorded
Record last updated

Record dates describe acquisition and updates, not human review. About corrections.

Lifecycle history 1 state

  1. GA1 Oct 2026
    First recorded 27 Sep 2026 · recorded from the source history · vendor release notes (2 sources) · experienceleague.adobe.com ↗ · archived copy, 26 Sep 2026 ↗ · experienceleague.adobe.com ↗ · archived copy, 26 Sep 2026 ↗

Record corrections 6

Changes made to this record after it was published, separate from the vendor's lifecycle states above. All corrections.

  1. Classification

    Significance: major → minor

    A retention limit extended to existing sandboxes, not a new capability or a removal. Evidence: experienceleague.adobe.com ↗

  2. Text
    Summary rewritten

    Before: Existing sandboxes/orgs will start enforcing the dataset TTL guardrail (90 days profile store, 13 months data lake) from October 1, 2026.

    After: Journey Optimizer enforces the dataset TTL guardrail (90 days in the profile store, 13 months in the data lake) on existing sandboxes and organizations from October 1, 2026.

    Summary in the present tense for a change in effect since October 1, 2026. Evidence: experienceleague.adobe.com ↗

  3. Lifecycle state

    Lifecycle state: Deprecation announced · Jul 2026 → GA · 1 Oct 2026

    Not the removal of a feature: the TTL guardrail "will be enforced on existing customer sandboxes and organizations starting October 1, 2026". Recorded as a change in effect from that date (owner decision). Evidence: experienceleague.adobe.com ↗

  4. Date

    Deprecation announced date: 1 Sep 2026 → 1 Jul 2026

    The TTL guardrail bullet is already in the July '26 > Administration section of the 2026 archive (no date of its own); September repeats it under "The following reminder applies". Evidence: experienceleague.adobe.com ↗

  5. Date precision

    Deprecation announced date precision: exact day → month

    Rule: never two states of a feature on the same day; a promised availability date is kept as the promise, not as the state date. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

  6. Date

    Deprecation announced date: 1 Oct 2026 → 1 Sep 2026

    Rule: never two states of a feature on the same day; a promised availability date is kept as the promise, not as the state date. Evidence: experienceleague.adobe.com ↗ · Reconstructed from the record's revision history.

Something wrong or out of date in this record? , ideally with a link to better evidence. How corrections work

Data retention & lifecycle on other platforms latest first

All Data retention & lifecycle changes →

More from Adobe AJO in Data retention & lifecycle

Report an issue

Tell us what is wrong in this record. Reports are checked against public sources, with the same rules as every entry. How corrections work

Sent through Web3Forms. Nothing you send is published. How reports are handled.