Once you have created and configured a tag property, the libraries are ready to be deployed and code implemented on your site.
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.
Create and configure a tag property for Adobe Analytics: Access the tool and create a space for your Analytics implementation.
Tags accommodates many organizational workflows in deploying code. Follow these steps to create the minimum necessary components for an Analytics implementation. As a tag admin, you can work within your organization to establish the correct workflow for deploying Adobe solutions.
Despite all the changes and configurations made so far, no code has actually been published. Creating a library, roughly translated as a collection of changes, allows the publishing of code to be used on your site.
If you control your website’s code, implement the two blocks of code in their respective locations (in the
<head> tag and just above the closing
</body> tag) on every page of your site. This code is commonly placed in the site’s overarching template. A blank page only containing implementation code would look like the following:
Attempting to build fails.
A common reason is because elements already exist in other libraries pushed to staging or production. When initially creating libraries, ensure only changed resources are added to the library.
Validate your Analytics implementation and publish to production: Start getting value out of Adobe Analytics.