AEP + Adobe Target Next-Page Personalization with TTL Persistence

Question

I am looking for guidance on a personalization use case involving AEP Edge Audiences and Adobe Target, specifically around extending personalization beyond the current session and supporting a TTL-based return visit scenario.

Current Architecture

* Adobe Web SDK
* Adobe Experience Platform (AEP)
* Adobe Target
* Edge Segmentation enabled in the Datastream
* ECID as the identity
* Same domain journey

User Journey

1. User lands on Homepage (`abc.com`).
2. Homepage contains a "Get Started" banner/blade.
3. User clicks the banner and navigates to a quiz page (`abc.com/quizpage.html`).
4. User completes the quiz.
5. Upon quiz completion, a custom event is sent via Web SDK.
6. AEP audience qualifies based on quiz completion attributes.
7. Business requirement is to hide the "Get Started" banner on the homepage for quiz-completed users.

What We Successfully Achieved

POC – Same Page Personalization

We created an AEP audience using quiz completion attributes that only become available when the quiz completion event fires.

Audience Evaluation Method: Edge
When the user completed the quiz, personalization was successfully rendered on the same page using Adobe Target.

Production Scenario – Next Page Personalization (Same Session)

We then used the same Edge audience in Adobe Target.

Flow:

1. User completes quiz.
2. AEP Edge audience qualifies immediately.
3. User navigates back to homepage.
4. Homepage Target request recognizes the audience.
5. Banner is successfully hidden.

This is currently working within the same browser session.

New Business Requirement

We now need the personalization to persist across sessions.

Example

* User completes the quiz today.
* Audience qualifies successfully.
* User closes browser.
* User returns after several days (up to 14 days).
* Same browser.
* Same ECID.
* Homepage should continue hiding the banner.

Current TTL expectation is:

14 days after quiz completion.

Attempted Approach

To support both:

* Immediate Edge qualification (same session)
* Persistent qualification (14-day return visits)

We created:

Audience 1

`Abc_Quiz_completed`

* Edge evaluation
* Event-based audience
* Used for immediate personalization

Audience 2

Abc_Quiz_completed_Batch`

* Batch/Streaming audience
* Intended for persistence across sessions

We then attempted to create a combined audience:

Abc_Quiz_completed
AND/OR
Abc_Quiz_completed_Batch

However, AEP returns the following error:

Failed to save

Please include only segments that have the same mergePolicyId as their dependencies.
(NEBULA - 100030-400)
```

From our understanding, this is because the source audiences were created with different merge policies/evaluation methods.

Questions

1. Is the overall approach correct?

Can AEP be used to support both:

* Same-session personalization (Edge)
* Cross-session personalization (14-day TTL)

using the same audience strategy?

2. What is the recommended design pattern?

Should we:

* Create a single audience?
* Use Edge + Profile attributes?
* Use Edge audiences combined with profile-based qualification?
* Use audience composition differently?

3. Is it possible to persist an Edge audience qualification for 14 days without introducing a new schema field?

Currently, schema changes are not preferred.

4. How do customers typically solve this?

Use case seems common:

text
User completes a quiz
→ Hide CTA/banner
→ Continue hiding CTA/banner for X days
→ Same ECID/browser
→ Adobe Target personalization

Would you recommend:

* AEP Edge audiences only?
* Streaming audiences?
* Profile attributes?
* Audience composition?
* Adobe Target profile attributes?

5. If the audience is Edge-based and working in-session, what is the Adobe-recommended method to make that audience available for future visits (up to 14 days) while still keeping the same homepage personalization experience?

Any architecture recommendations, implementation examples, or Experience League documentation references would be greatly appreciated.

Thank you!

DineshK · Answer

Hi ​@Sankaran,Q1 — Can AEP support both same-session and cross-session personalization using the same audience strategy?Not with a single audience, no. Edge audiences handle same-session perfectly but stop qualifying once the event ages past 24 hours. You need two different mechanisms — one for immediate qualification, one for persistence. AEP covers the first part, Target covers the second.Q2 — What's the recommended design pattern?Edge audience for same-session + Target profile attributes for cross-session. Not audience composition, not a combined AEP segment. The two-audience approach lives inside your Target activity, not inside AEP — you run your AEP edge audience and a Target profile audience side by side with OR logic. Whichever one matches the visitor, the experience fires.Q3 — Can you persist an edge qualification for 14 days without schema changes?No. Edge segments evaluate against events within a sub-24-hour window — there's no TTL configuration you can set to stretch that to 14 days at the AEP segment level.Target profile attributes are stored in Target's own visitor profile storage, completely separate from AEP XDM. You write a completion flag there when the quiz fires, and a profile script handles the 14-day window check on every homepage visit.Q4 — How do customers typically solve this?Adobe Target profile attributes, consistently. The AEP edge audience handles the in-session leg, Target profile attributes handle the persistence leg. Streaming audiences alone won't give you a controllable TTL. Audience composition doesn't solve the cross-session problem. Every "complete action → suppress for X days" use case I've seen in production lands on this same split.Q5 — Adobe-recommended method to make an edge-qualified audience available for future visits?At the moment the quiz completes, write a persistent flag into the Target visitor profile alongside the AEP event. From that point forward, every homepage visit checks the profile attribute — not the AEP audience. The edge audience is still there for the same-session leg, but the return visit scenario is owned entirely by Target's profile storage. Since that storage is tied to the ECID and lives server-side, it survives browser closes, session expiry, and anything else that would break cookie-based persistence.No schema changes required. Works within your current Web SDK setup.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded