This is the last post on the server-side everything series, at least for now. While I prepared the material for this post, I realised an interesting fact. Adobe Target does not require a lot of technical knowledge, when used on websites. However, server-side Adobe Target is the most complicated of all server-side implementations. Let’s see why.
Until last Thursday, I had an idea of what would this week’s post was going to be about. However, on Friday, it all changed. I saw the internal presentation of Attribution IQ and I changed my mind. I know there are a few series I have not finished, but I think this is more important. But do not worry, I will resume my other series soon. Let’s dive into Attribution IQ!
It is not too uncommon that you need to have multiple tenants in the Adobe Experience Cloud. Although it was not explicitly designed to support this feature, it is possible to achieve it. I must admit it is not straight forward, but not difficult either. I will start with an introduction to multi-tenancy and, in future posts, I will explain the details for each solution.
We are all familiar with the client-side debugging tools, from the old DigitalPulse debugger to Charles. However, as Tim asked me some time ago, how do we debug server-side implementations? It is not always easy, but you have various options. Let’s explore them.
lLet’s continue with the server-side implementation of the Adobe SaaS solutions. The next is the list is Audience Manager. This is probably one of the simplest implementation of all solutions. However, beware of server-side Audience Manager: it might not be what you are looking for.
A few weeks ago I read a great blog post entitled The Era of Server-side Everything from my colleague Jan Exner. I wanted to write a comment, but as I started to think about what to write, I realised it was going to be too long. Instead, I decided I would write my own post on this topic. Then, as I started to think what I would include, additional blog posts came to my mind. So, this is the first of a series of posts on server-side digital marketing.
In my previous post, I introduced Adobe Sensei. Two of the examples I gave, of tools using this feature, were anomaly detection and contribution analysis. Last week one of my customers asked me about these features so I thought I would explain them in more detail in this blog.
I am sure you have been hearing a lot about Adobe Sensei lately. This technology was announced in November 2016, but only in the last few months it has become more mainstream. In summary, Adobe Sensei is Adobe’s approach to artificial intelligence. In this post, I would like to provide a brief introduction to this new Adobe offering. I am not an expert in these technologies, but if you have heard of these technologies and are wondering about them, this post will shed some light.