Implementing Adobe Target with Adobe Experience Platform Web SDK

Experience Platform Web SDK is a client-side JavaScript library that allows customers of Adobe Experience Cloud to interact with both Adobe applications and third-party services through the Adobe Experience Platform Edge Network.

There are 3 main Steps needed for implementing Adobe Target with AEP Web SDK:

1. Initial Configuration

2. Tag Configuration

3. Application Setup

We will dive deep into the first part, which focuses on the Initial Configuration. Stay tuned for the upcoming sections where we’ll explore the Tag Configuration and Application Setup to complete your understanding of this powerful integration.

1. Initial Configuration:

There are a few steps in the initial configuration

A. Configuration permissions:

To implement the Experience Platform Web SDK using tags in the Data Collection interface, it is important to have the necessary user permissions set up in the Admin Console

Also have permission to Develop, Edit, Approve, Publish, Manage Extensions, Manage Environments, and Manage Properties.

Experience Platform: These features are accessible to all Adobe Experience Cloud customers, irrespective of their usage of Platform-based applications like Real-Time CDP.

We need to access all these things

i. Default production i.e. prod.

ii. Manage Schemas and View Schemas under Data Modelling

iii. Manage Identity Namespaces and View Identity Namespaces under Identity Management

iv. Manage DataStream and View DataStream under Data Collection

v. If you are a customer of a Platform-based application:

Access to a development sandbox

All permission items under Data Management, and Profile management

For Adobe target configure permission we need the editor or approver access

B. Configure XDM schema

Learn how to create an XDM schema for web data in the Data Collection interface.

Experience Data Model (XDM) schemas are the building blocks, principles, and best practices for composing schemas in Adobe Experience Platform.

By utilizing the Platform Web SDK and your schema, you can effectively manage and streamline the flow of web event data within the Adobe Experience Cloud ecosystem.

Requirements

All necessary provisioning and user permissions for Data Collection and Adobe Experience Platform.

C. Create an XDM schema

XDM schemas provide a universal and conflict-free way to describe data in the Experience Platform. They allow data structures to be easily shared and reused across organizations, ensuring compatibility and consistency in data management.

Step to create a schema for the Luma website

1. Open the Data Collection interface

2. Make sure that you are in the correct sandbox

3. Go to Schemas in the left navigation

4. Select the Create Schema button on the top right

5. From the dropdown menu, select XDM Experience Event

Add fields group

As noted earlier, XDM is the core framework that standardizes customer experience data by providing common structures and definitions for use in downstream Adobe Experience Platform services. By adhering to XDM standards, all customer experience data can be incorporated into a common representation

1. In the Field Groups section, select Add

2. Search for AEP Web SDK Experience Event

3. Check the box

4. Search for Consumer Experience Event

5. Select Add field groups

Once you have selected the appropriate field groups, it’s time to give your schema a name. A widely used naming convention for XDM schemas is to name them after the source of the data they represent.

1. In the Composition panel, select the Untitled schema name

2. In the Schema properties panel, enter the Display Name Luma Web Event Data

3. Select anything outside of the Display Name field to activate the Save option

4. Select Save

When examining both field groups, you will observe that they provide access to the commonly used key-value pairs essential for web data collection. These pairs contain important information that marketers can utilize in the segment builder interface of Platform-based applications.

you can change the display name of standard fields to suit your needs. You can also remove fields you don’t want. When you click on either field group name, the interface highlights what key-value pair groupings belong to it. In the below example, you see what groups belong to Consumer Experience Event.

Creating your web events schema requires exploring and documenting your business requirements, like crafting a Business Requirements Document. This process involves understanding your organization’s needs and objectives to guide the schema development.

The identity Map object

To accurately identify web users, a specific data set known as an “identity map” is necessary.

D. Configure Identity Namespace

Discover how to set up identity namespaces for utilization with Adobe Experience Platform Web SDK.

The Adobe Experience Platform Identity Service establishes a unified visitor ID that seamlessly operates across all Adobe solutions. This empowers Experience Cloud functionalities, including audience-sharing across solutions. Additionally, you can transmit your own customer IDs to the Service to facilitate cross-device targeting and integrations with external systems, such as your Customer Relationship Management (CRM) platform.

Requirement

· Configure permissions

· Configure schema

Steps to create an identity namespace for luma CRM ID

1. Open the data collection interface

2. Select the sandbox you are using for the tutorial

3. Select Identities in the left navigation

4. Select Browse

5. Select Create Identity namespace

6. Provide details as follows and select Create

Field Value Display name- Luma CRM ID, Identity symbol- lumaCrmId, Type Cross-Device ID.

The Identity namespace populates in the Identities screen.

To overcome a limitation in the Web SDK extension, it is necessary to create identity namespaces in the production sandbox as well, even if you have been using a development sandbox for this tutorial. Specifically, you need to create the Luma CRM ID namespace in your production sandbox.

E. Configure DataStream

Data streams are responsible for directing the data collected by the Platform Web SDK to the Adobe Experience Platform Edge Network. Through the data stream configuration, you can enable your Experience Cloud applications, connect to your Experience Platform account, and set up event forwarding.

Requirements

Before you configure your DataStream, you must have already completed the following steps

· Configure permissions

· Configure schema

· Configure identity namespace

Steps to create a DataStream :

1. Open the data collection interface

2. Make sure that you are in the correct sandbox

3. Go to Data Streams in the left navigation

4. Select New DataStream on the right-hand side of the screen.

5. Enter Luma Web SDK as the Name. This name is referenced later when you configure the Web SDK extension in your tag property.

6. Select your Luma Web Event Data as the Event Schema

7. Select Save

Congratulations on completing the first part of our blog series on Implementing Adobe Target with Adobe Experience Platform Web SDK! In the next part, we’ll dive into Tag Configuration. Stay tuned for Part 2: Tag Configuration and level up your Adobe Experience Platform skills.

Click here to access Part 2 :- https://implementadobetarget.blogspot.com/2023/06/2-tag-configuration_21.html

and continue your journey towards adobe Target Implementation. Happy reading!