AFAIK Adobe does not obfuscate data, so this sounds rather like the data was coming in obfuscated from your website's data layer.   As for the unspecified values in a logged in site section, this also sounds like the value is not present in all requests. If you are using an ever, you could consider ...

Hi @KatiaAr  maybe Adobe had a release window that affected the functionality. If something like this happens, you can always check https://status.adobe.com   As the error indicates, this may have been a temporary issue. Can you try again?

Different to audiences, where API-created PQL audiences can only be edited through the API and not via the UI, I think all schemas should be compatible to be extended through the API and UI. API comes with complexity and the typical learning curve

Yes, especially for low traffic websites with low conversion numbers, this may mean you have to run the same activity for a long time to reach statistic significance. In general, these seem to be the thresholds you find online. Up to you to choose reaching which one makes sense.   < 75%: Not signifi...

Hi @kani456  Even though this is more of a Target question, let me try to break it down for you.   In Adobe Target, the confidence level indicates how certain you can be that the difference in performance between your experiences is real and not just due to random chance. Simply speaking, it answers...

Think of it like a database. The primary identity is the Primary Key of your database row. The supporting identities are similar to Foreign Keys that help join to other rows.   Primary identities are the "main" identifier when the record is stored. They serve as main profile stitching anchor.   Seco...

Hi @MichaelJo29,  do you see this issue appearing on all every empty string or only on some attributes? Is your string attribute maybe set as required? Even though the recommended size is 1, a length of 0 should still be possible, but I am a little unsure whether a 0-string is considered not set and...

Hi @TapaswiniPa1  that is exactly the point. opening in a new tab does not abort the requests since it is not a navigation for the browser, taking the user away from the current website. For the browser it is a new window, and all requests that are supposed to be fired on the previous website go thr...

Yes, that is the typical error message you see in Omnibug.   Your aborted request is for the Facebook pixel though. I checked the documentation and could not find any hints that it supports PINGs as well. The described approach above is merely for AppMeasurement and WebSDK.