ECID is the main user identification ID of Adobe Analytics. When deploying Adobe Analytics, it is usually set to eVar.
Adobe Analytics has Client-side deployment and Server-side deployment, different deployment methods have different ways of setting ECID to eVars.
Client-side Tracking：Dynamic Variable
Let’s first look at client-side deployment, how to set ECID as eVar.
Wrong Configuration
Some people directly use the Experience Cloud ID Service’s built-in data element ECID, setting it as an eVar:
This data element does obtain the ECID, but may appear Unspecified in the report:
Unspecified means that the variable is undefined or unavailable, and the value is not obtained here.
If you use the built-in data element ECID of Experience Cloud ID Service to set the ECID, Unspecified may appear.
Correct Configuration
The correct way is to use dynamic variables. The data sent by Adobe Analytics has ECID by default:
mid is actually ECID, We can set mid to eVar through dynamic variables:
In this way, eVar will not appear as Unspecified:
Server-side Tracking：Processing Rules
If you are deploying on the Server-side, although the official method provides the getIdentity method to obtain the ECID, it may happen that for new users, the ECID has not been returned, but the Web SDK has already sent the data, resulting in Unspecified.
The correct way is to use processing rules. If it is deployed on the server side, a.x.identitymap.ecid.0.id is the ECID. Set as follows:
