@Kirill812 As per my understanding “overrideMboxEdgeServer” configuration is used to avoid "edge cases" (where a visitor would move from 1 edge to another). If the visitor switches from one edge node to another, then that would mess up with their targeting qualifications because their profiles are not synched across different servers(They would get different experiences just by refreshing the page ). Hence to avoid this "overrideMboxEdgeServer" the default value is set to "True" so a visitor wou...

Hi @Maple-Michelle1 they are referring to the marketingCloudVisitorId that is sent in the request payload to Target--ensure that matches the "mid" query string parameter in the server call to Analytics. I had an experience a while back with a similar issue (reporting mismatch). After much digging around I found it was in fact due to an intermittent sdid problem. In our implementation, we originally used the default at.js behavior which has viewsEnabled set to true. This effectively generates 2 m...

Hi @umamaheswariy46! @vishalchordia was able to weigh in on your Question here during his 9/8/21 Adobe Target Community Q&A Coffee Break! His answer below: Uma - I'm going to answer the questions in regards to AEP. Adobe Experience Profile (AEP) provides an user interface to view a specific User profiles with all the attributes and Segments the user is part. With AEP becoming the center point for all audience related acitivies, you could use the AEP to view the user's profile Thank you 🙂 Vishal...