Regarding first-party device IDs (FPID's) implementation, how can AEP Web SDK (which is a client side Javascript library) get the value of the cookie FPID even if FPID is flagged with HttpOnly? | Community
Skip to main content
July 3, 2024
Solved

Regarding first-party device IDs (FPID's) implementation, how can AEP Web SDK (which is a client side Javascript library) get the value of the cookie FPID even if FPID is flagged with HttpOnly?

  • July 3, 2024
  • 1 reply
  • 764 views

Hello, Hope you are all doing well!

 

I have a simple doubt:

 

Regarding first-party device IDs (FPID's) implementation, how is AEP Web SDK (being, as per the docs, a client side Javascript library) able to get the value of the cookie FPID to send to Edge network, even if the FPID is flagged with HttpOnly by the server? Wouldn't the browser block Web SDK, as a javascript library, to get FPID cookie?

 

Thank you very much!

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 Anil_Umachigi

@viniciuscosta1 Have you tried doing this in an env? 

the configuration of FPID happens in datastream, this data is read on the edge server once enabled. 

if you do not want to go this way, you can read the cookie server side and update datalayer on client side before it's passed into identityMap 

 

read here 

https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/first-party-device-ids#http-only

 

 

 

 

1 reply

Anil_Umachigi
Adobe Employee
Anil_UmachigiAdobe EmployeeAccepted solution
Adobe Employee
July 4, 2024

@viniciuscosta1 Have you tried doing this in an env? 

the configuration of FPID happens in datastream, this data is read on the edge server once enabled. 

if you do not want to go this way, you can read the cookie server side and update datalayer on client side before it's passed into identityMap 

 

read here 

https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/first-party-device-ids#http-only