My Targeting Configured Components are not displayed Viewing as Published | Community
Skip to main content
Level 2
September 20, 2019

My Targeting Configured Components are not displayed Viewing as Published

  • September 20, 2019
  • 3 replies
  • 22494 views

Hello everyone,

When I configure Targeting on a component its content is not being viewed as published. I am using AEM 6.5.

I have an experiment fragment and text component with Targeting set up:

When I see the page as published, it presents the following error:

[AT: Rendering mbox failed target-global-mbox : {status: "error", error: "unknown client code: ifactsolamericasptrsd"}]

This is my client code and I used it in my Cloud Service Target configuration:

Does anyone have a similar problem?

Do you think there is any configuration that I did not do?

Thanks,

Regards

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Adobe Employee
September 20, 2019

Can you check if you have applied the target configuration to the site?

Also, check if you have published the target configuration to publish instance.

Level 2
September 20, 2019

Hello, thanks for replying.

I applied Target as Cloud Service Configuration to the root of the site. And also for my experiences fragments.

About the experience fragments I'm using in targeting at page, they are published and exported to my Target instance. But they were exported as HTML Offer (I expected them to be exported as Experience Fragments Type, but I believe this is not the cause of the problem).

My problem still persists, do you believe that may be what I show you? Do you know why my experience fragments were exported as HTML Offer and not as Experience Fragment?

Thanks you for your support,

Regards

Adobe Employee
September 21, 2019

It seems that you are using new IMS to Target connection. The reason that XF exported as an HTML is a known limitation of the current implementation of IMS->Adobe IO -> Target connection. In order to be able to export to Target as XF you need to use an old (deprecated) way by employing a Target Classic account.

sunjot16
Adobe Employee
Adobe Employee
September 23, 2019

If you go to http://<host>:<port>/system/console/components on your publish, try stopping/starting the TargetedContentMangerImpl component manually.

josuev40522873
Level 2
November 8, 2019

Hello caio.moreira

I wonder if you can please help me:

1. How do you fix the specific issue with the clientcode error?

2. Were you able to fix the issue with the published version of the page?

Thanks in advance,

Level 2
January 16, 2020

Is anyone else facing similar issue? I am on aem 6.5 and i do not see the targeted result. I am using the IMS approach

March 27, 2020

AT: Rendering mbox failed target-global-mbox

 

Object { status: "error", error: "unknown client code: adobeapac37" }

I am using AEM + Target + IMS + IO with AEM 6.5.3