Adobe Experience Platform

What is Changing?Adobe Experience Platform Launch will soon require that all ports on SFTP Hosts be on the list below (or fall within the specified ranges).212280200-2994432000-2999434380808888ImpactWhen creating/editing an SFTP Host, Launch will perform validation on the Host's port. If the port is not on the list above, the save will fail with an error.If you happen to create a Host with a disallowed port before these changes, once they go into effect, builds sent to that Host will fail.RationaleWe consistently take steps to improve security and reduce our risk exposure. Limiting the allowed outgoing ports is required by our network and security teams to enhance the infrastructure that supports Launch.Why These Ports?When we conducted our analysis, all existing SFTP Hosts on our customer organizations were already compliant with the list of ports above. You will recognize many as commonly allowed incoming ports for corporate firewalls. The listed ranges let us include the other exist

Modern websites are built by referencing images, content, and scripts from various locations around the web. Sub-resource integrity (SRI) allows a browser to verify that the contents of the requested file have not been unexpectedly modified.SRI is different from a Content Security Policy (CSP), though they work together. When implemented correctly, a CSP ensures that only files from trusted sources are allowed on your site. SRI goes one step further by ensuring that the contents of these files match your expectations. You can read all about SRI and see examples on the MDN web docs. The basics:You generate a cryptographic hash of the asset that you want to validateYou put that hash in your site's HTML as the integrity attribute of the HTML element that loads itWhen the browser sees the integrity attribute, it will request the resource and independently generate the cryptographic hashThe browser compares the integrity hash with the one it generated - if they match, the ass

Corey Spencer took to twitter the other day to answer some of the burning questions we have been receiving about the Adobe Web SDK (Alloy.js).  Below is the whole thread, complied for your reading pleasure. Never heard of alloy ?  Be sure to check out the Adobe Summit 2020 Session:  https://www.adobe.com/summit/2020/with-alloy-js-never-tag-for-an-evar-or-mbox-again.html  Q1: Do I need Launch to use alloy.js.A1: Not as a tag manager. There is a Config ID which needs to be in the data stream (so the edge knows what rules to apply to it). That ID is created in the Launch IU but it is a new section separate from the tagging UI.  Q2: So I will be able to deploy alloy.js anyway I want?A2: Sure. But Launch will make it super easy to map your client-side variables to XDM.  Q3: So the data has to be in XDM?A3: Currently yes. But think of XDM as a format, not a standard. You can use our suggested schema in XDM or create your own. If you’re o

About this time last year, we announced the end of support for TLS 1.0 for libraries being hosted by Adobe. In the same vein, we want you to know that in the early part of April 2020, DTM and Launch will end support for TLS 1.1. TLS 1.2 will be the minimum allowed version.  We will update this post with the exact date when it moves closer and we determine what it is.As before, this is a security requirement coordinated across many Experience Cloud solutions so that they can be in compliance with certain data security standards required for companies who do credit card processing.Effectively, this means that browsers that do not support TLS 1.2 and above will no longer be allowed to retrieve a hosted library over an HTTPS connection. If you are using HTTPS to load your DTM or Launch library, then those browsers will no longer be able to retrieve and execute that library.Browsers that support TLS 1.2 and above - and will continue to function as they do today - are:Chrome 30 and up (

Sharing a tip that I hope will make your life better.When using %this....% with a custom attribute, don’t use quote marks. I.e. use %this.getAttribute(custom-attribute)% without quote marks, not %this.getAttribute("custom-attribute")%.(BTW this goes against my JavaScript sensibilities.)How I discovered this:For a link click, I want to set an eVar to the value of the link’s data-foo attribute. (My link definitely has a data-foo attribute with a valid string value.)Round 1:In the rule’s AA - Set Variables action, in the form, I set my eVar’s value to %this.getAttribute("data-foo")%. In the custom code, for sanity sake, I set another eVar to _satellite.getVar("data-foo"), with the appropriate linkTrackVars.--> Result: my original eVar is set with the string "null", my custom code eVar gets data-foo’s string value.Round 2:In the AA - Set Variables form, I use %this.data-foo%.--> Result: my original eVar is not set at all, my custom code eVar gets data-foo’s string value.Round 3:In th

The Launch API was first made available to customers about two years ago in the earliest alpha state.  At the time, true role-based permissions were not available through Adobe IO, and so in order to limit IO integrations (technical accounts) to certain permissions, we created roles that mapped to sets of permissions.  One of these roles was selected when you created your technical accounts.Fast forward a few years and Adobe IO is now integrated with the Admin Console.  This means that API users can be managed in the same way that flesh and blood users are managed - that is, API integrations can now be assigned to the same product profiles that regular users use.As of September 4, 2019 (see release notes), Integrations of both types are supported in Launch and the older role-based permissions are deprecated.  In February of 2020, the older role-based Integrations will be removed entirely.  Before that happens, someone from your Org will need to login to the IO Console and switch over t

At Adobe Summit 2018 in North America, we made Adobe Experience Platform Launch available to all Experience Cloud customers.  Since that time, we've seen rapid adoption of Launch and have helped thousands of customers migrate over from DTM.Last year, in early October, we announced (here and here) that we are going to sunset DTM.  This means that DTM will be kept up to date with security and bug fixes, but no more feature development work is happening and that it would be unavailable at the end of 2020.  We also said that we would be introducing progressive restrictions on its functionality to encourage users to begin planning and executing the migration process.We are now approaching the first DTM Sunset Milestone.  In about 60 days, on July 9th, we will remove the Add Property button in DTM (we had previously announced this date as July 1, but pushed it back a bit because of release cycles and company events).This change means that beginning with the release on Jul

You might have seen previous posts about this but Launch is building an integration with Adobe Exchange. This integration will give users a better catalog experience so they can get more information, screenshots/videos, and support for each extension. In preparation for this integration we are now requiring any extension in the public catalog to have an Exchange listing.We understand that this means taking time out of your busy schedules to create a listing so we worked with our marketing team to create some limited edition Launch merchandise. Anyone that completes their Exchange listing before June 15th will be eligible to receive a free "Launch" box full of awesome Launch goodies! For instructions on how to create an Exchange listing please see more information here. After you have created your Exchange listing please fill out this short form so we can get some information for where we should send your Launch box. If you have already created an Exchange listing for your extension fe

Effective March 4, 2019, DTM and Launch will no longer support TLS 1.0 in libraries being hosted by Adobe.  TLS 1.1 will be the minimum allowed version.This change is being made at the request of our customers so that these solutions can be in compliance with certain data security standards required by companies who do credit card processing.Effectively this means browsers that do not support at least TLS 1.1 will no longer be able to retrieve a hosted library over an HTTPS connection - thus anything implemented within the DTM or Launch library will no longer be functional on your site in those browsers.  Browsers that do not support any TLS versions above 1.0 are:Chrome 21 and below (current version is 72)Safari 7 and below (current version is 12)Firefox 23 and below (current version is 65)IE 10 and belowAfter this change, TLS 1.1 will be the minimum supported TLS version.  More info on browser support for specific browser versions can be found here.We expect the impact to be immateri

The Ideas section of the Launch Forum is one of the primary ways that the Launch product team receives feature requests from the community at large and we really appreciate all of our Launch users participating there.To date, we haven't been very organized about how we treated these ideas and how we would respond to them.  We're sorry about that.  And we're going to do better.I'd like to take a few moments to describe the process that we're going to use to review the ideas that are submitted here, what each of the different status labels means, and how they transition from one to the other.Idea Review ProcessWith the current size of the community (and expected future growth), the PM team cannot review every single idea that comes in.  We have established a vote threshold and once an idea exceeds that threshold, the PM team will review the item and begin to move it through the workflow below.  The threshold will increase over time as community engagement grows.At lea

We're testing a new behavior with the way that rules execute in the browser.This post will cover the problem we're solving, the solution that we'd like help testing, and the things you should watch out for as you test.  We'll then provide instructions for testing the behavior in your own browser as well as rolling it out to a portion (or all) of your audience.1) The ProblemCurrently, when a rule is triggered, Launch will execute the rule actions in order, but it does not wait for one to finish before the next one starts.This can create problems when the rule action actually does something asynchronous.  This is most common in the case of custom code where the network retrieval of the custom code is done asynchronously, so subsequent actions are often completed before the custom code is retrieved and executed.2) Solution in TestingTurbine is Launch's client-side rules engine.  Turbine is currently shipping with a hidden behavior that you can enable.  Once enabled, rule conditions and ru

In previous versions of the Mobile SDKs, you would use Adobe Mobile Services (http://mobilemarketing.adobe.com) to set your SDK configuration parameters. After making all of your config setting changes you would then download a JSON config file to use in conjunction with the SDK package that you would download from our public git.   With the Adobe Experience Platform SDKs we've changed this process to support an easier, more dynamic workflow. You can still download the SDKs from our public repositories -> GitHub - Adobe-Marketing-Cloud/acp-sdks: Home of the official Adobe Cloud Platform mobile SDK , but now you also have the option of managing your SDKs and solution integrations within Adobe Launch.   In Adobe Launch you now have the capability to create a mobile property. We've separated the Core SDK out as an extension, along with additional extensions for other Adobe Experience Cloud solutions. You can add the appropriate extensions to your SDK build as appropriate and

Welcome! Here is a list of resources you can use to get started using the Experience Platform SDKs.Explanation VideoA quick video to explain what is new with the Adobe Experience Platform SDKsWhere to download the SDKsThe following forum thread explains in detail on where you can download each respective SDK: Get the Experience Platform SDK - Adobe Experience Platform Mobile SDKs Technical DocumentationIf you want to dive right in to the docs, you can access them here: Home - Adobe Experience Platform Mobile SDKs

Community Members,I encourage each of you to have a read through the latest series of blog posts regarding Launch.Better in Launch: Production TestingBetter in Launch: Upgrade Process Better in Launch: Integrations Better in Launch: Automation Better in Launch: Performance Better in Launch: Team Collaboration Better in Launch: Publishing Better in Launch: SecurityBetter in Launch: User Interface Better in Launch: Events, Actions, and Data Elements Please leave any comments or questions you have about these post in the comments below and we'll be sure to address them.Thanks,Jantzen

A follow up piece to give an overview of Script Hoisting and how it's used in Adobe Launch.https://spark.adobe.com/page/n5xi9782gMCei/

Welcome! We hope you're as excited about Launch as we are!How do I get started with Launch?All Experience Cloud customers have been provisioned for Launch. To get started, please review the getting started documentation. This documentation will show you how to setup your users and permissions for Launch.Now that I've logged in, where do I go to learn more?The best place to learn more about launch is to attend one of our LIVE demos. You can get registered for one or view a past recording here - Ask the Community Expert: Launch by AdobeI've attended the demo, now what?It depends on your style of learning:I like to get in an get my hands dirtyIf you've got access to Launch, go ahead and login start using it. Use what you learned in the demo to create a web property, create libraries, deploy the library to a dev environment, and start playing with extensions and rules.A few resources you may want to have while you play around:Overview & General InformationDocumentation​BlogDeveloper Do

We have a few items that were released this month. A list of the highlights is below:Asynchronous deploymentRule OrderingUpdates to Data ElementsNew Rule ConditionsActive LibraryMore details and videos of each of the features can be found on the Spark storyFeature Updates for Launch, by Adobe