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. Those builds are delivered to a hosted location.
Adapters define available destinations where the builds can be delivered. They come in two types:
Managed by Adobe
The same adapter can be used for multiple environments within a property.
This adapter type is the default selection and is simplest to manage.
When you choose the Adobe-managed option, libraries that Launch builds will be delivered to a 3rd party CDN that Adobe has contracted with. These CDNs operate independently from Adobe, so even when Launch has maintenance or downtime, the tags deployed to your sites and applications continue to function as normal. The embed code references the main library file on the CDN so a browser can retrieve the files at run-time.
Today, the primary CDN provider is Akamai. Files hosted on Akamai will have a domain of assets.adobedtm.com. This can be referenced securely or not securely (http:// or https://) based on how you call it in your
When you create a new property through the Launch UI, a default adapter of this type is created for you.
Open the Adapters tab.
Create the new adapter.
Name the adapter.
Select Managed by Adobe as the adapter type.
If you do not want your builds delivered to Akamai, your other option is to have Launch deliver builds to a secured SFTP server that you host.
Launch connects to your SFTP site using an encrypted key. There are a few steps to set this up correctly:
You must have a public/private key pair installed on your SFTP server. You can generate these keys on your server or generate them somewhere else and install them to your server. See here for an example of how to generate keys.
You must encrypt the private key with Launch's public GPG key so that you can provide your private key to Launch during the SFTP adapter creation process. See here for instructions and Launch's public GPG keys. Unless you know you need a different one, use the Production Environment's GPG key. Finally, you can encrypt your private key from any machine, you do not need to install GPG on your server in order to complete this step.
You may need to whitelist the Launch IP addresses with your company firewall to allow Launch to be able to reach your SFTP server and connect to it. Those IP Addresses are:
There is a full guide on how to setup SFTP servers for Launch delivery on the Launch blog.
Open the Adapters tab.
Create the new Adapter.
Name your adapter.
Select SFTP as the adapter type.
Enter the host, path, port, username, and encrypted private key.
When you click Save, Launch will test whether it is able to connect to - and deliver files to - your SFTP server. It will create a folder, write a file within that folder, and then check to make sure the file is there, then cleanup after itself. If the user account on your SFTP server (the one attached to the secure certificate you provided to Launch) does not have the necessary permissions to perform this action, then the Adapter will go into a "Failed" status.