FAQ for Adobe Target Deployment - Released October 28 2014

Frequently asked questions for the Adobe Target deployment using dynamic tag management. This content is relevant only to the Target tool updated on October 28 2014.

Important: Adobe recommends that you thoroughly test this Adobe Target integration in your staging library before publishing the new tool configuration to your production library. Testing the new integration mitigates potential conflicts with your current implementation before it is implemented on your production site.

Question Answer

Is this a new Adobe Target tool or a change to the existing tool?

A change to the existing tool.

If you currently have an implementation of Adobe Target in dynamic tag management, it will continue to function as is unless you make a change. Please review the following questions for more details on avoiding potential issues.

Do I have to do anything to get the new functionality?

No.

The existing tool automatically becomes available. You can then view the configuration for your Adobe Target tool to see the new configuration options.

If I make configuration changes in the new version of the tool, can I test in staging before publishing to production?

Yes.

All changes can be tested in staging just like you normally would before deploying to a production environment. If you choose not to publish, because you notice issues in staging, the production code will continue to function as it did before the new integration was released.

If I switch from manual configuration (the default setting for existing tools) to automatic configuration, will my current settings be affected?

No.

How does changing from manual library management to Managed by Adobe affect my current settings or code?

The code previously hosted in the manual editor is replaced by the mbox.js code supplied by the linked Adobe Target account.

See Library Management - Adobe Target

Will the revision history for the Adobe Target tool be retained when the new integration is released?

Yes.

I currently load Adobe Target through a page load rule. Should I be aware of anything as I migrate to the built-in tool?

If you currently load mbox.js through a global page load rule, adding a new Target tool to the property, or changing the configuration of an existing Target tool, could break this implementation method. This occurs because the tool deploys another instance of the mbox.js when utilizing either of the available automatic configuration options, or the Manual > Hosted by Adobe configuration option.

To avoid this issue, test the deployment in staging to ensure you are only deploying a single mbox.js code on your site before deploying a new tool configuration to production.

What pitfalls should I be aware of as I migrate to the Adobe Target tool?

With the present functionality of the mbox.js code, auto-loading the mbox.js code via the integrated Target tool could break scripts currently being deployed later in the <head> as they may be pushed down into the <body/> section of the page.

If you encounter this conflict, revert to the Manual code configuration (your hosted code is retained and becomes available in the Custom editor), and move the createGlobalMbox() function out of the mbox.js code. Place it in a page load rule to avoid sequencing issues.