Why do AAM data collection server (DCS) responses appear to be slow

If you notice slow response times from the Adobe Audience Manager data collection servers (DCS), you should first check http://status.adobe.com/marketing_cloud for any related system outages that might cause this, but chances are that a third party or customized JavaScript file is in use, such as from a tag management system to integrate different software into your digital properties (e.g. Tealium's Universal Tag manager, Google Tag Manager, etc). If a third-party or customized file is firing the call to our server, that file could have an effect on the reported response time to your browser, even while the actual response time from the server has already been received by your third-party script.

If a third-party or customized file is firing the call to our server, that file could have an effect on the reported response time to your browser. The response from AAM might have already been received by the device, but the JavaScript file could be performing additional calls before finalizing.

If no known outages are reported at status.adobe.com, you will want to verify that the responses from our DCS are still slow when not using a third-party JavaScript file to control AAM calls. If a third-party script is making the calls to our DCSs, rather than from the Adobe-provided script (which includes our own tag management system at dtm.adobe.com), we're unable to troubleshoot your issues.

However, if the calls to the AAM DCS are coming from an Adobe script on your web page and you find these response times are taking more than 500 milliseconds, we'll be happy to investigate our servers for any issues and verify the behavior for you.

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.