I wonder why in Step 5 on First-party device IDs in the Platform Web SDK | Adobe Experience Platform uses FPID as primary identifier, given order of priority will only enabled ECID during new cookie identification of user. ie. Step 5 : should only have ECID = 678 instead of FPID = 012 being used as identifier.
Solved! Go to Solution.
@navink386520 Not really, since this is a migration usecase the initial visit will have an ECID set already (appmeasurement library) before webSDK is introduced and used until that cookie is deleted and the next session onwards FPID takes over.
In the 5th visit the user deletes all cookies ( let's say manually) including FPID ( let's say set for 2 years expiration), this will initiate the sequence of web server sets FPID, the webSDK on client reads the FPID set's a new ECID.
Since FPID was present and will be used to create the ECID, it is the identifier.
Hope that helps
@navink386520 Not really, since this is a migration usecase the initial visit will have an ECID set already (appmeasurement library) before webSDK is introduced and used until that cookie is deleted and the next session onwards FPID takes over.
In the 5th visit the user deletes all cookies ( let's say manually) including FPID ( let's say set for 2 years expiration), this will initiate the sequence of web server sets FPID, the webSDK on client reads the FPID set's a new ECID.
Since FPID was present and will be used to create the ECID, it is the identifier.
Hope that helps
Views
Likes
Replies