FAQs about the Adobe Analytics Tool
A FAQ about the automatic configuration of the Adobe Analytics deployment. The automatic configuration method manages the AppMeasurement code for you.
Where do I put my plug-ins when implementing Adobe Analytics via DTM?
If using DTM to manually host the s_code , plug-ins can be added in the same editor as the hosted s_code , just as it would be in a typical Adobe Analytics implementation.
However, it is also an option to place the plug-ins in the editor within the Customize Page Code section of the tool settings. Both implementation methods should be equally effective.
If I make configuration changes in the new version of the tool, can I test in staging before publishing to production?
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?
If I switch from manual library management to Managed by Adobe, will my current settings or code be affected?
Any user code that you have specified is overwritten with the base AppMeasurement library. You must move this code to the new Custom Page Code section at the end of the tool configuration so that the code continues executing. This method allows the AppMeasurement library to be managed (and upgraded) separately from the user's custom code.
Will the revision history for the Adobe Analytics tool be retained when the new integration is released?
See Add Adobe Analytics Tool for configuration information.
There is a small chance that the integration could cause data collection issues if you currently use Adobe Analytics. These issues could arise only if you publish your library to production subsequent to the release. (Production code remains intact until publishing occurs.)
To avoid these issues, ensure that:
- Report suite IDs are correctly entered in the tool.
- Report suite IDs in the tool match the IDs in the AppMeasurement code.
- The currency code, character set, tracking server, and SSL tracking server configuration fields are correctly set with supported values.
- Custom code is defined in Library Management.