Hi @gmadala  I you are completely free to map your custom data to anything in the standard Adobe XDM schema in data prep as calculated fields. But that is the point. Ultimately, may find cases where you will start to create your own XDM schema fieldgroup to make it easier to onboard data from other ...

Hi @Rishank_Tyagi unfortunately, you will have to pick a correct answer since I do not have the rights to select my own answers as correct xD

Hi @Rishank_Tyagi    the frontend works the same way. Adobe places one or more cookies with user identifiers which get sent automatically with any outgoing tracking call. This user identifier is linked to all additional information like eVars you are sending with the tracking request. And this happe...

Hi @Rishank_Tyagi  eVars values are persisted on the Adobe servers, you will not find them on the client. You send them in a tracking call and Adobe takes care of the rest for you.   What exactly do you mean with backend scenario?

Frankly, I have always used the server-side approach. Maybe reach out to support on this

Hi @kamil_tagging  at this point it is hard to say what causes your issues. In general, I have not had bad experiences with it   Can you give more context on (maybe screenshots would help) do you use consent? which platform? do you send a tracking call once consent is given (on the same page)? do yo...

Hi @skatofiabah    Yes, your assumption is correct. If it is on Visitor level, it looks at any Visit where Page A was seen after the first Page A page view has happened. This can be during the same Visit or any of the following ones, as long as the Visitor can be identified.   I would suggest you pl...

Yeah the usual. Thx for the feedback 

By any chance, you also don't know whether this one is deduplicated or now? My assumption would be not

Thx  @leocwlau for confirming  Is there anyone you know I could ask for a documentation update? Quite annoying when something that important isn't explained neither in Workspace nor mentioned in the documentation