identify audiences across Adobe solutions so insights are taken from one solution can be applied in another.
Launch By Adobe allows marketers to manage tags, distribute data, and simplifies tag management.
Data Elements, Extensions, Rules and the Publishing process are the main aspects of Launch which you will use on a day-to-day basis.
Data Elements - Collect, organize, and deliver data across web-based marketing and advertising technology..
Extensions - “Tools” in DTM have been replaced by “Extensions”. While on the surface they will feel very similar, there are some subtle, yet extremely powerful differences to be aware of.
Launch is an open and extendable platform. Whereas the Activation team built all of the Adobe and 3rd-party Tools for DTM, Launch allows the Adobe solution teams and 3rd parties to build their own extensions. You can even create your own extensions and share them to the extension marketplace.
Think of Launch as the OS and extensions as the App Store. Extensions on the Launch platform allow Launch to evolve with the digital marketing landscape without Adobe bottlenecks.
Rules - Create robust rules that combine multiple events, sequenced in the way that you determine using if/then logic with conditions and exceptions. Extensions provide options for:
The rule builder includes real-time error checking and syntax highlighting for your custom code.
When the criteria outlined in your rules are met and conditions are satisfied, the actions you define are executed in order.
Publishing - The publishing process enables teams to publish code to pages. Different people can create an implementation, approve it, and publish it to your pages.
- Changes to your code are encapsulated within libraries you define
- You specify where and when you want your code deployed
- Multiple libraries can be built in parallel by different teams
- Unlimited development environments
- Deliberate, permissioned process for merging libraries together
Open APIs - Automate implementations of individual technologies, or a group of technologies.
- Launch interacts with the Reactor APIs
- Deployments can be automated through APIs
- Integrate the Launch APIs with your own internal systems
- You can build your own user interface, if desired
Light, Modular Container tag - The Launch container tag is 60% lighter than DTM and 40% lighter than Google Tag Manager. The content of your container is minified, including your custom code. Everything is modular. If you don't need an item, it is not included in your library. The result is an implementation that is fast and compact. See Minification.
Integrate Launch By Adobe with AEM so that you can use your Launch web properties to track AEM sites. Launch enables marketers to manage tags for collecting
Cloud Services - Digital Marketing cloud services are the AEM mechanism to configure integrations between AEM and cloud services such as Adobe Marketing
Launch is Adobe's next-generation tag management platform and the best way to deploy Adobe Analytics, Target, Audience Manager, Experience Cloud ID Service, and all of their 3rd party marketing solutions using Launch by Adobe.
Steps to follow before integrating Launch with AEM:
- Integrating with Adobe Analytics
- Integrating Adobe Analytics with AEM using Launch
Launch By Adobe is used load client library for Adobe Target. AEM synchronizes segments from Adobe Target
Integrate your AEM sites with Adobe Target to personalize content in your pages:Implement content targeting.Use Target audiences to create personalized experiences.Submit context data to Target when visitors interact with your pages.Track conversion rates.
When you target a component in AEM author, the component makes a series of server-side calls to Adobe Target to register the campaign, set up offers, and retrieve Adobe Target segments (if configured). No server-side calls are made from AEM publish to Adobe Target.
Integrating AEM with Adobe Target requires knowledge of Adobe Target, AEM Activities management, and AEM Audiences management. You should be familiar with the following information:
- Adobe Target (See the Adobe Target documentation).
- AEM Activities console (See Managing Activities).
- AEM Audiences (See Managing Audiences).
When working with Adobe Target, the following is the maximum number of artifacts allowed within a campaign:
- 50 locations
- 2,000 experiences
- 50 metrics
- 50 reporting segments
Author targeted content using Targeting mode of the AEM touch-optimized UI. Targeting mode and the Target component provide tools for creating content for experiences:
- Easily recognize the targeted content that is on the page. A dotted line forms a border around all targeted content.
- Select a brand and an activity to see the experiences.Add experiences to an activity or remove experiences.
- Perform A/B testing and convert winners (Adobe Target only).
- Add offers to an experience by creating offers or using offers from a library.
- Configure goals and monitor performance.Simulate the user experience.
- For more customization, configure the Target component.
- Activity - rule set defining which content is shown to which visitor
- Experiences - collection of offers, bound to an audience
- Offer - content to be shown in a location
- Audience - class of visitors defined by specific criteria
- Location - specific area on the page where content is targeted
|contexthub.kernel.js||The first include in your page header. This
loads the Context Hub base library
including the code for the stores.
|satelliteLib.js||The second include in your page template.
This loads the Launch library.
||This is the request that loads the data for
our donation store.
||This is the request made by the auto-
|These are the 2 targeted locations on our
The difference between the /ajax request for the global mbox and the /standard request for the targeted components is that we don’t expect content to be returned by the global mbox request. So we can send this as an asynchronous request that just sends the profile data required for the current user and then forget about it.
The targeted components and their mbox however are expected to return actual content to be displayed. In the lab setup we are using a synchronous request for the targeted components to make sure our page loads smoothly without any flicker. For the mbox managed by the targeted components this means that on the AEM publish instance we are using an mboxCreate call to define the mbox. But using synchronous requests can affect page load performance.
When inspecting the responses for the local mbox request you can see that AEM just synchs a JS snippet that takes care of loading the experience from AEM. This means the actual content stays in AEM and will be delivered from there, which allows to leverage AEMs powerful content aggregation and management
Experience Cloud Debugger Chrome Extension
The Experience Cloud Debugger is a Chrome Extension built by an Adobe.com developer. It contains basic debugging tools for all SaaS-based Experience Cloud Solutions, in addition to some very powerful and unique Target capabilities built by the Target Engineering Team. Add the extension from here:
Launch Command Chrome Extension
This is a new Extension built by the Launch BU to switch embed codes. Add the extension from here:
Browser Developer Tools
The tools above are both Chrome extensions. If you prefer to use a different browser, make sure you have Developer Tools installed (some browsers require a separate download).