Leverage fragments in decision policies fragments

Simply copy-paste the code block below into the decision policy code. Replace variable with the fragment ID and placement with the fragment reference key:

{% let variable =  get(item._experience.decisioning.offeritem.contentReferencesMap, "placement").id %}
{{fragment id = variable required=false}}

1. Navigate to the Helper functions and add the Let function {% let variable = expression %} {{variable}} to the code pane, where you can declare the variable for your fragment.

   

2. Use the Map > Get function {%= get(map, string) %} to build your expression. The map is the fragment referenced in the decision item. The string can be the device model you entered in the decision item as the Fragment reference key.

   

3. You can also use a contextual attribute which would contain this device model ID.

   

4. Add the variable that you chose for your fragment as the fragment ID.

   

To insert AEM Content Fragment attributes into your email using a decision policy:

1. Open your email draft in the Email Designer and click the Decisioning icon in the right rail to open the decision policy panel.

2. Select the selection strategy you assembled and specify a placement to define the area of the email where the offer will populate.

3. Click the + icon and select the specific field from the AEM content fragment that should render in that area — for example, the hero image URL field.

   

4. Before publishing, click Simulate content to preview the result and verify that the highest-priority offer and its content fragment render as expected for a test profile.

When building a JSON-based code-based experience, use the following structure to render AEM Content Fragment attributes from a decision policy.

[
{{#each decisionPolicy.YOUR_POLICY_ID.items as |item|}}
{% let frag = get(item._experience.decisioning.offeritem.aemContentReferencesMap, "YOUR_REFERENCE_KEY").id %}
{{fragment id = frag result='YOUR_REFERENCE_KEY' required=false}}
{
  "fieldName": "{{{YOUR_REFERENCE_KEY.fieldName}}}"
},
{{/each}}
]

Keep the following in mind when building your JSON payload:

• Place the JSON array brackets [ and ] outside the #each loop.
• Use triple braces {{{ }}} for field values inside JSON strings to prevent HTML escaping of special characters and ensure valid JSON output.
• The result='YOUR_REFERENCE_KEY' parameter captures the resolved fragment content under that name so you can reference its fields with YOUR_REFERENCE_KEY.fieldName.

For HTML-based code-based experiences, use standard double braces for field rendering:

{{#each decisionPolicy.YOUR_POLICY_ID.items as |item|}}
{% let frag = get(item._experience.decisioning.offeritem.aemContentReferencesMap, "YOUR_REFERENCE_KEY").id %}
{{fragment id = frag result='YOUR_REFERENCE_KEY' required=false}}
<div>{{YOUR_REFERENCE_KEY.fieldName}}</div>
{{/each}}

1. From your AEM instance URL, identify the author domain — for example, author-p12345-e67890.adobeaemcloud.com.

   

2. Replace author with publish to obtain the publish domain: publish-p12345-e67890.adobeaemcloud.com.

3. In the Journey Optimizer personalization editor, prepend that publish domain to the asset reference field from the Content Fragment.

   

The image will now resolve to its full publish URL at delivery time.

1. Open your Content Fragment in AEM.

2. Go to the JSON preview and check the References section to locate the published asset URL.

   

3. Copy the publish URL and paste it into a dedicated text field within the Content Fragment.

   

4. In Journey Optimizer, reference that text field directly as the image source in your personalization expression.

   

This approach avoids manual URL construction and keeps the publish URL within the Content Fragment itself.