FPID and Demdex ID in AEP Web SDK

[Harveer_SinghGi1]

Hi Team,

Adobe product documentation mentions that if we are using FPID in our implementation than we cannot use Use third-party cookies option in Web SDK configuration,

This means I can use either FPID or Demdex ID to seed ECID.

I want to understand what happens if we have both of these options enabled?

• Does to FPID take precedence over Demdex ID or vice-a-versa?
• Does it break the visitor identification process? What happens then? How does user get ECID?
• Does it work like if FPID is available use it otherwise use Demdex ID or vice-a-versa?

Thanks

[bjoern__koth · Accepted solution]

Hi @Harveer_SinghGi1 

the FPID will take precendence over the classic cookies. Should your FPID service not have persisted a value, the typical cookies will be used until their lifetime expires.

After that, the FPID cookie will be used.

So, I don't think this would break anything.

[RiteshY18]

@Harveer_SinghGi1 suggest using FPID , as it is severe based have longer days of persistence over others and is first-party domain

also, third-party cookies support is going away soon , third-party cookies can break the experience if third-party cookies are disabled at client's browser for which u have no control.

[RiteshY18]

@bjoern__koth   it will break the experience that is why we have an FPID approach