hi, I am hoping someone would be able to assist with in this situation.
We have an implementation where we integrated Adobe Target with Adobe AEM. That way the end user can do personalisation / targeting from either of UIs.
However as an result we end up having multiple mboxes firing for each experience on the page. I will illustrate:
if anyone could provide clarity on that topic., that would be much appreciated
Jason Hickey, could you please have a look at this situation with multiple subsequent mbox calls?
This has a negative impact on the UX as the targeted content block disappears and appears multiple times (every mbox call hides and then shows the content).
We would highly appreciate if you could share your advice.
As far as my understanding when experience s are created in the AEM UI it is usual and has no consequences as far as they have different loading time,event call back and different workflow process.
We are facing the same problem. marina.bear: Did you figure out a solution yet? Having 2 calls is not problematic, but for each mbox call, we are triggering an analytics event to capture some extra data with the mbox call loading. This is causing to many analytics calls being fired.