ÃÛ¶¹ÊÓÆµ

[Integration]{class="badge positive"}

Export Experience Fragment to ÃÛ¶¹ÊÓÆµ Target experience-fragment-target

[AEM Sites as a Cloud Service, AEM Sites 6.5]{class="badge informative"}

Learn how to export AEM Experience Fragment as ÃÛ¶¹ÊÓÆµ Target Offers.

video poster

Transcript

Hi there. In this video, let me show you how to export Experience Fragments created in ÃÛ¶¹ÊÓÆµ Experience Manager as a cloud service to ÃÛ¶¹ÊÓÆµ Target as HTML offer or JSON offer. The personalization team can then use the exported Experience Fragment offer in ÃÛ¶¹ÊÓÆµ Target to create an activity. I have an ÃÛ¶¹ÊÓÆµ Experience Manager as a cloud service instance set up for this video with the production, staging and development environment. Please make sure to use the latest build of AEM for your setup. So to publish an Experience Fragment to Target, there are few steps or prerequisites. AEM and ÃÛ¶¹ÊÓÆµ Target should be integrated using cloud services and the cloud service account should be added to your Experience Fragment before publishing. Secondly, you should also select the decide export format before publishing based on your use case. If not selected, estima format is selected by default. 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. From the AEM homepage, let’s navigate to Experience Fragments. How to create an Experience Fragment is out of scope for this video, hence, I have created an Experience Fragment with two variations. Let’s take a quick look at the Experience Fragment in Variations before exporting into to ÃÛ¶¹ÊÓÆµ Target.

From the Experience Fragment UI, select the WKND Adventure Experience Fragment to view its properties. From the cloud services tab, select the ÃÛ¶¹ÊÓÆµ Target solution and choose the cloud service configuration. Select the decide cloud service configuration and then choose the ÃÛ¶¹ÊÓÆµ Target export format. Select the ÃÛ¶¹ÊÓÆµ Target workspace and then pick the externalizer domain. Save and close the properties window. At this point, you have successfully added Target cloud service to your Experience Fragment and we are all set to publish and export the content. From the Experience Fragment UI, select the Experience Fragment and click on export to ÃÛ¶¹ÊÓÆµ target option. Make sure to publish the content before exporting. Open a new tab and navigate to ÃÛ¶¹ÊÓÆµ Target. Select Target Offer from the main navigation, and you should be able to view the Experience Fragment and its variations exported to ÃÛ¶¹ÊÓÆµ Targets as offers. Take a note off the offer type and the source for these offers. Let’s take a quick look at the offer properties for one of the variations. Under the offer info tab, you can view the offer content directly on a published instance or navigate to view the original content in AEM using the deep link. The personalization team can now use the exported Experience Fragment offer in ÃÛ¶¹ÊÓÆµ Target to create an activity. The ability to export the experience fragment as HTML or JSON offers helps content authors and marketers to create and deliver a personalized experience to a wide variety of channels. -

Next Steps

Troubleshooting

Exporting Experience Fragments to Target fails

Error

Exporting Experience Fragment to ÃÛ¶¹ÊÓÆµ Target without the correct permissions in ÃÛ¶¹ÊÓÆµ Admin Console, results in the following error on the AEM Author service:

Target API UI Error

… and the following log messages in the aemerror log:

Target API Console Error

Resolution

  1. Login to with administrative rights for the ÃÛ¶¹ÊÓÆµ Target Product Profile used but the AEM integration

  2. Select Products > ÃÛ¶¹ÊÓÆµ Target > Product Profile

  3. Under Integrations tab, select the integration for your AEM as a Cloud Service environment (same name as the ÃÛ¶¹ÊÓÆµ Developer project)

  4. Assign Editor or Approver role

    Target API Error

Adding the correct permission to your ÃÛ¶¹ÊÓÆµ Target integration should resolve this error.

recommendation-more-help
bb44cebf-d964-4e3c-b64e-ce882243fe4d