This article guides you through the steps necessary to provision a global mbox to deliver other nested mboxes into your pages with Adobe Test&Target, accommodating multiple optimization campaigns without campaign conflict.
In order to accommodate the multitude of Optimization Campaigns at scale that an enterprise business typically runs in Adobe Test&Target, you'll need to provision a "Global Mbox" on the page that can be used to deliver as many additional nested mboxes as you need according to the amount of concurrent campaigns you'll be running. Since one mbox may only be used to deliver one campaign's offer at a time, using a "Global Mbox" you'll be able to provision additional mboxes, one per the active campaigns that will be running concurrently. This allows for greater scalability without campaign conflict. As each Optimization Campaign has completed and its corresponding nested mbox is no longer needed. You'll be able to remove that nested mbox from being provisioned. Naturally, your "Global Mbox" will need to be deployed via your "Global Rule" to be activated globally.
Provisioning Your Global Mbox
1. To begin, launch the Ensighten Visual Tagger and click on the "Testing" button. From there, click on the "T&T Provisioner" button to enter the module.
2. Enter a name for your global mbox. Keep it as semantically meaningful as possible so you will easily recognize it when setting up your T&T campaigns.
3. Next, choose the mbox type. Select "Global" and continue.
4. Click on the "Targeting" button to expand its contents. From here you can build your conditional targeting which acts as a filter and only creates your mbox if the proper URL or Data Layer conditions are met. While you can leave your targeting blank and run this mbox on every page of your site, globally, using the targeting in T&T to filter out when to fire you campaign, extra mbox calls accrue a cost both financially as well as for your overall page load performance, even if slight. Using this targeting you can deliver your mbox only where it will be used and thus save on cost. This is a very important step in optimizing your optimization efforts.
4.1 First off, click the "+ Add Condition" link to create a new targeting condition which will appear at the bottom of the "Targeting" container.
4.2 Check the checkbox at the top left of your new condition to set it as active. Any conditions without their checkbox checked will not be compiled into the final, combined targeting logic.
4.3 You can build your condition around data stored either in your current URL or by your predefined Data Library so select appropriately.
4.4 Based on your selection, the next select box will populate with corresponding sub options. Make your next selection and continue.
4.5 Now choose an operator or evaluator for your condition in the third select box and continue.
4.6 And finally, enter the final, conditional values upon which your new targeting condition will evaluate as "true". For example, if you've selected "URL" and "Host" "equals" with the value of "www.mysite.com", your "Global Mbox" will only be created on the pages of "www.mysite.com". Or if you have selected "Data Library" and "Language" "equals" with the value of "en", your "Global Mbox" will only be created for visitors that have their browser language set to English.
NOTE: If you do not have a Data Library predefined and delivered on your current page already, you will be shown a custom form field to enter any data element name you wish, assuming you'll be setting up that data element into your Data Library later. If the data element that you have manually entered does not yet exist when your new mbox rule is deployed and running live on your site, the data element will evaluate as a "" blank string value within your condition logic.
You may also enter multiple values within the value form field as a multi-line value, entering each value variation one by one on each line of the form field. These value variations will evaluate as "OR" as in "this or that or that" and so on for as many values as you enter. This way you can set up multiple variations of your condition to save on time. Using the URL example above, you could have entered "URL" "Path" "equals" "/landingpage.html" "OR" "/landingAlternate.html". As long as your visitor lands on one of those pages, your mbox will be created.
4.7 If you wish to add another condition, simply click the "+ Add Condition" link again and repeat the steps above.
5. Next, select whether you'd like to use the same name for your "Global Mbox" on every page or whether you'd prefer its name to be generated dynamically, to which there are some additional advantages. If you have opted to use the "Same Mbox Name, Globally", a "Global Mbox" with the name you've entered above will be created on every page that meets your targeting criteria. Often, however, this results in mboxes being created on pages where you will not immediately be using them for your Optimization Campaign. As mentioned above, extra mbox calls accrue a cost both financially as well as for your overall page load performance, even if slight, so while the static-named global mbox is easy enough to set up and has its uses such as for global site redesign testing or engagement tracking through T&T, you'll find even greater cost savings by selecting to create a "Dynamically Generated Name" for your "Global Mbox".
The "Dynamically Generated Name" mbox will compile together your "Global Mbox" name on each page based on the URL and some configuration options which will appear in a container as soon as you make that selection.
5.1 First, you'll have the option to enter a "Global Prefix" which just means a namespacing or identifier that will precede all the mboxes being dynamically generated. For instance, if you entered "MWS:" to identify "Global Mbox" names dynamically generated on "MyWebSite.com", all the mbox names for this "Global Mbox" will begin with "MWS:" first. This will help organize all your dynamically generated mboxes in T&T.
5.2 Next, regarding filtering out website domains, select whether you'd like to "Exclude" domains as in a blacklist approach or "Include" domains using a whitelist approach. Then enter all the website domain host values, comma-separated, in the next field. This is an extra level of targeting that will keep your costs down and will only dynamically generate a "Global Mbox" on the specific domains where you will be running tests.
5.3 Next you have the option to include a comma-separated lists of any folders within you site that, should they exist in your URL at the time, a "Global Mbox" will not be created. In this way, you can refrain from creating a "Global Mbox" on entire sections of your site. For example, if you entered "support,contact" the "Global Mbox" would not be created for any pages within your Support section or Contact section of your website, assuming that those folder names appear in the URL for those sections.
5.4 And finally, you can enter a comma-separated list of any special folders that, should they appear in the URL of the page being loaded, not only will a "Global Mbox" be created, but its dynamically-generated name will leverage the name of your special folder. For instance, if you entered "cart" then on every cart page that is in the "/cart/" folder of your site, no matter how many folder levels deep in your URL, an mbox will be created and use the value "cart" within the "Global Mbox" name.
5.5 In most cases this is all that needs to be done and the "Standard" implmentation can remain selected. However, there is also an "Advanced" feature that is hidden until the "Advanced" option has been selected. The "Global Mbox" uses your previously entered "Global Prefix", the hostname of the domain, and the name of the first folder name of your website subfolders that appear in the URL. This is intended to create a "Global Mbox" with a different name for each of your top-level directories of your site, yet keep the name consistent within that entire directory subsection. Having a section-named "Global Mbox" allows you to deactivate entire site sections in T&T that you will not need to be testing and therefore save on cost, while creating the mbox on sections where testing will be in progress without having to fundamentally re-configure your "Global Mbox" settings with each change. However, some website server-side frameworks will prepend your directories with their own special folders that never change across all sections, and therefore they do not truly represent your top-level directories. This is especially common for E-Commerce platforms where something akin to "/estore/" is always the first folder of every URL past the home page. Once you've selected the "Advanced" implementation, you'll be given the opportunity to trim off certain folders from your URL from being counted, and begin your dynamic name generation on the true top level directory, whether that's the 2nd folder deep up or further on up to the 4th folder level in.
5.6 After that, you'll notice a textbox with the current URL displayed within and a "Test Name" button below it. If you click the "Test Name" button, you'll be able to get a preview of what such a dynamically generated name would look like using your current configuration settings on the current page that you're on. To see what name would be generated on other pages, simply change the URL in the textbox and click "Test Name" again. Use this feature to get a good feel for the types of names that would be generated throughout your website and tweak your configuration options according to your needs.
6. Setting up "Mbox Parameters" is optional, but a great way to build user profiles and power targeting in T&T. If you choose to send in extra targeting or profile data into T&T via your mbox, click the "Mbox Parameters" button to expand its contents.
6.1 First off, click the "+ Add Parameter" link to create a new mbox parameter which will appear at the bottom of the "Targeting" container.
6.2 Check the checkbox at the top left of your new condition to set it as active. Any conditions without their checkbox checked will not be sent into your mbox request.
6.3 Enter a name for your parameter. Keep it as semantically meaningful as possible as you may be using this for targeting in T&T and will need to understand what it refers to. In addition, if you intend to send this data into T&T to build a user persistent profile, enter "profile." at the start of your parameter name.
6.4 Next, select the data element whose value you'd like to map into your new mbox parameter. You'll notice as make your selections that you'll see a preview of your parameter name=value pair at the bottom of your parameter container that represents the data that will be sent into your mbox request. At the bottom of your select box there are three special options, *Custom*, *All Data*, and *All Profiled*.
- *Custom* - allows you to manually enter in a custom value for your parameter without using your Data Library.
- *All Data* - compiles all the Data Library data elements that exist on your page and sends the entire parameterized string into your mbox request.
- *All Profiled* - does the same thing as *All Data*, but prepends the "profile." syntax before each data element of your Data Library to build a persistent user profile in T&T out of your entire Data Library on each page that your mbox will be created.
6.5 If you wish to add another mbox parameter, simply click the "+ Add Parameter" link again and repeat the steps above.
7. Once you've configured all your targeting, naming, and parameter options, you're ready to create your new "Global Mbox" rule within Ensighten Manage. Click the "Create Rule" button at the bottom. Once clicked, every item that has been check-boxed will be added and compiled into your mbox rule. So long as you are currently logged into Ensighten Manage, your mbox rule will be posted directly into your account as a new custom rule, ready to be configured and approved for deployment. If you do not see the "Rule created successfully" message, please log into Manage in a new tab or different browser and try again to ensure your rule becomes created.