Highlighted

User identification and Adobe Target | AEM Community Blog Seeding

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

961

Correct Answer

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

961

Correct Answer

1.1K
kautuk_sahni
Community Manager

08-11-2020

BlogImage.jpg

User identification and Adobe Target by Pedromonjo

Abstract

A year ago I wrote about Declared IDs. I briefly mentioned then an issue that arises with setting these IDs: lazy loading and Adobe Target. However, I know that I did not explain too much about the issue. In this post I will get into more detail.


Order of execution
The typical order of execution of the Adobe tools on a page is as follows:
1. Request ECID on the first page of the first visit or read the stored value
2. Call Adobe Target
3. Apply changes to the DOM according to the response from Target
4. Call Adobe Analytics
5. Call Adobe Audience Manager or use server side forwarding.

Steps 1 & 2 must happen inside the HEAD section of the HTML page. Expect the unexpected if moved outside. Steps 4 & 5 can be moved to the very bottom of the page, just before the 

tag, although you could put them elsewhere in the HTML. Number 3 takes place automatically as the page loads. What happens when you have a declared ID? You are free to call Visitor.setCustomerIDs() (help page) at any point after step 1. All Adobe calls will use the declared ID after the previous JavaScript code executes. However, it is clear what will happen if you make the call after step 2: Target will not know about your declared ID. Why is this an issue? Read on…

Read Full Blog

User identification and Adobe Target

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager