Hi Team,
Asking this query, out of my curiosity.
I was checking the integration between AEM application with Adobe Launch, Adobe Analytics.
DevOps team will create script in Launch, then that script is used in AEM application. So that, every time when page loads, Adobe launch script will execute and it will pass the data to Analytics. Wanted to know, where this Adobe Launch script is placed? is it in Akamai CDN?
I am new to Adobe Analytics. While reading the study material, I heard about placement of Adobe Launch script in some CDN.
Solved! Go to Solution.
Views
Replies
Total Likes
The Adobe Launch script initially (without any extra effort) can be hosted by Adobe's Akamai servers, which is a CDN (assets.adobedtm.com). This is the default host / environment configuration. However, you aren't limited to this.
Within the Hosts area of launch, you will have the default "Adobe Hosted", but you can add your own host:
At present, the only "custom" solution is SFTP:
This is actually the solution we use. I use the Adobe Hosted for Dev, and our SFTP Host for Staging and Production.
This is because our SFTP isn't connected directly to our site.. When I deploy code to staging or production, the files are uploaded to an SFTP server.. then we have a Jenkins job that will take the files in SFTP and deploy them to our Web Servers... so continuing to use Adobe's host for Dev means I can test code quicker and easier within Dev and QA, and then I can verify the "final builds" and deployment process with Staging; and of course, then our production file is hosted on our own server and CDN.
This is up to you, whether or not to pursue a process to host your files in your own infrastructure, and you don't necessarily need to have an extra deployment step between uploading to SFTP and then to your web servers.. that will be something you would have to talk about with your own DevOps team.
The Adobe Launch script initially (without any extra effort) can be hosted by Adobe's Akamai servers, which is a CDN (assets.adobedtm.com). This is the default host / environment configuration. However, you aren't limited to this.
Within the Hosts area of launch, you will have the default "Adobe Hosted", but you can add your own host:
At present, the only "custom" solution is SFTP:
This is actually the solution we use. I use the Adobe Hosted for Dev, and our SFTP Host for Staging and Production.
This is because our SFTP isn't connected directly to our site.. When I deploy code to staging or production, the files are uploaded to an SFTP server.. then we have a Jenkins job that will take the files in SFTP and deploy them to our Web Servers... so continuing to use Adobe's host for Dev means I can test code quicker and easier within Dev and QA, and then I can verify the "final builds" and deployment process with Staging; and of course, then our production file is hosted on our own server and CDN.
This is up to you, whether or not to pursue a process to host your files in your own infrastructure, and you don't necessarily need to have an extra deployment step between uploading to SFTP and then to your web servers.. that will be something you would have to talk about with your own DevOps team.
Thanks a lot @Jennifer_Dungan for your effort and dedication to reply to my query with detailed explanation. Will trouble you soon
Well I look forward to helping you, and I can assure you, it's no trouble at all. Welcome to the world of Adobe Analytics!
Hi Jennifer,
We are trying to setup something same.
We are finding the possibility to have both Akamai and SFTP host in single property due to some security concern.
I'm trying to figure how this would be possible, when we can publish only single env in prod. Basically only one library can be managed in the prod .
Since, I'm new to publishing flow part and self hosting. I'm not sure how self hosting works. Could you please help me to understand how this could be possible? Thanks
Hi @SA30,
You really cannot have multiple "prod" hosts... there is only one prod website, and therefore only one Adobe Launch file for it.
So you can use either Adobe hosted (this loads the file off of adobedtm.com domain), or you can self-host (which means that you publish the JS files to a server that you own, and the files are loaded from there, usually on your domain or a sub-domain for your site.... or you take it a step farther like us... we send our files to an SFTP location, then we have a deployment process to copy the files from there to our webserver.)
You can however have different hosts for different servers.... we use Adobe Hosted for all our Dev builds (because these are quick - we don't have to do the full deployment process to test all the incremental changes). Our Staging and Prod however are both self-hosted. So that we can test our deployment process with the build that will go to prod, and of course our production files.
Do you have any specific questions?
Views
Replies
Total Likes
Views
Like
Replies