AEM Personalization using Target

[test1234567]

Hello Community,

We are in the process of implementing an integration with Adobe Target. Our goal is to sync the segments from Target, which we are able to do successfully. My question is: if we personalize content in AEM for different audiences, how are the segments resolved? I understand that we need to call Target (using mbox and passing parameters if required), but I would like to confirm—based on the response from Target, is the content on the page updated accordingly?

For this implementation, we are not using any A/B testing or experience targeting from Target. We are only pulling the segments and authoring the content in AEM. I want to understand what role Adobe Target plays as an engine in this scenario. If anyone has implemented a similar setup, could you please share your experience or advice? Thank you.

[Umesh_Thakur]

Hi @test1234567,
When you are creating any activity directly in AEM with synced segment from Target, with the help of context hub, AEM used to show the personalise content on author instance but when you publish the personalised page then target comes into play based on how Target is configured for your site like thru launch but this kind of configuration can be used only on on-prem AEM instance as I was not able to find a way to do the same on AEM as CS.

I have seen many org. was using same kind of AEM- Traget integration with AEM on-prem as always there was some issue with browser compatibility with VEC of target and replacing component was rather easy in AEM.

Hope this helps

Umesh Thakur