The Edge Network Server API supports visitor identification via First-Party ID (FPID).
All user identities should be supplied in the identityMap
field group. This field group is included in the AEP Web SDK ExperienceEvent
mixin.
{
"identityMap":{
"FPID":[
{
"id":"55613368189701342632255821452918751312",
"authenticatedState":"ambiguous"
}
],
"CRM":[
{
"id":"2394509340-30453470347",
"authenticatedState":"authenticated"
}
]
}
}
There are multiple ways in which a device can be identified within the Edge Network. See the table below for an overview of the supported IDs.
ID namespace | Managed by | Description |
---|---|---|
FPID |
Customer | FPID will be automatically encoded into an ECID by the Edge Network, therefore solutions which require an ECID will work as well. For consistent device identification, these IDs must be persisted on the device and supplied on each request. For web interactions, this involves storing them as browser cookies. |
IDFA /GAID |
Experience Platform | Can identify users across applications, so these IDs are not encoded into ECID by the Edge Network. |