I need to configure that some Identity Namespaces be unique in Identity Service:IdentityA - entity 1 IdentityB - entity 2 IdentityC - entity 3 Additionally I need to configure the priorities. That is in the description of the priorities:Segmentation service: For each merged profile, segment memberships are recorded under the identity with the highest namespace priority.Lets assume that some customer has both IdenityA and IdentityB. However IdentityA has a higher priority. I configure the audience and different people fall into that audience (some has IdentityA, some has IdentityB and some has both). However when I create batch journey I need to choose the namespace.Does the people which fall into the audience which has IdentityB fall into that journey if they do not have IdentityA and IdentityA is the core namespace for that journey?

Michael_Soprano

Level 10

Question

Identity Namespace & Batch Journey

Forum|Forum|21 days ago
July 20, 2026
3 replies
38 views

I need to configure that some Identity Namespaces be unique in Identity Service:

IdentityA - entity 1
IdentityB - entity 2
IdentityC - entity 3

Additionally I need to configure the priorities. That is in the description of the priorities:

Segmentation service: For each merged profile, segment memberships are recorded under the identity with the highest namespace priority.

Lets assume that some customer has both IdenityA and IdentityB. However IdentityA has a higher priority.

I configure the audience and different people fall into that audience (some has IdentityA, some has IdentityB and some has both).

However when I create batch journey I need to choose the namespace.

Does the people which fall into the audience which has IdentityB fall into that journey if they do not have IdentityA and IdentityA is the core namespace for that journey?

DavidKangni

Community Advisor

@Michael_Soprano

the profiles will be discarded because they had a missing identity for the required namespace.

David Kangni

K

kalarav.vasavada

Level 2

No. If you select IdentityA as the journey's namespace, only profiles that actually have an IdentityA value will enter the journey. Profiles qualifying via IdentityB but with no IdentityA are filtered out at journey entry. As Namespace priority only decides which identity a segment membership is stamped under on the merged profile, No IdentityA value = no addressable identity = profile is skipped. These skipped profiles typically appear as "excluded / no identity" in the journey report.

Please share if you would like to include them, so will share steps and solution for that.

A

ashexplorer

Level 1

Yes, that’s right - the profiles which had IdentityB will be discarded and only the ones having the selected identity namespace IdentityA in this case will be included.

Sign up

Login with SSO

Login to the community

Login with SSO