I am returning to my series of posts on Adobe Experience Platform (AEP), which I left a few months ago. We are at the last step, although it will take me a few posts to get into all the details I want to explain. The activation part of AEP is when we finally see the value of AEP, when we are finally using its results in our marketing efforts.
Sometimes I joke with my colleagues saying that, if I had to start again my career as a consultant, I would have chosen security as my area of expertise. I do not think that I would have liked it as much as my career at Adobe, but I know that I would have always been in demand. That being said, we all have to be very conscious of the security of everything we do, even in digital marketing. Let me explain why.
We made it again! With all the issues that we have faced due to the pandemic in the last three years, we have reached the end of 2022. At least I can say that this year has been better that the previous 2 years for several reasons.
If you have been involved in Adobe Experience Cloud implementations, at some point you probably have stumbled upon CNAMEs. If you have wondered what are these creatures and why they can be useful for your marketing goals, this post is for you.
As I said in the introduction to RTCDP B2B, marketing automation activities are very different in B2B compared to B2C. If there is one detail that I have found particularly difficult to understand in B2B, that is the data model. The first time you see it, it feels too complex, until you start to understand what it is all about. This post is an explanation of the AEP B2B schemas, using my own words. My goal is to help you understand this data model if you, like me not that long ago, have no clue about it. Any subject matter expert could write a dissertation on each schema. However, my goal in this post is to help newbies. If you find any error, let me know in the comments and I will fix it.
Although I have been 10 years at Adobe, during 9 of those years I had been oblivious to the business-to-business (B2B) world that lies out there. My customers had been from many different verticals: retail, telecom, banks, gambling, CPG… but all these cases were business-to-consumer (B2C). Last year I had my first encounter with a B2B customer; this year I have had two RTCDP B2B implementations. If you are a bit lost regarding the differences between B2B and B2C in the Adobe Experience Platform (AEP), this post is for you.
One of the main purposes of Adobe Experience Platform (AEP) is to create a 360-degree view of your customers. In more technical terms, this is what we call the unified profile. While this is a conceptually sound capability, there are certain cases when this unified profile could be wrong, with information from other profiles which should not be there.
Today I want to tackle an area that I rarely mention in this blog: digital transformation. I know, this is a very broad concept, with many ramifications and ways of implementing it. Every digital strategist has their idea of what it is, how to approach it and how to implement it. My goal today is just to introduce the three pillars of a digital transformation program: people, process and technology.
If you have been following my series on the Adobe Experience Platform (AEP), you should now have data ready to work with. If you have the RTCDP or AJO SKUs, you will now want to start communicating with your customers. For that, the next step is to segment your total population, which is what I will describe here.
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.
When people start working with Adobe tools, they are flooded with lots of new names, which are not always obvious. Or you start with one tool, but as you learn more, you start to get lost. This was my case, when I had to learn the rest of the Adobe Experience Cloud with a background of Adobe Analytics. If this is your case, keep on reading!
I have been a bit lazy and I have not addressed this topic for some time. I have read a few articles, but I was not sure what I wanted to write about. However, in the last few weeks, I have been involved in an initiative with a customer, where they are replacing their existing static data layer with an Event Driven Data Layer (EDDL). This has given me the final push I needed to learn it and decipher it for you.
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.
Those of us in the digital marketing industry use very liberally some concepts, taking for granted that everybody knows what they mean. Two of such concepts are “segments” and “audiences”. I have used them in my posts very often, without giving much thought to which word I use. I had a recent enablement session with a customer and I realised that I have never explained these terms.
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.
It has been a long journey, but here I am: in less than 1 week I will celebrate my 10th anniversary at Adobe. It has been an amazing journey, much better than what I thought 10 years ago. Without a doubt, it has been my best job ever. Not everything has been rosy, though. Let me summarize the positives and the negatives of these 10 years.
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.