Expand my Community achievements bar.

Join us at Adobe Summit 2024 for the Coffee Break Q&A Live series, a unique opportunity to network with and learn from expert users, the Adobe product team, and Adobe partners in a small group, 30 minute AMA conversations.
SOLVED

Generate FPID using web sdk

Avatar

Level 4

How to generate FPID value using web sdk?

 

Also, is FPID optional as I understand ECID is a must and FPID is a fallback.

 

I am currently reading https://experienceleague.adobe.com/docs/experience-platform/edge/identity/first-party-device-ids.htm... 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@xcode2295 wrote:

How to generate FPID value using web sdk?


Your website has to generate this. See https://experienceleague.adobe.com/docs/experience-platform/edge/identity/first-party-device-ids.htm.... Talk to your developers about creating the FPID in the UUIDv4 format.

 


@xcode2295 wrote:

Also, is FPID optional as I understand ECID is a must and FPID is a fallback.


I think there are 2 main considerations:

  1. If not all of your Adobe tracking is done with Web SDK, e.g. you track AA with Web SDK but you still load Target from at.js, then ECID would still be your primary identifier, so that Adobe can continue to do its visitor stitching across its products properly.
  2. If all of your Adobe tracking is done with Web SDK and you are very confident that you can set a unique UUID for every single visitor to your website, then you can use FPID as your primary identifier and ditch the ECID.

I personally prefer to keep ECID because I'm paranoid about ensuring that every visitor gets identified properly. 

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

@xcode2295 wrote:

How to generate FPID value using web sdk?


Your website has to generate this. See https://experienceleague.adobe.com/docs/experience-platform/edge/identity/first-party-device-ids.htm.... Talk to your developers about creating the FPID in the UUIDv4 format.

 


@xcode2295 wrote:

Also, is FPID optional as I understand ECID is a must and FPID is a fallback.


I think there are 2 main considerations:

  1. If not all of your Adobe tracking is done with Web SDK, e.g. you track AA with Web SDK but you still load Target from at.js, then ECID would still be your primary identifier, so that Adobe can continue to do its visitor stitching across its products properly.
  2. If all of your Adobe tracking is done with Web SDK and you are very confident that you can set a unique UUID for every single visitor to your website, then you can use FPID as your primary identifier and ditch the ECID.

I personally prefer to keep ECID because I'm paranoid about ensuring that every visitor gets identified properly. 

Avatar

Level 4

That is super helpful info as it helps me prioritize the work as we are moving to web sdk this year but, not all of it, so will keep ECID as a primary identifier for now.