Skip to main content
Jasbirka
Jasbirka
Level 5
April 27, 2026
Question

Can we use conditional content at the Fragment level?

  • April 27, 2026
  • 1 reply
  • 29 views

Hi Everyone,

Currently, we can only add conditional content (Dynamic Content) at the email level for fragments. Is there a possibility of implementing this functionality at the fragment level?

I am encountering an issue because I need to add variants at the email level, but I would prefer to use them at the fragment level.

This would allow me to utilize the fragments as Snippets in the old legacy editor, where segments are easily used at the snippet level.

Any help would be greatly appreciated.

Thanks!

      1 reply

      A
      akhil_merupula
      Level 3
      May 12, 2026

      Hi ​@Jasbirka ,

       

      Currently conditional content (Dynamic Content) at the fragment level is not natively supported in AJO the way you’re describing. The Dynamic Content conditions in AJO Email Designer apply at the email level, not within the fragment itself, which is exactly the limitation you’re hitting.


      That said there are a few workarounds depending on your specific use case.

       

      The first approach is using personalization expressions directly inside the fragment content. Instead of relying on Dynamic Content variants, you can embed inline conditional logic using AJO’s personalization syntax directly within the fragment’s text blocks or component properties. Something like an if/else expression that evaluates a profile attribute or context data and renders different content accordingly. This keeps the logic inside the fragment and means you don’t need to manage variants at the email level. The limitation is that it works well for text and attribute-level changes but gets harder to manage for structural layout differences.


      The second approach is creating multiple purpose-specific fragments one per variant and then controlling which fragment gets included at the email level using Dynamic Content on the fragment inclusion block itself. This feels counterintuitive but it keeps the fragment content clean and self-contained while still giving you variant control. The tradeoff is managing more fragments, but for reusable header or footer blocks this is often the cleanest long-term solution.

       

      The third option if you’re on ACC with the legacy editor context you mentioned the snippet-level segment approach you’re used to doesn’t have a direct equivalent in AJO fragments today. This is a known gap that several teams have raised. Worth submitting a feature request through your Adobe account team or the AJO product feedback channel since there’s clearly demand for it given how useful snippet-level conditions were in the legacy editor.


      Hope one of these helps bridge the gap in the meantime.

      Terms & ConditionsAccessibility statement

      Loading footer...