That's what I was afraid but thank you, Yuhuisg!

Thank you leocwlau and yes, unfortunately, FPID with uuid v4 is not good enough. But v5 is 

Thank you Yuhuisg!

Team, What is the equivalent of s.visitorID with the AEP Web SDK?I'm trying to find a solution where Adobe Analytics would use that custom visitor ID (such as CRM ID or Loyalty ID) to override the ECID so I can get an exact count of visitors that will not be cookie-based.This Adobe doc seems to say ...

Thank you all!

In the AEP > Customer > Identity UI, it is not possible to change the type of an existing Identity (let's say from "Cross-device ID" to "Non-people identifier", as an example).But can it be done with the identity API?

This means that for now, we need to explicitly send page and profile parameters if we want the ML algo to evaluate them, am I understand it correctly, Alex? alloy("sendEvent", { renderDecisions: true, data: { __adobe: { target: { "profile.gender": "female", "profile.age...

Hi team,   When you use the AEP Web SDK to collect data and get it forwarded to both Adobe Analytics and Adobe Target, does the ML (Auto-Target) algorithm automatically evaluate the XDM fields/values we're sending to the Edge or do we have to explicitly pass (someof ) them as page or profile paramet...

Actually, I think I found the answer for use case 2b: Remove IP addressThe Adobe documentation says: Checking Remove IP address replaces the IP address with x.x.x.x in the data, after geo-lookup.So I guess the geo-segmentation reports will still work.I now believe that use case 2a will obfuscate the...

Hi,I understand that when it comes to collecting and reporting the IP address, we have several options. What I am not clear on is how it impacts the geo-lookup (geo-segmentation reports).1. IP - Replace the last octetI understand what it does to the IP Address report and how it impacts the geo segme...