Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM Campaigns to Adobe Target

Avatar

Avatar
Validate 1
Level 1
rami_el
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
rami_el
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
rami_el
Level 1

16-10-2015

Hello,

I'm trying to connect my AEM instance to Adobe Target. I have followed the instructions in this doc. The segments are synced from Adobe Target to my local AEM instance. However, when I create a new Campaign in AEM and add the Cloud Service Configuration to use Adobe Target, it doesn't sync back to Adobe Target. I was wondering if anyone has seen this problem before. (Using a vanilla AEM 6.1 Author Instance)

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 25
Employee
shekhardhiman
Employee

Likes

51 likes

Total Posts

688 posts

Correct Reply

330 solutions
Top badges earned
Give Back 25
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Give Back 25
Employee
shekhardhiman
Employee

Likes

51 likes

Total Posts

688 posts

Correct Reply

330 solutions
Top badges earned
Give Back 25
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
shekhardhiman
Employee

19-10-2015

Hi there,

Thanks for reaching out to Adobe Community.

As per my knowledge: 

  • The integration seems to leverage the API to Target Classic Workflow. 
  • The experiences and activities (campaigns) created in AEM show up in the Target Classic UI.
  • There seems to be a bug in AEM that prevents the integration from working when your author instance is not running on a dedicated port like 4502.
  • The integration will pull the segments from Target into AEM for use in a targeting scenario, but only segments that you have created yourself, not the ones that ship with Target. I haven't been actually able to get the personalization (based on Target segments) running in AEM. AFAIK AEM does not necessarily have  a concept of the Target (or MC) visitorID and of the visitor profile data stored inside Target.
  • As far as I know, you cannot preview / QA targeted experiences using the client context in AEM (or the persona settings on the top of the page in author mode – forgot what it is properly called.). So, there is no way to QA your targeted experiences right now.

Thanks!

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1
Level 1
Prateek_Agrawal
Level 1

Likes

0 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
Prateek_Agrawal
Level 1

Likes

0 likes

Total Posts

19 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
Prateek_Agrawal
Level 1

09-08-2016

rami_el wrote...

Hello,

I'm trying to connect my AEM instance to Adobe Target. I have followed the instructions in this doc. The segments are synced from Adobe Target to my local AEM instance. However, when I create a new Campaign in AEM and add the Cloud Service Configuration to use Adobe Target, it doesn't sync back to Adobe Target. I was wondering if anyone has seen this problem before. (Using a vanilla AEM 6.1 Author Instance)

 

Hi,

 

the same is not working for me? Neither on 4502 nor on any other port.

were you able to figure out the solution for the same?

If yes, then can you please share the same.

Thanks in Advance,

Prateek

Avatar

Avatar
Validate 1
Level 1
Lalit_Saini
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
Lalit_Saini
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
Lalit_Saini
Level 1

03-08-2016

+1 to Shekar's Solution

Apart from this there is one hotfix (Hotfix 6570) which you should install to fix Adobe target integration issues