If you are a Target Classic Workflow user and aren’t able to use the global mbox for all of your campaigns, the Adobe Target Tool provides an easy method to place wrapping mboxes with built-in flicker handling.
The Adobe Target Tool integration currently uses the mboxUpdate method to make mbox calls, so keep the following in mind:
- The mboxUpdate call waist for the window onload event before the call is made. Test content takes longer to appear than when using mboxCreate .
- Extra SiteCatalyst calls will be made if using the legacy Test&Target > SiteCatalyst integration plugin. Consider switching to the “Analytics for Target” back-end integration.
To add an mbox placed by dynamic tag management:
- Navigate to Rules > Page Load Rules .
- Click Create New Rule.
- Name the rule.
- Add conditions.
- Trigger the rule at Top of Page to ensure that the default content is hidden until the mbox response has been received.
- Add the mbox:
- Expand the Adobe Target section.
- Choose the element to wrap with the mbox using a CSS selector.
- Name the mbox.
- Use the default Timeout value of 1500ms.
- Add parameters.
- Save the rule.
- Perform the instructions in QA, Approval, and Deployal Steps .
You can add parameters to your mbox calls with static or dynamic values. Parameters can be regular mbox parameters or profile parameters. To make the parameter a profile parameter, use “profile.” in the name (e.g., “profile.customerType”).
Additionally, if you’re using an auto-created global mbox, you can add global mbox parameters that will be included with the auto-created global mbox. See Mbox Parameters for details.
Below is an example of an mbox named “hero” that wraps an element with an ID of “hero” and includes an mbox parameter named “pageName” with a value that is dynamically populated by a data element called “Page Name.”