When I attended my AAM training a few years ago, I remember I barely understood what I was explained. To me, it was all new. The technicalities were not that difficult, but when the trainers explained the business side, I stopped following the course; it was all gibberish to me. It took me a couple of years to get a reasonable understanding of the display advertising industry. Since then, colleagues and customers have asked me to explain them how this industry works, so I thought I would write a “display advertising introduction for dummies” post. I will omit a lot of parts and will simplify it. If you are well versed in this area, I suggest you skip this article, as it will not offer anything new to you. In fact, you may even know more than me!
The main functionality of the Adobe Admin Console is user management. If you have been using Adobe products for a while, you will remember when you had to create users in each tool. This is all changing and Adobe is moving to a centralised approach, where all user management is done in one single interface. Let’s see how.
The Adobe Admin Console is probably one of the least known sections of the Adobe Experience Cloud. In fact, the admin console is now its own product in the Adobe ecosystem, as it can potentially be used by more clouds. As most of you know, all products in the Experience Cloud come from acquisitions, which means that each product had its own administration section. However, Adobe is now investing in a single administration console for all of them and this is the result. Here you have an introduction to the Adobe Admin Console.
If you keep information about your customers, you need a database to store it. The first solution that probably comes to your mind is a CRM, but this is not the only option. As you know, Adobe does not offer a solution to store customer data, but there are many integration points between Adobe solutions and this database. Let’s see how to use your customer data in the Adobe ecosystem and some additional details to take into account.
Server-side integrations have many benefits, which I am not going to enumerate. If you can choose between server-side and client-side integrations, I would generally recommend server-side. However, there is always one drawback: debugging. You cannot see what happens between the servers. This is the case of the Adobe Target and Adobe Audience Manager integration. I have personally had to debug it a few times and this is how you can do it.
In large projects, one of the typical questions I get asked is: should we use one Adobe Marketing Cloud (AMC) or multiple? Unfortunately, there is no black or white answer here, but many shades of grey. However, in the end, you have to choose one option and this decisions is final. Let me share with you some tips to choose wisely.
In my previous post, I explained how to use Adobe Analytics in mobile apps, as there are many similarities between web and apps. However, there are very clear differences, like the fact that an app is installed in a mobile device and a web is not. This gives the SDK the opportunity to capture additional metrics and dimensions in what we call lifecycle metrics. You might also see them named as mobile metrics and dimensions.
After adding the app to Adobe Mobile Services and including the SDK in the mobile app project, the fun starts. Now you can start using the full power of the Adobe Experience Cloud in your app. Let’s start by capturing the user’s behaviour, so you can analyse it in Adobe Analytics. This is very similar to what a web analyst would do with the web.
In this fast-changing world we are living in, we tend to concentrate too much on the details and forget about the big picture. As, probably, many of you, I started by just thinking on how to solve the particular questions my customers had. One day, though, I had one of those enlightenment moments and I started to think in use cases instead. Let me explain you my journey until I realised how important the use cases are.