Allow for segment/audience creation based on visit count

Hey,

totally understand the frustration here — this is a genuine gap in RTCDP today and you're not alone in hitting it.

The root cause is that when Analytics data flows into AEP via the Source Connector, the visit boundary gets lost. AEP sees individual hits, not sessions. So there's nothing to count as a "visit" out of the box.

Two approaches that actually work well together for this:

 

Option 1 — Pass Session ID through Web SDK

If you control your tracking implementation, generate a session ID in the browser and pass it with every hit via Web SDK:

alloy("sendEvent", {
  xdm: {
    _yourorg: {
      sessionId: "your-session-id-here"
    }
  }
});

Once that field is landing on your Experience Events in AEP, you can use Computed Attributes to count distinct session IDs per user in a rolling time window — that gives you true visit count on the profile. You can then segment on it directly in the audience builder.

Once the computed attribute is on the profile you can build multiple audiences using different thresholds — users with 1-3 visits, 4-10 visits, 10+ visits — all from the same single computed attribute. No need to create separate logic for each interval.

You'll need a small schema change to add the session ID field to your XDM schema, and a data element in Launch to generate or capture the session ID. But once it's in place it's clean and real time.

 

Option 2 — CJA Audiences pushed to RTCDP

If you're on CJA this is honestly the most straightforward path. CJA understands sessions natively the same way Analytics does, so you can build your visit count logic there exactly how you'd expect — visits in last 30 days between 3 and 10, or whatever intervals make sense for your KPIs.

Once the audience is defined in CJA, publish it directly back to AEP and activate from RTCDP. Clean, accurate, no workarounds needed.