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

Adobe Target use cases

Avatar

Avatar
Validate 1
Level 2
muthu1985
Level 2

Likes

9 likes

Total Posts

27 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Applaud 5
View profile

Avatar
Validate 1
Level 2
muthu1985
Level 2

Likes

9 likes

Total Posts

27 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Applaud 5
View profile
muthu1985
Level 2

14-08-2017

Hi,

I'm new to Adobe Target. just trying to understand global mbox parameter usage. Is there any use cases/example to understand better on why we should use global mbox.

thanks,

Muthu

Replies

Avatar

Avatar
Boost 5
Level 3
LJ_Jones
Level 3

Likes

27 likes

Total Posts

37 posts

Correct Reply

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

Avatar
Boost 5
Level 3
LJ_Jones
Level 3

Likes

27 likes

Total Posts

37 posts

Correct Reply

8 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile
LJ_Jones
Level 3

16-08-2017

The old way in Target Classic was to wrap non global mboxes around specific divs on the page so that you could target content and changes to those divs.  This made it easy to run specific content tests to those specific divs on a page.  I find this to be limiting. 

In Target Standard, you use global mboxes.  The global mboxes allow you to make changes anywhere on the page and don't restrict you to just those divs.  It also allows you to use the visual experience composer.  Global mboxes will allow you to create much more complex tests which often have a better chance of producing a significant result.  You will want to use Global mboxes.