Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Adobe Event Forwarding (formerly known as Adobe Launch)

Updated on October 4, 2022

Product Description

Adobe Event Forwarding is the new name for the Adobe Launch (server side extension) product that is part of Adobe Experience Platform.

Adobe's website for their Adobe Experience Platform Launch application leads with the following: "Great customer experiences require you to bring data and systems together. With Adobe Experience Platform Launch, you can connect multiple technologies and turn data into action — so you can deliver powerful, memorable experiences."

For more Adobe-specific information, see the Adobe website.

Integration Approach

The Pega Customer Decision Hub™ Event Forwarding connector captures and forwards streaming Adobe Event Forwarding data to Pega Customer Decision Hub. 

Pega Customer Decision Hub collects streaming data and insights from virtually any data source, including Adobe, and combines those data and insights with the customer’s current context to deliver next-best-action recommendations when needed. By using Pega applications, including Pega Customer Decision Hub, you can switch between selling, serving, retaining, and nurturing in real time, and quickly deploying new strategies to keep pace with ever-changing market conditions and customer demands.

By using the Pega Customer Decision Hub Event Forwarding connector, you can capture and forward specific data elements from the Adobe XDM data model to Pega Customer Decision Hub.

Extension configuration details

In Adobe Event Forwarding, configure the rule and the mapping of captured digital behavior events on your digital property to the expected behavioral data entities needed by Pega Customer Decision Hub. In the Data Mapping section, associate the Pega Customer Decision Hub clickstream event data entities with your collected data entities.

Components of Adobe Experience Platform Web SDK / Event Forwarding

  • Components
    • Adobe Experience Platform Web SDK, Mobile SDK.
    • Current and future direction for data collection for the Digital Experience products.
    • Adobe Experience Platform Edge Network.
    • Global distributed network provides a single consolidated SDK for every channel, which sends data to a common Adobe domain and receives a single payload back for data and experience delivery.
    • Adobe Experience Platform Launch Server Side - Event Forwarding.
  • Requirements
    • Adobe Experience Cloud Customer
    • Adobe Experience Platform Event Forwarding or DTM embed code on your web pages
  • Two ways to send events to non-Adobe destinations
    • Adobe Experience Platform Tags Client-side
    • Write Custom Js function in Web SDK Data Collection or build your own extensions
    • Adobe Experience Platform Event Forwarding Server-side
    • Use Adobe Cloud Connector Extension or build your own extensions
Adobe Data collection framework
Adobe Data collection framework

Adobe Experience Platform on the Client side

  • Prerequisites
    • Adobe Experience Platform Collection Enterprise
    • Map data to Experience Data Model (XDM)
    • Set up Adobe Experience Platform Edge Configuration
  • Configuration
    • Create a new Experience Platform client-side property. The Experience Platform client-side property collects digital assets such as domains, subdomains, websites, and applications.        
    • Copy and install the embed code from Client Properties > <Property> > Environments > <Dev | Stage | Prod> on your web pages.
    • Install and configure the Adobe Experience Platform Web SDK extension for the client-side property, then select the newly created Adobe Experience Platform Edge configuration file. Write a custom JavaScript function in the Data Collection section to convert XDM data to JSON, then write a custom JavaScript function to send events directly to Customer Decision Hub.
    • An extension is a packaged set of code that extends the Adobe Experience Platform Event Forwarding interface and the library functionality. 
    • Configure Client Properties > <Property> > Rules to define the events that need to be triggered on web pages, as well as the data that need to be collected using Web SDK and sent to the Adobe Experience Platform Edge Network. Enable the rule and then publish it.

Experience Platform on the server side

  • Prerequisites
    • Adobe Experience Platform Collection Enterprise
    • Access to Adobe Experience Platform Launch Server Side - Event Forwarding
    • Map data to Experience Data Model (XDM)
    • Adobe Experience Platform Web or Mobile SDK configured to send data to the Adobe Experience Platform Edge Network
  • Configuration
    • Create an Experience Platform Server Side property and an “Edge” platform type.
    • Configure Edge Network to send data to the Experience Platform Server Side property.
    • Install the Adobe Cloud Connector Serve Side extension that enables users to send data to non-Adobe destinations.
    • Create Experience Platform Server Side rules, and then configure the events sent to Customer Decision Hub by using Adobe Cloud Connector.

Pega Customer Decision Hub prerequisites for integration with Experience Platform

  • Prerequisites
    • Pega Customer Decision Hub and Pega Platform™ version 8.6 or later
    • Pega Customer Profiler Designer accelerator component installed
  • Configuration
    • Based on the client business, save the Customer Profiler Designer accelerator summary component (FSClickStream, HealthCareClickStream, InsuranceClickStream) into the CDH Implementation Rules ruleset.
    • In Customer Decision Hub, Click Data > Profile Data Sources > Summaries. Open the summary and then click Save.
    • In Customer Decision Hub, Click Data > Profile Designer. Associate the summaries that you want to use with specific customer contexts.
    • The CDH Clickstream Service endpoint URL (https://<host>/prweb/api/Clickstream/1.1/Insertis available to accept event JSON payloads from Adobe Experience Platform Launch.

Sample Financial Services Data Model events that you can map to Adobe Experience Platform Event Forwarding and Events

  • Events tracked for frequency: 
    • Web visits
    • Cards page visits
    • Deposit page visits
    • Mortgage page visits
    • Loan page visits
    • Investment page visits
    • Help page visits
    • Churn page visits (visits to pages correlated with churn risk)
    • Used branch locator
    • Home page visits
    • Accessed via mobile
    • Accessed via PC
  • Track average active minutes spent on:
    • Web pages 
    • Card pages 
    • Churn visits 
    • Deposit pages 
    • Help pages 
    • Investment pages 
    • Loan pages 
    • Mortgage pages 

The following figure shows the configuration screen of Adobe Experience Platform Event Forwarding and how various parameters and values can be shared:

Adobe Experience Platform Tags action configuration
Adobe Experience Platform Event Forwarding Action Configuration overview (example screen)

A high-level overview of an Integration: U+ Bank example

 The following figure shows a high-level overview of the integration between Pega Customer Decision Hub and Adobe Experience Platform Event Forwarding, using Uplus bank as an example:

1. Phil logs in to U+ Bank and shows interest in a credit card.

2. Phil's page view is detected by Adobe Launch Client Side (Tags); Adobe Web SDK sent an XDM event to the AEP edge network.

3. Edge is configured to forward the event to the Launch Server Side - Event Forwarding.

4. The Pega Customer Decision Hub Connector is installed and configured to send the clickstream event to Customer Decision Hub.

5.Using Customer Profile Designer, ClickStream is configured to update customer profiles based on the launch events.

Use case example - interplay between Adobe Tags and Pega Customer Decision Hub
Use case example; the interplay between Adobe Event Forwarding and Pega Customer Decision Hub

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us