Expand my Community achievements bar.

Never miss an update of the Adobe Journey Optimizer Community Lens! Subscribe now to get the latest updates, insights, and highlights delivered straight to your inbox every time a new edition drops.
SOLVED

Using Placement of Channel Type Email Content Type JSON in Journey Email Action content builder

Avatar

Level 1

I have built a Placement of Channel Type Email and Content Type JSON. I have added the placement to a couple of offers and populated them with some JSON. I then go into a Journey and add an Email Action and edit the content and edit the email body. I then try to add an Offer Decision and it asks we to pick a Placement but the Email JSON placement I configured is not available in the drop down list. Why is this?

 

The use case is that I want to create the offers as JSON that can then be rendered across the email because we refer to different parts of the offers across many different parts of the email.    

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@dmoorethree Currently, non-HTML content type offer placements are filtered out in email. Kindly log an enhancement for the same

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

@dmoorethree Currently, non-HTML content type offer placements are filtered out in email. Kindly log an enhancement for the same

Avatar

Employee Advisor

@dmoorethree 

Your Email + JSON placement is not showing up in the Offer Decision picker because JSON placements are not currently supported for AJO Email decisioning. The email designer only exposes email placements whose content type matches what the email channel knows how to render (HTML/text/image). JSON placements are supported for other channels (mobile, code‑based, content cards, etc.), but not as a first‑class placement type inside Email offers today.

bit advanced,  but to keep JSON, but render it via code-based / custom channel then pull into Email 

If you absolutely must keep true JSON and manipulate it as data:

  • Use a code-based experience or an external service to:
    • Take the JSON representation from the offer decision (for a JSON placement).
    • Transform it into ready‑to‑inject HTML snippets per “slot” in the email.
  • Then either:
    • Store the resulting HTML in profile/context attributes that the email can personalize on; or
    • Use a custom action in a Journey before the Email to fetch/compute HTML and reference that response