In my previous post, I started explaining what profile merge rules are. If you were expecting that in today’s post I documented how to configure it, I am still not there yet. I still need another building block: the declared IDs. With it, I will be in a position to show you how to proceed with profile merge rules.
Introduction to Profile Merge Rules
One of the most difficult features to understand in Adobe Audience Manager is profile merge rules. I thought of diving directly into the configuration, but first I want to explain what problem profile merge rules is trying to solve it and how it does it. Then I can move on to the code and, finally, the configuration.
Override Last-Touch Channel
My initial goal, when I wrote about attribution, was actually to talk about the configuration option named “Override Last-Touch Channel” in the Marketing Channels reports. However, I realised I needed an introduction to make it clearer and I wrote my previous post. Now I can go into the details of this technical feature and its consequences.
Some Thoughts on Attribution
During the EMEA Summit 2019, one Adobe customer asked me about one detail of the Marketing Channels configuration. The conversation we then had around this question, reminded me of the confusions some managers tend to have about attribution. Let me clarify a few things about this topic.
Site Speed and Adobe Tools
In a recent project I worked on, the client set a team up to analyse the site speed of the website. This resulted in some clashes between them and the Adobe team. Both sides had their own arguments and it was difficult to progress. Today I want to give you my point of view and tips of what you can do if you find yourself in the same situation.
A4T and Server-side Digital Marketing
In a client-side implementation, the JavaScript code takes care of Analytics for Target (A4T), so you do not have to do anything. However and as usual, in any server-side or hybrid implementation of Analytics and Target, A4T requires some additional care.
Hybrid Analytics
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.
Hybrid Target – Part 2
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.
Hybrid Target – Part 1
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.
Hybrid ECID
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.