Validate a development implementation and publish to production
Once your tag library is pushed to production, your organization can begin to use Adobe Analytics to pull basic reports.
Adobe Experience Platform Launch has been rebranded as a suite of data collection technologies in Experience Platform. Several terminology changes have rolled out across the product documentation as a result. Please refer to the following document for a consolidated reference of the terminology changes.
Deploy your Analytics implementation to your dev environment: An Analytics implementation must be published to your development environment in order to follow this page.
Validate your dev implementation using the Experience Cloud debugger
The Experience Cloud debugger is a Chrome plug-in that shows all Experience Cloud tags present on a page.
- Open Chrome Web Browser and go to Adobe Experience Cloud Debugger on the Chrome Web Store to install the extension.
- Navigate to your development website that you have implemented tags on.
- Click on the Adobe Experience Cloud debugger icon in the upper right of Chrome
- If everything is properly implemented, you should see content inside Adobe Analytics, tags, and the Adobe Experience Cloud Visitor ID service:
Deploy your dev implementation to staging/prod
Once you’ve validated you’re seeing data, you can push your implementation to the live version of your site.
- Go to experience.adobe.com and log in when prompted.
- Select Launch / Data Collection.
- Click Go to Launch / Data Collection, then select Tags.
- Click the tag property that you intend to implement on your site.
- Click the Publishing tab and locate your library in the development column.
- Click the dropdown on the library, then select Submit for Approval. Click Submit on the modal window.
- Click the library’s dropdown again (now in the Submitted column), and select Build for Staging.
- After a few moments, the yellow colored light on the library turns green, indicating a successful build.
- Click the library’s dropdown again, and select Approve for Publishing.
- Click the library’s dropdown again (now in the Approved column), and select Build and Publish to Production.
- Go to the Environments tab, the click Production Environment.
- Copy the production header + footer code, and provide it to your website owners. Request that they implement this code on your site’s production environment.
Validate your production implementation
Confirm that you’re seeing data on the live version of your site, and begin official data collection for Adobe Analytics.
- Once you have confirmed from your website owners that they have pushed the tag code to production, navigate to your website’s homepage in Chrome and open the Adobe Experience Cloud debugger.
- If everything is working, you should see similar data to your tests in your dev environment. At this point, you are now collecting data on your site and can now start using Adobe Analytics for reporting.
No data appears in the debugger.
While on your site, open the browser’s developer console (typically F12). Look at the source code of the page and make sure the following are met:
- Header code is properly implemented: Make sure the header code is inside the
<head> tag, and that the file exists.
- AppMeasurement library exists: Navigate directly to the JS source to make sure the JS file contains code. If it does not, make sure each environment is created, and that the library is published to its respective environment.
- Interfering plug-ins: Some Chrome plug-ins can prevent image requests from firing. Disable any plug-ins that might stop data from being sent to Adobe’s servers.
Now that a basic implementation is set up, your role within your organization can influence which path you want to learn more about: