Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Duplicate mboxes: consequences

Avatar

Avatar
Validate 1
Level 3
marina_bear
Level 3

Likes

22 likes

Total Posts

32 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 3
marina_bear
Level 3

Likes

22 likes

Total Posts

32 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
marina_bear
Level 3

18-07-2018

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:

  • at.js injected via DTM adds a global mbox to the page
  • when experiences are created within AEM UI using Targeting mode, each of the targeted components (or building blocks of the page) become "offer locations" and they then start to fire 2 duplicate local mboxes.
  • the mbox duplication takes place once per component. What it means is that no matter how many experiences (modifications of the same component) we create, it will still send 2 local mbox calls on page load
  • if there are multiple targeted components on a page, each will fire 2 local mboxes. Example: if we target 5 components, the page will send 1 global + 5x2 local = 11 total mboxes on page load

Question:

  • is it normal or abnormal behaviour to have duplication of local mboxes
  • what are the risks of having duplicate mboxes on the same location: functional, technical if any? (eg experience serving etc)
  • does it impact data collection (custom params, profiel scriots)
  • does it impact goals/metrics in reporting
  • does it impact billable target calls (page loads)
  • any other considerations

if anyone could provide clarity on that topic., that would be much appreciated

Replies

Avatar

Avatar
Coach
MVP
Andrey_Osadchuk
MVP

Likes

509 likes

Total Posts

917 posts

Correct Reply

243 solutions
Top badges earned
Coach
Contributor
Seeker
Bedrock
Boost 500
View profile

Avatar
Coach
MVP
Andrey_Osadchuk
MVP

Likes

509 likes

Total Posts

917 posts

Correct Reply

243 solutions
Top badges earned
Coach
Contributor
Seeker
Bedrock
Boost 500
View profile
Andrey_Osadchuk
MVP

04-09-2018

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. 

Avatar

Avatar
Boost 5
Level 4
pranavkaushik
Level 4

Likes

39 likes

Total Posts

37 posts

Correct Reply

13 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile

Avatar
Boost 5
Level 4
pranavkaushik
Level 4

Likes

39 likes

Total Posts

37 posts

Correct Reply

13 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile
pranavkaushik
Level 4

19-09-2018

Hi Marina,

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.

Avatar

Avatar
Give Back
Level 1
frederika281331
Level 1

Likes

3 likes

Total Posts

3 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Boost 3
Boost 1
View profile

Avatar
Give Back
Level 1
frederika281331
Level 1

Likes

3 likes

Total Posts

3 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Boost 3
Boost 1
View profile
frederika281331
Level 1

24-10-2018

Hi,

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.

Regards,

Frederik.