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

Not able to see exported XFs in Adobe Target

hagupta
Level 1
Level 1

We are trying to export XFs from AEM 6.4 to Adobe Target . We have integrated adobe target using Classic credentials method for which we already requested for target classic credentials and received the same.

Upon exporting an XF from aem, we are getting success message as well but the same is not present in Target under Offers.

Is there something we are missing ?

Thanks

2 Replies
Vaibhavi
Community Advisor
Community Advisor

Hi @hagupta ,

 

Though we get a success message, if the XF is not exported target due to some error, it will be loggged. Please have a check on the error.log  for the details.

 

Below is the prerequisite for the integration. Hope you have configured both.

  1. You have to integrate AEM with Target. See Integrating with Adobe Target for more information.
  2. Experience Fragments are exported from the author instance, so you need to Configure the Link Externalizer on the author instance to ensure that any links are externalized for the publish instance.

Please refer to below document for more details.

https://experienceleague.adobe.com/docs/experience-manager-64/administering/integration/experience-f...

 

hagupta
Level 1
Level 1

Thanks @Vaibhavi for your reply.

We have already configured the Externalizer service for author instance. I can see below logs in error.log

 

09.06.2021 01:48:10.831 *WARN* [10.75.29.86 [1623224890817] GET /content/experience-fragments/test/test3/master/_jcr_content/contexthub.commerce.orderhistory.json HTTP/1.1] org.apache.sling.scripting.sightly.js.impl.jsapi.ProxyAsyncScriptableFactory Script /libs/wcm/foundation/components/page/headlibs.js uses the deprecated asynchronous API provided by the 'granite' namespace. Please refactor the script to use the synchronous API provided by the org.apache.sling.scripting.javascript bundle.

09.06.2021 01:48:10.841 *WARN* [10.75.29.86 [1623224890817] GET /content/experience-fragments/test/test3/master/_jcr_content/contexthub.commerce.orderhistory.json HTTP/1.1] org.apache.sling.scripting.sightly.js.impl.jsapi.ProxyAsyncScriptableFactory Script /libs/wcm/foundation/components/page/body.js uses the deprecated asynchronous API provided by the 'granite' namespace. Please refactor the script to use the synchronous API provided by the org.apache.sling.scripting.javascript bundle.

09.06.2021 01:48:10.856 *WARN* [10.75.29.86 [1623224890817] GET /content/experience-fragments/test/test3/master/_jcr_content/contexthub.commerce.orderhistory.json HTTP/1.1] com.day.cq.wcm.msm.impl.LiveRelationshipManagerImpl StarResource given at /content/employee/en_us/errors/404/jcr:content/footerIPar/*: no parent: no LiveCopy

09.06.2021 01:48:10.870 *INFO* [qtp565643093-496864] reuest.log null

09.06.2021 01:48:11.211 *INFO* [qtp565643093-497090] reuest.log null

09.06.2021 01:48:11.556 *INFO* [qtp565643093-496864] reuest.log null

09.06.2021 01:48:11.815 *INFO* [qtp565643093-496180] reuest.log null

09.06.2021 01:48:12.160 *WARN* [10.75.29.86 [1623224892157] POST /libs/cq/experience-fragments/content/commons/targetexporter.html HTTP/1.1] org.apache.sling.engine.impl.request.RequestData SlingRequestProgressTracker not found in request attributes

09.06.2021 01:48:12.166 *WARN* [10.75.29.86 [1623224892157] POST /libs/cq/experience-fragments/content/commons/targetexporter.html HTTP/1.1] org.apache.sling.scripting.sightly.js.impl.jsapi.ProxyAsyncScriptableFactory Script /libs/wcm/foundation/components/page/head.js uses the deprecated asynchronous API provided by the 'granite' namespace. Please refactor the script to use the synchronous API provided by the org.apache.sling.scripting.javascript bundle.

09.06.2021 01:48:12.174 *WARN* [10.75.29.86 [1623224892157] POST /libs/cq/experience-fragments/content/commons/targetexporter.html HTTP/1.1] org.apache.sling.scripting.sightly.js.impl.jsapi.ProxyAsyncScriptableFactory Script /libs/wcm/foundation/components/page/headlibs.js uses the deprecated asynchronous API provided by the 'granite' namespace. Please refactor the script to use the synchronous API provided by the org.apache.sling.scripting.javascript bundle.

 

but these seems to be warnings only. Let me know your thoughts on this.

Thanks