I am working on a use case where a user clicks on one of the three links on the page which is remembered in the cookies and we would then provide personalised content to the user based on the link he/she has clicked within the same session. We are using Launch and Adobe Target but don't have Audience Manager.
@anubhavs4404437 You dont need Audience Manager for your use case. I would recommend Audience Manager if you are onboarding user data from your internal data warehouses as an example or if you want to use data that flows into Adobe Analytics into Audience Manager. Theres more use cases but for this one you can I believe your main option is going to be passing this data as a parameter to Target in an mbox, ideally the global mbox since that is more commonly used and typically autogenerated. I am assuming that the cookie is set before taking the user to the page they are expecting to go to as a result of the click or that if the very next page is where they will be seeing the personalized experience that we will have the cookie value set prior to calling Adobe Target. Based on these assumptions and information you have provided here is my recommendation.
1. In Launch - Create a data element for the cookie where the value will be in.
2. In Launch - In the rule for Target, we should add the parameter and the data element name. Please take note of what you enter as the value as you will need this in Target.
3. In Target, create an activity using a custom audience that uses the "Custom" option drop down when creating the audience, you should enter for the name the same value that Launch is going to send to Target as a parameter. Then you set it to equal whatever you need it to equal.
4. To validate, you should be expecting the cookie to be set when you click the button, on the page where you want to see the activity you should see in the parameters to target the value being passed in and the activity being displayed.