Adobe Experience Manager Sites & More

Umesh_Thakur · 11/5/23

Hi Team,

I need to export some experience fragment to adobe target as an offer. After integrating target with AEM I am able to push the xf to target but when I use those xf in any activity, created in traget, xfs are not visible in the entire container so I suspect this is happening due to <html> and <boyd> tag available in the exported xfs html.

When googling I find below community article which says some modification needs to be done on the xfpage structure component but when I refer

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

WKND demo site there was no su modification on the xfpage level but it still working fine in some of the community demo so can anyone please tell me whether it is really needed?

Thank

Umesh Thakur

kautuk_sahni · 12/5/23

@Umesh_Thakur

Yes, it is recommended to remove the <html> and <body> tags when exporting Experience Fragments (XFs) to Adobe Target. While these tags are not strictly required for XFs to work in Target, removing them can provide several benefits:

Improved Performance: Removing the <html> and <body> tags reduce the size of the exported XF code, which can lead to faster loading times and improved performance in Target.
Reduced Conflicts: The <html> and <body> tags can potentially introduce conflicts with the existing page structure in Target, which can cause rendering issues. Removing these tags eliminates this possibility.
Better Integration: Removing the <html> and <body> tags ensure that the XF content seamlessly integrates with the Target environment, avoiding potential inconsistencies or compatibility issues.
Simplified Configuration: Removing the <html> and <body> tags simplifies the configuration process for using XFs in Target, as there is no need to worry about potential conflicts or compatibility issues.
Consistent Behavior: Removing the <html> and <body> tags ensure that XFs behave consistently across different environments in AEM and Target.

Overall, removing the <html> and <body> tags is recommended for exporting XFs to Adobe Target, as it enhances performance, reduces conflicts, improves integration, simplifies configuration, and promotes consistent behavior.

Kautuk Sahni

View solution in original post

kautuk_sahni · 12/5/23

@Umesh_Thakur

Yes, it is recommended to remove the <html> and <body> tags when exporting Experience Fragments (XFs) to Adobe Target. While these tags are not strictly required for XFs to work in Target, removing them can provide several benefits:

Improved Performance: Removing the <html> and <body> tags reduce the size of the exported XF code, which can lead to faster loading times and improved performance in Target.
Reduced Conflicts: The <html> and <body> tags can potentially introduce conflicts with the existing page structure in Target, which can cause rendering issues. Removing these tags eliminates this possibility.
Better Integration: Removing the <html> and <body> tags ensure that the XF content seamlessly integrates with the Target environment, avoiding potential inconsistencies or compatibility issues.
Simplified Configuration: Removing the <html> and <body> tags simplifies the configuration process for using XFs in Target, as there is no need to worry about potential conflicts or compatibility issues.
Consistent Behavior: Removing the <html> and <body> tags ensure that XFs behave consistently across different environments in AEM and Target.

Overall, removing the <html> and <body> tags is recommended for exporting XFs to Adobe Target, as it enhances performance, reduces conflicts, improves integration, simplifies configuration, and promotes consistent behavior.