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 drop-down list on the library, then select Submit for Approval. Click Submit on the modal window.
Click the library’s drop-down list 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 drop-down list again, and select Approve for Publishing.
Click the library’s drop-down list 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 install 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 extensions: Some extensions, such as ad blockers, can prevent image requests from firing. Disable any extensions that might stop data from being sent to Adobe.
Now that a basic implementation is set up, your role within your organization can influence which path you want to learn more about: