Experiences Double up when Updating GlobalMbox via DTM. | Community
Skip to main content
M
michel_proulx
Level 2
June 13, 2017
Solved

Experiences Double up when Updating GlobalMbox via DTM.

  • June 13, 2017
  • 5 replies
  • 4024 views

Hi Guys,

When we have a default experience shown & then attempt to update the experience on the same page with an mbox update through dtm, our activity reloads and show both the original version & the new version.

The page itself doesn't reload which is good but we can't seem to remove the old experience, it only appends the new experience.

Sound familiar?

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ralphy31443771

Hey guys,

We've found a different solution for this.

The issue stemmed from the fact that our data was stored in an array and we needed to only pass the first value of the array to target. So the initial approach was to transform the data on page load and then update target via mboxupdate. This then lead to the issue of target-global-mbox being reloaded on update and having element generated by the mbox double up on the page (banners, etc).

To get around having to do an update on page load, I created data elements that used a custom script to transform the data. Now that they're part of the dtm layer, they're loaded before the initial target-global-mbox load and we are able to pass already transformed data via Global Mbox Parameters in DTM.

5 replies

ParitMittal
ParitMittal
Level 10
June 15, 2017

Hi Michael,

Are you triggering mboxUpdate()  via Page Load rule or you are triggering the mboxUpdate() for javascript events on the page via Event based rules in DTM.

If you are using the Page Load rule, Please trigger the rule at the top of the page to ensure that the default content is hidden until the mbox response has been received

Regards

Parit Mittal

R
Adobe Employee
ryanr7Adobe Employee
Adobe Employee
June 15, 2017

Hey Michael,

I have some additonal questions that will help us better understand your situation:

  1. On the initial page load is Target's response returning any content changes?
  2. What mbox name is used in your update call to Target? Is it fired only once on the page?
  3. What kind of a content change is being made? Is this using the insert element edit option by chance from the Visual Composer?
M
michel_proulxAuthor
Level 2
June 15, 2017

Thanks so much Guys, just looping in my IT counterpart on this. well get back to you soon...

R
ralphy31443771Accepted solution
June 16, 2017

Hey guys,

We've found a different solution for this.

The issue stemmed from the fact that our data was stored in an array and we needed to only pass the first value of the array to target. So the initial approach was to transform the data on page load and then update target via mboxupdate. This then lead to the issue of target-global-mbox being reloaded on update and having element generated by the mbox double up on the page (banners, etc).

To get around having to do an update on page load, I created data elements that used a custom script to transform the data. Now that they're part of the dtm layer, they're loaded before the initial target-global-mbox load and we are able to pass already transformed data via Global Mbox Parameters in DTM.

ParitMittal
ParitMittal
Level 10
June 19, 2017

Thanks Ralph . We are glad to know that the issue is resolved .

Terms & ConditionsAccessibility statement

Loading footer...