Adobe launch что это
In order to use the Launch API, each request must include the following authentication headers:
- Authorization: Bearer [TOKEN]
- x-api-key: [KEY]
- x-gw-ims-org-id: [ORG_ID]
This guide covers how to use the Adobe Developer Console to gather the values for each of these headers so you can start making calls to the Launch API.
Gain developer access to Adobe Experience Platform
Before you can generate authentication values for the Launch API, you must have developer access to Experience Platform. To gain developer access, follow the beginning steps in the Experience Platform authentication tutorial. Once you arrive at the step “Generate access credentials in Adobe Developer Console”, return to this tutorial to generate the credentials specific to Launch.
Generate access credentials
Using Adobe Developer Console, you must generate the following three access credentials:
Your IMS Organization’s ID ( [ORG_ID] ) and API key ( [KEY] ) only need to be generated once and can be reused in future API calls. However, your access token ( [TOKEN] ) is temporary and must be regenerated every 24 hours.
The steps for generating these values are covered in detail below.
One-time setup
Go to Adobe Developer Console and sign in with your Adobe ID. Next, follow the steps outlined in the tutorial on creating an empty project in the Developer Console documentation.
Once you have created a new project, click Add API on the Project Overview screen.
The Add an API screen appears. Select Experience Platform Launch API from the list of available APIs before clicking Next.
On the next screen, you are prompted to create a JSON Web Token (JWT) credential be either generating a new keypair or uploading your own public key. For this tutorial, select the Generate a key pair option, then select Generate keypair in the bottom-right corner.
The next screen confirms the keypair has successfully generated, and a compressed folder containing a public certificate and a private key is automatically downloaded to your machine. You will need this private key in a later step to generate an access token.
Select Next to continue.
The next screen prompts you to select the product profile(s) to associate with the API integration.
Product profiles are managed by your organization through the Adobe Admin Console, and contain specific sets of permissions for granular features in Adobe Experience Platform Launch. Product profiles and their permissions can only be managed by users with administrator privileges within your organization. If you are unsure which product profile(s) to select for the API, contact your administrator.
Select the desired product profile(s) from the list, then select Save configured API to complete the API registration.
Once the API has been added to the project, the project page reappears on the Experience Platform Launch API page. From here, scroll down to the Service Account (JWT) section, which provides the following access credentials that are required in all calls to the Launch API:
- CLIENT ID: The Client ID is the required [KEY] which must be provided in the x-api-key header.
- ORGANIZATION ID: The Organization ID is the [ORG_ID] value that must be used in the x-gw-ims-org-id header.
Authentication for each session
Now that you have your [KEY] and [ORG_ID] values, the final step is generating a [TOKEN] value.
Note that these tokens expire after 24 hours. If you are using this integration for an application, it is a good idea to obtain your bearer token programmatically from within your application.
You have two options to generate your access tokens, depending on your use case:
Generate access tokens manually
Open the private key you downloaded earlier in a text editor or browser and copy its contents. Then, navigate back to the Developer Console and paste the private key in the Generate access token section on the Launch API page for your project before selecting Generate Token.
A new access token is generated, and a button to copy the token to your clipboard is provided. This value is used for the required Authorization header, and must be provided in the format Bearer [TOKEN] .
Generate access tokens programmatically
If you are using your Launch integration for an application, you can programmatically generate access tokens through API requests. In order to accomplish this, you must obtain the following values:
- Client ID ( [KEY] )
- Client secret ( [CLIENT_SECRET] )
- A JSON Web Token ( [JWT] )
Your client ID and secret can be obtained from the main page for your project, as seen in the previous step.
To obtain your JWT credential, navigate to Service Account (JWT) in the left navigation, then select the Generate JWT tab. On this page, under Generate custom JWT, paste the contents of your private key into the provided textbox, then select Generate Token.
The generated JWT appears below once it has finished processing, along with a sample cURL command that you can use to test the token if you wish. Use the Copy button to copy the token to your clipboard.
Once you’ve gathered your credentials, you can integrate the API call below into your application in order to programmatically generate access tokens.
Request
The request must send a multipart/form-data payload, providing your authentication credentials as shown below:
Response
A successful response returns a new access token, as well as the number of seconds left until it expires.
Property | Description |
---|---|
access_token | The newly generated access token value. This value is used for the required Authorization header, and must be provided in the format Bearer [TOKEN] . |
expires_in | The remaining time until the token expires, in seconds. Once a token expires, a new one must be generated. |
Next steps
By following the steps in this tutorial, you should have a valid values for [ORG_ID] , [KEY] , and [TOKEN] . You can now test these values by using them in a simple cURL request to the Launch API.
Start by attempting to make an API call to list all companies.
Once you confirm that your access credentials are working, continue to explore the other API reference documentation to learn the API’s many capabilities.
You might already be using a free tag management system (TMS) such as Google Tag Manager to manage your marketing tags.
Have you heard about the free tag management system by Adobe?
Launch (or Adobe Experience Platform Launch) is a next-generation tag management system designed to unify data from multiple sources. It’s a rule-based TMS, which allows more control over each part of your tags.
Launch also offers extensions, a great feature to help you extend the platform based on your needs.
In this article, you will learn how to leverage your marketing solutions with Launch. The article covers:
- Launch’s main features
- The best extensions
- How to start working with Launch
- How to get Launch for free
Table of Contents
What is Adobe Launch?
Launch is the next generation of tag management system developed by Adobe. It’s an entirely new product with a new code base aimed to replace the previous Dynamic Tag Management (DTM) by Adobe.
Launch offers a simple way to deploy and manage your analytics, marketing and advertising tags.
Launch empowers anyone to build and maintain their own integrations with extensions.
You can easily install, configure and deploy new extensions. What else is great about Launch? It’s free!
An extension is a package of code (JavaScript, HTML, and CSS) that extends the Launch user interface and client functionality.
It enables you to build, manage and update your integrations using a self-service interface.
You can think of Launch as an operating system and extensions are the application you use to achieve your tasks.
All the extensions can be found within the Extension Catalog. Some extensions are provided by Adobe and offer integrations with other products of the Adobe Experience Cloud such as Adobe Analytics or Adobe Target.
It’s simple for you to deploy specific extensions that help you with your marketing activities.
And if you don’t find the perfect extension you can choose to extend the system and build your own.
Create robust rules with Rules Builder
Launch offers an excellent Rules Builder mechanism.
You can create rules that combine multiple events, sequenced in the way that you determine. Rules Builder uses an if/then logic with conditions and exceptions.
Here are some example of elements you can use to build a rule:
- Events: a click, a mouseover, any custom event
- Conditions: the trigger of your rule
- Exceptions: cases your rule must not be executed
- Actions: set variables, send requests, send conversion pixels, etc.
Rule Builder includes real-time error checking and syntax highlighting for custom code.
If you are a non-developer, this feature will save you time. It can check whether or not your tags or pixels will work and by that, prevent errors before publishing.
Data Elements
Data Elements are variables that collect, organise and deliver data across web-based marketing and advertising technology.
Launch is open
Launch has an open API that gives you plenty of freedom regarding automation and integration.
Here are some interesting use cases that you could implement thanks to the open API:
- Interaction with the Reactor APIs
- Automated deployment
- Integration with your own internal systems
- Develop a custom user interface
Launch, a lightweight tag management system
Web performance is key. Your web pages must be lean and load fast.
The Launch tag container is 60% lighter than Adobe DTM and 40% lighter than Google Tag Manager’s.
The content of your container is minified, including your custom code. Everything is modular. If you don’t need an item, it’s not included in your container. The result is a fast and compact implementation.
Looking for help with the integration of Launch in your marketing ecosystem?
An excellent publishing process
Enterprise Publishing is another highlight of (Adobe Experience Platform) Launch.
The publishing process enables your team to publish code to your webpages. Different users can create a version of the container, approve it, and publish it to your website.
What this means?
- Changes to your code are encapsulated within the libraries you define
- You specify where and when you want your code to be deployed
- Multiple libraries can be built in parallel by different teams
- Unlimited development environments
Launch, you next tag management system
Launch is a next-generation tag management system. The system, designed by Adobe, was released in 2018. It uses the latest technologies and on top of this, is designed for the needs of modern digital marketing.
You don’t have the excuse of cost anymore – Launch is free. And the best thing? You don’t have to be an Adobe Experience Cloud customer. Anybody can start using Launch.
Start using Launch today.
Patrick Psiuk
Analytics Expert
Would you like to receive the next article?
Subscribe to our newsletter and we will send you the next article about Adobe Experience Cloud.
Adobe Launch is an Adobe Experience Cloud core service and allows marketers to manage Adobe and third-party tags for tracking or other analytics purposes.
Adobe Launch provides a standard way to retrieve and use data, some of which comes from the back end. Adobe Launch has the ability to customize and respond to triggers that allow us to create action based on what visitors do. Because of the aforementioned capabilities, Adobe Launch is the perfect solution for managing first-party and third-party tags and extensions in one place.
Integrating Adobe Experience Manager with Adobe Launch allows you to manage all of your integration in one place. Adobe Launch acts as the centerpiece of your Adobe Experience Cloud implementation, providing access to Adobe Target, Adobe Analytics, Audience Manager, etc.
In this blog, we are going to explore the Adobe Launch integration with Adobe Experience Manager.
Configure Adobe Launch
- Login to the Adobe Experience Cloud and navigate to Adobe Launch.
2. Create a new property. A Property is a collection of rules, data elements, configured extensions, environments, and libraries. In Launch, you can create multiple web properties per company.
4. Click on the newly created property.
5. Click on the “Adapters” tab.
Default configuration is Managed by Adobe. This configuration make use of Akamai to host and deliver the Launch libraries.
6. Click on the “Environments” tab.
Staging, Development and Production environments are created by default. You can have as many Development environments, but only one Staging and one Production environment.
6. Click on the “Install” button.
7. Click on the “Data Elements” tab.
8. Create a new Data Element with the following definition:
9. Click on the “Extensions” tab and verify the Core Extension.
10. Click on the “Publishing” tab and publish the newly created Property and the Core Extension.
Set up Adobe IMS Service with Adobe Experience Manager
5. Select “New Integration” and click “Continue”
6. Provide a Name and Description for your integration
7. Navigate to your AEM Author Server
8. Go to Tools > Security > Adobe IMS Configuration
9. Click on “Create.”
10. Select Adobe Launch
11. Check the “Create New Certificate” checkbox
12. Specify an alias and click on “Create Certificate”
13. Download the Public Key
14. Go back to Adobe IO Console and upload the Public Key Certificate.
15. Select an appropriate role and click on “Create Integration”
16. Click on “Continue to Integration Details”
17. Navigate back to AEM Author and click the “Next” button
18. Specify a Title
19. Copy the API Key and Client Secret from Adobe I/O console and paste it in the IMS Configuration
20. Go to the JWT Tab in Adobe I/O console and copy the entire JWT Payload and paste it in the Payload text area field of IMS configuration
22. Click on “Create.”
23. To test, select the newly created configuration and click on “Check Health”
Integrate AEM with Adobe Launch
- On AEM Author, go to Tools > Cloud Services and Select Adobe Launch Configurations
2. Select We.Retail and click on “Create”
3. Specify a Title
4. Select the IMS Configuration from the drop down
5. Select the Experience Cloud Organization
6. Select your Adobe Launch Property
7. Click on “Next”
8. Verify the Staging URI, it should match the Library URI specified in Adobe Launch
Giving your users a great mobile experience means constantly evaluating how they are interacting with your app and quickly responding with updates and optimizations. Based on these guiding principles, we built Adobe Experience Platform Mobile SDK from the ground-up to be modular, flexible and dynamic. Managing mobile SDKs through Adobe Experience Platform Launch brings a host of new features and capabilities that enable you to better engage with your users with meaningful personalization.
Let’s take a look at some of the top features of the Adobe Experience Platform Mobile SDKs and how managing them with Launch can accelerate your mobile application development.
Adobe Experience Platform Mobile SDK can be implemented across a variety of platforms. For Android and iOS, we use dependency managers (CocoaPods and Gradle) to ensure that we pull the correct versions of the extensions and any necessary dependent files. We also support additional platforms such as React Native, Flutter and WeChat Mini Programs. Soon, we will have support for Apache Cordova, Xamarin, and Unity.
Thousands of companies and organizations already use Adobe Experience Platform Launch for website tag management and configuration. For mobile, Launch lets you create and manage mobile properties providing a familiar set of controls and workflow paradigms for managing app implementations. Getting started with Launch’s mobile workflows is easy. Activating Launch for mobile applications does not require its use on your website or vice versa (Figure 1).
Figure 1: The user interface in Adobe Experience Platform Launch now allows the user to select mobile applications as an option for creating a new property.
When you develop your application with the Adobe Experience Platform Mobile SDK, you retain a dynamic link back to your Adobe Experience Platform Launch property. Keeping this live link allows you to push configuration and resource updates to your application dynamically without requiring a developer to rebuild or resubmit a new version of the app each time.
Think about how many times you wished you had the ability to change an Adobe Analytics report suite or an Adobe Target client code but decided not to because it would require you to resubmit your application.
Launch also provides a publishing process that allows you to phase-gate your changes, first testing in development, staging and finally production (Figure 2).
The Mobile Core event hub lies at the heart of the Adobe Experience Platform Mobile SDK. The Mobile Core event hub provides the core data structure tied to all SDK extensions, maintaining a list of registered extensions and internal modules, a list of registered event listeners, and a shared state database.
The event hub publishes and receives event data from registered extensions to simplify integrations with Adobe and third-party solutions. Customers can also build private extensions to connect with internal business systems that they wish to integrate into mobile workflows.
Data elements in Adobe Experience Platform Launch act as aliases, making it easier to access data flowing through your mobile SDK implementation from both Adobe solutions and third-party extensions. Using data elements, customers can easily reference or use data as a workflow trigger, or condition. Data elements also make it easy to include mobile data such as context data, IDs, or anything else in post-backs to external endpoints (Figure 4).
Watch this video to learn more about how to create data elements in Adobe Experience Platform Launch:
One of the main benefits of using Adobe Experience Platform Launch to manage your mobile SDK implementation is the ability to create both simple and complex workflow rules. You can define what events and or conditions you want to trigger an action and then deploy these new rules to your application dynamically. Because your application maintains a live-link to your Launch environments you can easily add or modify rules depending on your needs.
To learn more about how rules work in Adobe Experience Platform Launch, check out the video below.
The icing on the cake is a brand new data and experience validation tool called “Project Griffon.” With Project Griffon, mobile app developers, product owners and marketers alike can easily understand how data is flowing through app implementations and how it is processed through Adobe Analytics.
With no need to create proxy networks, install profiles or certificates, Project Griffon accelerates mobile application development by creating a secure session through a QR code or deep-link that allows you to more quickly inspect, validate, debug data collection and experiences for your mobile app (Figure 5).
Project Griffon is in active development and is adding new features and enhancements at a rapid pace to not only help customers troubleshoot and validate experiences with Adobe solutions but to expand validation capabilities for our Adobe Exchange partners. Read more about Project Griffon here.
We’ve taken a lot of time to develop documentation to guide you through the use of these new tools. We continue to add information for our users including code snippets organized by platform, sample tutorials, and implementation articles. We have also developed documentation on best practices for migrating your mobile implementation from our v4 SDKs. If you are looking for an answer to a question and cannot find it in our documentation, make sure to shoot us a question in our community forums. Adobe Consulting Services are also available to help with all implementation needs.
Follow the Adobe Tech Blog for more customer and developer stories and resources, and check out Adobe Developers on Twitter for the latest news and developer products. Sign up here for future Adobe Experience Platform Meetups. For exclusive posts on Adobe Experience Platform, follow Jaemi Bremner.
Недавно я научился работать над Adobe Launch. Я хотел узнать на вкладке консоли на веб-странице, какие правила запускаются, а какие не выполняются. Я использовал запуск и DTM Switch, и это дало мне .
Отслеживание событий с помощью Adobe Launch
Я пытаюсь создать единое отслеживание событий (отправка формы) в сборе данных Adobe Experience Platform. Мне нужно видеть в Google Analytics количество пользователей, которые нажали на отправку .
как реализовать правила и события для отслеживания форм в Adobe Launch?
Я новичок в Adobe Analytics. Я пытаюсь отслеживать ошибки формы, которые возникают, когда пользователь отправляет форму, не заполнив обязательные поля. Итак, я передал значения формы в .
Как получить значение заголовка нажатой кнопки в Adobe Launch?
Я хотел бы использовать настраиваемый код элементов данных в Adobe Launch, чтобы получить текстовое значение для родительского элемента элемента, по которому щелкнули мышью. Я использовал $ ('h2.cmp-teaser__title.wow.animated'). Text (); метод, .
Adobe Launch: события GTAG (view_item и т. Д.)
Я борюсь с настройкой событий gtag ecom в Adobe Launch (тип тега пользовательского кода) для Google Ads. В основном я добавляю данные о событии в dataLayer (gtag ('event' . )), и ничего не происходит, по крайней мере, в .
Невозможно установить list2 в Adobe Launch в пользовательском коде
Я пытаюсь установить list2 в моем вызове аналитики с помощью специального кода, но он не настраивается. Эта проблема возникает только с s.tl (), тогда как с методом st () он запускается правильно. Ниже приведен код: - .
Как получить значения свойств для родительского элемента элемента, по которому щелкнули мышью, с помощью пользовательского кода в Adobe Launch?
Я хотел бы использовать настраиваемый код элементов данных в Adobe Launch, чтобы получить текстовое значение для родительского элемента элемента, по которому щелкнули мышью. Я использовал метод $ (this) .parents ('h3'). Text (), но когда я проверил .
Читайте также: