Adobe Launch Basics - Embedding Launch and Environments

this video is going to be a tutorial about how to embed adobe launch into your website so you can start collecting data with Adobe Analytics and utilizing launches tech management abilities I'm going to assume that your property has already been created and that libraries have already been published in it when you first open up a property and launch you'll be taken to this overview tab in order to find your embed codes you'll want to navigate to the environments tab here you're presented with three environments and you have the option to create additional environments these environments represent the different stages of the launch publish process and loosely correspond to the different stages of developing a website I'm gonna tell you how I like to set up my environments and what I found works best but there are no set of rules so feel free to adjust these directions for your specific situation or website there are production staging and development environments each one of these environments will contain a unique embed code that you need to place in the global head of your website depending on which development level you are working in you'll understand what I mean by that is second starting with the production environment it contains the embed code that needs to be placed in the global head of your production website if I click on the gray box in the install comm it will bring up the installation instructions here I can find the code snippet that I need this process is the same for the staging and development environments I like to place the staging script in the non production environments of my site things such as beta test or uit because staging represents the level below production and a lodge publish process as for the development script I typically don't embed that anywhere rather a user to work in isolation from other environments that way any changes I make and launch will not affect the staging or production environments or any other development environments that may exist I'll show you how to switch between environments in a few minutes for now I'm going to open up the production installation instructions as you can see I have the option to load the library asynchronously which is one of launch's biggest upgrades over TTM I can also choose to not load the library asynchronously but I will need to add this extra piece of code that tells launch that it has reached the end of my page when it loads the general consensus in the launch community is that you should always be loading the light library asynchronously because it increases page performance I'm going to double check that the load library asynchronously option is selected and that the async attribute has been added to my script tag now I'm ready to copy the script element and head over to my website here I have a simple website running locally that I'm going to place the launch code into for this demo I'm only going to be placing the production embed code because this site does not have non production environments however this process is the same for embedding any type of launch environment here I have my index.html file which contains my COBOL head element so I'm going to paste the embed code here you can put the code into your global head element in any way you see fit for example this is a react website so I can make a react component that loaded the staging or production embed script based on one environment my site is currently in but for now I'm just gonna save my index.html file and I should see my page reload with the launch script loaded if I hop over to my network tab I should see a 200 from the launch library since I have a launch library loaded on my page I can use the launch switch Chrome extension to jump between environments without having to embed them each time clicking on the launch switch Chrome extension will bring up a drop-down of my available environments as well as show me the environment my page loaded with originally in this case it's the production environment if I wanted to switch to the staging environment I all I'd have to do is select it from the drop down and reload the page I can see in the network tab that my page originally loaded the production library but then redirected that request to the staging library this is useful for testing rules and changes on production version of a website without having to publish those changes all the way through to the launch production environment now that it has successfully Adam launched to my page I'm ready to start setting up my analytics collection and tag management in the launch UI

Channel: John Simmons

Views: 901

Keywords: adobe launch, adobe analytics, web analytics, web development

Id: oToBytC9QDE

Length: 4min 44sec (284 seconds)

Published: Wed Jun 12 2019