Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Adobe Summit 2023 [19th to 23rd March, Las Vegas and Virtual] | Complete AEM Session & Lab list

Solving Implementation Pain Points with Adobe Experience Platform Web SDK and Edge Network | AEM Community Blog Seeding

Avatar

Administrator

BlogImage.jpg

Solving Implementation Pain Points with Adobe Experience Platform Web SDK and Edge Network by Adobe Tech Blog - Jaemi Bremner

Abstract

The implementation of marketing technologies on a website can be complex. Data is coming and going, personalization content is retrieved and rendered, and identities and segments are synchronized.

As Adobe has grown its portfolio of marketing technologies, our technical complexity has grown with it. Many of Adobe Experience Cloud offerings were acquisitions. Each product had its own JavaScript library, its own server endpoint, its own database, and its own method for managing a visitor’s identity. We acknowledged that each Adobe product needed to be integrated with other Adobe products.
With Adobe Experience Platform, our goal is to reduce the complexity of implementing Adobe’s technologies on your website by creating a more unified experience. Early first steps included a unified JavaScript library, unified data, unified requests, unified server endpoints, and unified cookies.

Let’s take a look at some of the specific pain points we’ve heard from our customers and how Adobe Experience Platform Web SDK (a JavaScript library) and Adobe Experience Platform Edge Network (a network of servers with which the SDK interacts) seek to solve them.

Read Full Blog

Solving Implementation Pain Points with Adobe Experience Platform Web SDK and Edge Network

Q&A

Please use this thread to ask the related questions.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

0 Replies