Set segment qualification to expire after a short amount of time

[floriana_guardi]

I'm building a segment in Audience Manager. I would like to use existing traits, without recreating new ones with a shorter expiration time.

How can I set a segment qualification rule so that it expires?

My segment currently looks like this:

(trait 1 OR trait 2) AND NOT (trait 3 OR trait 4)

Trait 1 and 2 are qualification traits, like page URL contains xyz and user profile is abc. Trait 3 and 4 are exclusion traits, like form submission OR pop-up view. Qualifying for these conditions triggers a pop-up in the next pageview. Pop-up view is trait 4, so once a visitor sees the pop-up, they are out of the segment. Except for the pop-up one, the traits are all standard with a 120 days lifespan.

My stakeholder would like the trigger of the pop-up to always happen at least on the second page view, never on the first. So, assuming a visitor qualifies for trait 1 OR 2 and ends the session, how do I adjust the segment so that they have to qualify again for it in the next visit?

[AnkitJasani29]

Hi @floriana_guardi ,

To meet your goal in AAM - ensuring the pop-up is shown only on the second page view and not the first, without creating new traits - you’ll need to adjust the segment logic to include some sort of time-based behavior or use recency/frequency constraints at the segment level.

(trait 1 OR trait 2) AND NOT (trait 3 OR trait 4)

Trigger the pop-up only on the second page view, not on the first.

Avoid creating new traits (especially duplicates with shorter lifespans).

Use existing traits and AAM features to expire the segment qualification between sessions or enforce "re-qualification".

Use Recency/Frequency (R/F) Controls in the Segment

Set recency and frequency at the segment level, which can be used to ensure a user needs to match the trait multiple times (i.e., across sessions or pageviews).

(trait 1 OR trait 2) with frequency >= 2 AND NOT (trait 3 OR trait 4)

• Frequency >= 2 ensures that the user must have matched one of the qualifying traits (1 or 2) twice - i.e., over at least two pageviews.
• This prevents pop-up display on first pageview, because the user hasn't met the segment criteria yet.
• On second pageview, they would re-qualify and meet the frequency condition.

Optional: Use Time-Based Suppression (If Needed)
If you're still worried about long-living segment memberships (e.g., from trait 1 or 2's 120-day expiration), you could:

Add a recency limit, e.g., "recency = 1" to limit how recently the trait was realized.

But this is often less reliable than frequency in your use case, unless you have session traits.

Alternative (If You Have a Session-End Trait):
If you have a “session end” or “session start” trait, or you can create one (e.g., using DTM/Launch logic), you could also structure the segment like this:

Session start AND (trait 1 OR trait 2) AND NOT (trait 3 OR trait 4)

Then ensure that trait 1 or 2 happened in a previous session, and not the current one - although this gets more complex without explicit session traits.

Best Solution:
Update your segment logic to:

(trait 1 OR trait 2) with frequency >= 2 AND NOT (trait 3 OR trait 4)

This meets your requirement without recreating traits and ensures the pop-up triggers only on the second pageview or later.