I've some questions about Adobe Target.
The implementation that I'm looking for is:
I think I can create dynamic audiences with mbox parameters. But the question is how can I assign the users to that audience? Or is it already been done when the request to the mbox has met with custom parameter and the user is already created in that audience? Or should I not to have use Adobe Target at all?
I don't have Adobe Target instance yet, if this can be done I'll get one. So please can you explain how this can be done step by step.
Hi, In the scenario there is no need to assign users to the audience . Its done in real time. So if a user satisfies the conditions of the audience defined , there will be served the personalized experience .
Please refer to the below links for more information.
Please refer to section "In-page profile attributes (also called "in-mbox profile attributes)" in Methods to get Data into Target . This specifically talks about the use case related to Login information. So even if the user logged out, you can still capture the attribute in the visitor's profile so that it can be used for targeting later.
Yes, if the user deletes their cookies,then you are considered a new visitor and shown a new experience . Otherwise, say for example if you are using an XT activity for your personalization , users must meet the experience targeting rules on every impression to continue to see the experience's content. So as long as they meet the qualification criteria, they will be shown the same content on return visits .
Hope this helps.
Glad to have helped. If you have any new questions, please free to start a new thread and we will try our best to have them answered for you.
Thank you so much for your help. If I have futher questions I'm going to ask from here If you don't mind.
How about the user? Let's say I managed to personalize contents to different users. When a content personalized for an anonymous user, I think if the user closes the browser or delete the cookies, the experience will returned the default state, right? But that's not the issue for logged in users?