This article contains the answers to frequently asked questions about Adobe Experience Platform Auditor.
Auditor is a service of the Adobe Experience Cloud that was co-developed with ObservePoint, experts in validating digital implementations.
With Auditor, customers can scan up to 500 webpages at a time and receive a report that shows how to improve their Adobe Experience Cloud implementations so they receive the full value of their Adobe investment.
The following Adobe solutions are not currently included in the test rubric. Support for these solutions is planned for future updates.
There is no limit to the number of audits you can run. Users are limited to one audit running at a time. An error occurs if you try to start an audit with the same settings as the one that's running.
The ObservePoint technology currently crawls URLs that are found in document links. Links found in buttons, pagination widgets, and other such page elements are not crawled.
You can submit test suggestions via the Auditor Community by clicking Share Feedback on this page: https://forums.adobe.com/community/experience-cloud/platform/core-services/activation-service/auditor
There are many factors contributing to the time it takes for an audit to complete, including:
The ObservePoint engine loads each page of the audit in a browser. The faster a page loads, the faster the audit completes.
Adobe Auditor uses a single connection to visit each page. Full ObservePoint accounts use as many as 10 engines at once.
After each page loads, the audit waits for a network silence of seven seconds before proceeding to the next page. If a page sends a lot of network requests that occur after the page loads, the wait will timeout after 60 seconds.
If a page or tag cannot be found, the audit stores that URL and returns to it later in the audit. The audit will visit a page up to three times to make sure that the error was not caused by a transient issue.
After an audit has run, all the data it has collected is processed and filtered through the rules. This processing time is significant, though it doesn't take as much time as the scan itself.
Each scan generates a report that shows what URLs were scanned, issues found on those webpages, and recommendations on how to correct the issues found.
Results from scans are broken out into three categories:
In addition to these three categories, the report provides alerts containing information you should be aware of but that does not necessarily require immediate action.
The recommendations that come within these categories are then broken out into three additional categories:
All the recommendations given through Auditor are intended to help you take action to fix a problem with your implementation of Adobe Experience Cloud solutions, such as DTM or Target. To facilitate this, the Auditor team has worked extensively to provide very granular instructions on what needs to be done where. You can export a spreadsheet of all URLs scanned and all test results so you can pinpoint problem areas easily. Here is an example of one recommendation for a DTM implementation:
pageBottom callback last
A _satellite.pageBottom() function is required for a correct DTM implementation. Add the inline script immediately prior to the closing </body> tag to ensure proper DTM functionality.
No. However, ObservePoint’s full offering allows customers to audit and monitor all of your marketing tags and technologies. As an Adobe customer you have access to a complimentary trial account. To access your trial account visit ObservePoint’s Auditor Page.
This functionality is currently unsupported without the full ObservePoint offering.
The crawling is performed by ObservePoint, so the same IP addresses are used.
See the ObservePoint documentation for more details.