Generate FPID using web sdk | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by yuhuisg
@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.html?lang=en#setting-a-cookie-using-your-own-server. 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. 😂

1 reply

yuhuisg
Community Advisor
yuhuisgCommunity AdvisorAccepted solution
Community Advisor
March 14, 2023
@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.html?lang=en#setting-a-cookie-using-your-own-server. 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. 😂

X
xcode2295Author
March 14, 2023

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.

Terms & ConditionsAccessibility statement

Loading footer...