Once a property has been created and configured in Launch, the libraries are ready to be deployed and code implemented on your site.
Create and configure a property for Adobe Analytics in Launch: Access the tool and create a space for your Analytics implementation.
Launch accommodates many organizational workflows in deploying code. Follow these steps to create the minimum necessary components for an Analytics implementation. As a Launch 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:
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Example page</title>
<script src="//assets.adobedtm.com/launch-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-development.min.js?lang=en"></script>
</head>
<body>
<p>This is a test page.</p>
<script type="text/javascript">_satellite.pageBottom();</script>
</body>
</html>
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.