A few weeks ago I heard of a conversation between Adobe and a customer about server-side implementations of web analytics and optimisation tools. In this case, the problem was that some vendor was misleading our customer. Well, actually, this vendor blatantly lied. I wanted to explain this situation so that none of my readers fall into this trap.
You all know that Adobe Analytics has an out-of-the-box solution to track download links. It just works and few people even care about it. You may not know that you can even extend its functionality, by adding additional eVars/props/events to the server call. Not very common, but I had to do it for one client. However, what happens when someone downloads content through a direct link or you have a server-side implementation?
Server-side Target seems to be a recurring topic. I have written a few times about it. However, I have been guilty of keeping the posts very technical. Lately, I have received more questions about it and I want to clarify some important, non-technical aspects from this type of implementation.
The last tool I showed in my Summit lab was Adobe Analytics. Initially, I was not sure whether I should write about it. However, I have come up with some ideas to share and here you have the final post on this lab.
With the Adobe Target server-side code code already step up, as I explained in part 1, we are now ready to move to the Adobe Target interface and configure it. I will show how to do it with an Experience Targeting activity, but it should work as well with an A/B test.
The next step after you have a hybrid ECID implementation is to do the same with Target. I already wrote a post on how to create a pure Adobe Target server-side implementation. Now I will explain how to create a hybrid implementation. This post will show the code and the next one, the Target configuration.
As I explained in my EMEA Summit lab, you should not use the ECID server-side if you are in a web environment. The solution I proposed was to use a hybrid approach. This means that the ECID must still be generated client-side, and then used server-side.
Last Thursday (16/05/2019) I delivered my very first lab at an Adobe Summit. I would like to thank all of you who attended. It went really well and many participants managed to do the full exercise. I have received many requests to publish the content or explain more. There is so much to explain, that I will write multiple posts in the coming weeks, to cover all aspects. Use the comments if you need more clarifications.
When, a few months time ago, I started writing the series of blog posts on Server-side digital marketing, I did not initially know what to expect. If the number of comments per post is a valid survey method, then I can now say that this series has been the most popular in my blog so far. I have even received internal requests from colleagues about this topic after reading one of these posts.
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.
Let’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.