Extensions, rules, and data elements are building blocks. When you want to make your application do something, these building blocks are added to libraries and then a library is "built" into a build.
When you create a library, you must assign it to an environment. When the library is built, Launch uses the settings from the assigned environment to determine the following:
Destination - This is the location where you want your build to be deployed. It is controlled by selecting an adapter for the environment to use.
Archive Format - You can get a deployable set of files or have it zipped up in an archive format. This is controlled by the archive settings.
Embed Code - This is the code you'll use to deploy your build at run-time and will be different based on property type.
On the environment screen, you have a drop-down menu to select from the existing adapters on your property.
When a build is created, Launch will deliver that build to whatever location you've specified with the assigned adapter.
Most builds consist of multiple files. Multi-file builds contain a main library file (linked in the embed code) that contains internal references to the other files. Those other files are pulled in as needed.
By default, the archive option is
off, and the build is delivered in a format that executes at run-time as is. For Web properties, this is .js. For Mobile properties, this is .json.
If you use the archive option, all build files are delivered as a .zip file (optionally encrypted) instead. This can be useful if:
You are self-hosting the library, but don't want to set up the SFTP adapter for delivery.
You need to run code analysis on the build prior to deployment.
You just want to look at the build contents to see what's in it.
The embed code is a
<script> tag that you put on the pages of your site to load and execute the code you build in Launch.
You can choose to have this tag be synchronous or asynchronous.
The embed code is generated for you based on the environment configuration, so the only required action for you is to copy and paste them into your site on the pages where you want Launch to run.
Embed codes are generated and updated when you save the environment.
If you load the library synchronously, when the browser reads the embed code, it retrieves the Launch library and executes it before continuing to load the page. This is also how DTM works.
In a synchronous deployment, the embed code consists of two
<script> tags that you need to put within the HTML of your website. One
<script> tag goes in the
<head> and one goes at the footer in the bottom of the .
If you load the library asynchronously, the browser continues to load the page, retrieves the Launch library, and executes it in parallel. In this case, there is only one embed code, which you put in the
<head>. Depending on what's in your Launch library, the switch from sync to async can change the behavior of your rules and other elements, so be sure to thoroughly test any changes.
The paths contained in the embed code depend on the configuration of the environment, so if you update the environment configuration, it is possible the embed codes will change.
Configuration changes that change your embed codes are:
Switching from an Akamai adapter to an SFTP adapter (or vice versa)
Marking the Archive box
Updating the path field (the embed code changes in real time as you update the path)
When the embed code changes in Launch, you'll need to update the embed codes in your HTML. For obvious reasons, many people try to avoid changing embed codes after they've been implemented.
New properties are created with three environments: one Development, one Staging, and one Production. This is enough to run the publishing workflow. If desired, you may add additional Development environments. This is most common on larger teams with multiple developers working on different projects at the same time.
Open the Environments tab.
Click Create New Environment.
Select the type of environment you want to create.
The environment where you create and edit, events, configurations, and so on.
The environment where you test and approve your changes.
The environment where your embed codes are placed in the pages or applications that are available to the public.
Select your adapter.
(Optional) Enable Create Archive if you want your build delivered as a .zip package. If you want to encrypt the .zip file, enable Encrypt Archive and enter an encryption password. Enter the location where the library is hosted. The path can be either a full URL or a relative path that can be used across multiple domains. This is important because most builds have multiple files that contain internal references to one another.
In the Web Install Instructions dialog box, select whether to load the library asynchronously. If you choose to load the library asynchronously, copy the embed code provided in the dialog box. You can also install your embed code later by clicking the Install icon for that environment in your Environments list. Refer to the information below.
Repeat for each environment in your development, approval, and publishing change.
After the environments are created, you are ready to publish.