Exporting experience fragment from AEM to Target | Community
Skip to main content
alissonxavier01
Level 3
Sep 20, 2019 5:42 PM UTC
Solved

Exporting experience fragment from AEM to Target

Hello Guys,

I am exporting experience fragment from AEM to Target.

However it is exporting like an HTML and doesn't experience fragment.

Does anyone a problem like that?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
leoberliantAccepted solution
Employee
Sep 21, 2019 3:46 PM UTC

It seems like 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.

View reply

10 replies

alissonxavier01Author
Level 3
Sep 23, 2019 5:10 PM UTC

Thanks guys.

It is working now.

Translate
alissonxavier27
Level 3
Sep 23, 2019 4:45 PM UTC

OK guys.

I requested a Classic Target account.

I am waiting for a response to my ticket.

I will inform you about the new steps.

Thanks

Translate
leoberliant
Employee
Sep 23, 2019 4:41 PM UTC

You need to request a Classic Target account from Target Support. AEM is still using a Classic Target API to connect to Target. By default, Classic Target Account is not assigned when Tagert is provisioned to an organization.

Translate
kautuk_sahni
kautuk_sahni
Employee
Sep 23, 2019 2:55 PM UTC

Adding to what Tanya shared, if in case you want to reach to Support of Experience Cloud solutions, please visit here[1].

[1] Adobe Experience League | Support

Translate
Kautuk Sahni
Shaheena_Sk
Level 4
Jul 30, 2020 6:14 AM UTC

Hi,

i was going through your video for integrating target with AEM through DTM. i am using AEM6.5 and i was able to make successful connection between DTM-Target-AEM. But, when i do "export to target" for my experience fragment. i get a pop up mentioning the page has missing target configuration. though i have configured the cloud service with the DTM configuration for that experience fragment.

does this imply that i cant use the button export to target if i m integrating through dtm?

Translate
kapila
Employee
Sep 23, 2019 2:51 PM UTC

Hi alissonxavier0105​,

Please connect with Target support team for Target Classic account. I recommend you to drop a mail to tt-support@adobe.com from registered user.

Translate
alissonxavier01Author
Level 3
Sep 23, 2019 12:54 PM UTC

Hi berliant​,

How can I get a Target Classic account?

Thanks

Translate
leoberliantAccepted solution
Employee
Sep 21, 2019 3:46 PM UTC

It seems like 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.

Translate
alissonxavier01Author
Level 3
Sep 20, 2019 6:38 PM UTC

Hi,

I did the steps like the document but I am using AEM 6.5.

Translate
Hamid1350
Employee
Sep 20, 2019 6:31 PM UTC

Check the relevant document to ensure you are not missing anything:

Target Integration with Experience Fragments

Translate
Terms & ConditionsAccessibility statement

Loading footer...