A traditional Test&Target deployment requires individual mBoxes to be added to specific site content that has been identified for optimization.
This approach makes swapping in test content really easy, I just need to create an HTML Offer that contains a different image that I want to test:
However, this approach forces you to know ahead of time what content you want to test. What happens 3 months later when you have new content you want to optimize? If you are like most organizations, you place a request into IT to have the new code deployed and they respond how happy they are to include your code in the next release that is scheduled to go out in 6 weeks.
This is where a Global mBox Strategy becomes your friend. A Global mBox is really nothing more than an mBox deployed to every page of your site (or specific pages on which you are focusing your optimization efforts). This mBox is different than the one we described earlier in this post in that it doesn’t wrap or define any specific content on the page to be tested.
Global mBox Example:
Now that we have our Global mBox deployed, we can test any page content we want without having to identify that content ahead of time. The method of creating your test offers will be a bit different, you will write script to manipulate the page rather than just coding in standard HTML. Once you are confortable with this approach, your ability to test when and where you want will be greatly increased.
The following video tutorial will walk you through the basics of how to execute a test using a Global mBox Strategy: