How to choose between Cross Device Identity or Non People Identity? | Adobe Higher Education
Skip to main content
Luca_Lattarini
Level 9
September 18, 2022
Respondido

How to choose between Cross Device Identity or Non People Identity?

  • September 18, 2022
  • 1 resposta
  • 1850 Visualizações

Hi All,

 

Assuming that we have a web site for telco industry where every subscription has its own account ID. This account ID is obtanied by merging N user account ID. For example user account id1 +user account  id2 = account ID.

Assuming that we want to target with offer at user level (1:1) and on the same time tracking at account ID level 

 Anyone can recommend if account ID  should be Non People Identity or Cross Device Identity and set up as secondary identity with user account ID as primary identity? Or Any other possibe approach?

For your information we have a User Account schema with Primary ID = user account id 

Thanks

Luca

 

 

 

 

 

 

Este tópico foi fechado para respostas.
Melhor resposta por ChetanyaJain-1

@luca_lattarini Non-people IDs are used for storing identifiers that require namespaces but are not connected to a person cluster. For example, a product SKU, data related to products, organizations, or stores.

1 Resposta

ChetanyaJain-1
Community Advisor
Community Advisor
September 18, 2022

@luca_lattarini 

accountId should be cross-device id - do not set that as non-people id.

Use non-people id if you need to use it for lookup table like Product (productId).

 

As far as I know, non-people id will not be used for stitching.

 

Regards,

Chetanya

ChetanyaJain-1
Community Advisor
Community Advisor
September 20, 2022

@luca_lattarini Non-people IDs are used for storing identifiers that require namespaces but are not connected to a person cluster. For example, a product SKU, data related to products, organizations, or stores.

Luca_Lattarini
Level 9
September 20, 2022

@chetanyajain-1  first of all, thanks for yoru help. To implement my scenario I am thinking to create account id = (user account id1 +user account  id2) as cross device identity as primary identity and user account id as secondary . Or viceversa?

Thanks