Inconsistent JSON format (Offer vs. XF) when exporting AEM Experience Fragments to Adobe Target via Workflow

[developer0001]

Hi all,

I'm currently working on a customer implementation where Adobe Experience Manager (AEM) is integrated with Adobe Target. We have a workflow that automatically exports Experience Fragments (XFs) to Target in JSON format using the standard “Export to Adobe Target” process step provided in the workflow.

However, I’ve run into an inconsistency:

• Sometimes the exported payload appears in Target as a "JSON Offer"

• Other times, it appears as a "JSON XF" (Experience Fragment)

I’ve checked the workflow configuration and it’s always using the same OOTB process step (com.adobe.cq.target.integration.process.ExportExperienceFragmentToTargetProcess). I wasn’t able to identify what conditions or configurations lead to the difference in export type.

My questions are:

1. What exactly determines whether AEM exports an XF to Target as a JSON Offer vs. JSON XF?

2. Is there a setting in the Experience Fragment configuration or workflow metadata that drives this?

3. Has anyone else experienced this inconsistency, and how did you resolve it or enforce consistency?

4. Are there known bugs or version differences that affect this behavior?

We’re using AEM as a Cloud Service and the Target integration is done via Adobe IMS with appropriate Target workspace mappings. Any insights or pointers (documentation or experience) would be highly appreciated!

Thanks in advance.

[NarenKotipalli]

@developer0001I'm not entirely sure about the exact issue you're facing, but based on my understanding, the export format of the Experience Fragment (XF) depends on the Cloud Service Configuration applied to the XF’s root folder.

Could you please check the Properties of the XF or its parent folder and confirm that the correct Cloud Configuration is selected—particularly the "Export Format" setting?

Depending on this configuration, even when using the same workflow step, AEM may export the XF to Target in different ways:

• As a JSON Offer – when it's configured for JSON export.
• As a JSON XF – when the XF’s structural type is recognized by Target as a full Experience Fragment deliverable.

Verifying and standardizing this setting should help ensure consistent behavior during export.

Hope this helps!

Best,
Narendra

[developer0001]

Thanks for your response, Narendra.

I’ve double-checked the folder configuration, and it’s correctly set to JSON (not HTML or JSON & HTML).

However, I’m still seeing inconsistent behavior:

• In some cases, the exported payload shows up in Adobe Target as a "JSON Offer"

• In other cases, it appears as a "JSON XF" (Experience Fragment)

I’m trying to understand what factors determine this variation. Any further insights would be greatly appreciated.

[NarenKotipalli]

@developer0001Thanks for confirming the folder configuration, that’s a helpful detail.

To get a clearer picture of what might be causing the difference, could you share the exported payloads (or screenshots) for both cases from Target Offers?

• One where the Experience Fragment appears in Target as a JSON Offer
• And another where it shows up as a JSON XF

Also, are you seeing this inconsistency even when the content and structure of the XFs are the same? That would help determine whether the issue is related to the content itself or something else in the export process.

Once we can compare the two, it should be easier to pinpoint what’s driving the variation.

Happy to take a closer look once you have that!

Best,

Narendra