Articles by category: Platform

I have mentioned a few times the expression enable for profile, without explaining what it really meant and how to play with it. I wanted to document it a few months ago when I started writing more about the Adobe Experience Platform (AEP). However, as usual, I realised that I had to first explain some background before addressing this concept. This is what I have done in the past few posts, but now you should have all you need to understand it.

Creating an XMD schema does not also create storage for this schema. A schema is just a data model, not the data itself. To get the data in Adobe Experience Platform, you need to create datasets, which conform to schemas. In other words, the datasets are the storage where the ingested data is stored.

I had written this post a few months ago, but I realized that there were many topics that I needed to explain before I could finalize it. Now that you understand what the Experience Data Model (XDM), the AEP identities and the unified profile are, let’s see how all of these features are used together.

One of the first clarifications I need to make about Adobe Experience Platform (AEP) when I start working with a new client is that it is not your typical database. People are used to relational databases and NoSQL databases, so, naturally, they try to classify AEP into a known category. I would dare to say that CDPs should have their own category.

AEP stores a huge amount of structured data. Therefore, it makes sense that you can access that data in a way that resembles a database. In this post, I will show you a couple of ways to achieve it.

Now that you understand what the Experience Data Model (XDM) is, let’s move to another critical element of the AEP puzzle: identities. In theory, they look simple but, under the hood, they can become complex and difficult to manage.

If you are new to AEP, you will be trying to understand many new concepts. One of them is the Experience Data Model or XDM. This is one of the key components of AEP and you should understand it to master Adobe’s CDP. Since I also started scratching my head about this new concept when I first heard about it 3 years ago, I would like to use my learnings to help you understand it.

I remember being a bit nervous before my first AEP project. The tool seemed very complex and I had only received the training. Seeing what my coworkers were doing and the questions they had, meant that I saw myself as a noob. However, as I dived into it, it was not as difficult as I initially thought. Of course, it is not an easy tool but, once you get the hang of it, things start to make sense. I also received a lot of support from the experts. In this post, I want to share the approach that you should take in an ideal AEP project.

So you have finally decided to start a project with the AEP Web SDK and Adobe has provisioned it for you. There are now quite a few steps you need to take, so I will go one by one. While you could start in many places, I will start with the edge configuration.

The Adobe Experience Platform Web SDK was introduced some time ago. I do not remember exactly when, but I have not had the time to work with it until very recently. Now that I have finally started to get my hands dirty with it, I will start writing about it. However, before I get into the how, I want to start with the why and the what.

In part 1 of this series, I explained the reason why we need a new tool. To summarise, there was no solution in the market that could be used in digital marketing with a true 360-degree view of the customer. In this post, I will explain the main core components of the Adobe Experience Platform.

If you have been using Adobe Experience Cloud (AEC) tools lately, you will have heard more than a few times the new kid in town, the Adobe Experience Platform (AEP). I first heard about it 3 years ago, when it was just an initial idea. Now it is with us and I am sure many do not yet understand it.