Community Ideas Update – H1 2025

Hey AJO Community! 

We’re excited to kick off a new initiative called Community Ideas Updates—a quarterly roundup that reflects our ongoing commitment to co-innovate with you. Your ideas aren’t just suggestions—they’re directly shaping the evolution of Adobe Journey Optimizer (AJO). Through these updates, we aim to provide clear visibility into how your voice translates into product direction and delivery, and ensure you see the impact of your feedback in action. 

We are starting with two quarters first so, here’s what’s been happening with your ideas in the first 2 quarters, i.e., 1^st January – 30^th June’ 25: 

Impact at a Glance 

• 39 ideas submitted by community members 
• 5% features delivered 
• 8% of those accepted as roadmap items
• 64% of those ideas are being investigated by the product team

Delivered Ideas – You Asked, We Built It! 

We’re thrilled to share that the following ideas have been delivered and are now part of the product. Huge shoutout to the community members who submitted these, your contributions made a real difference! 

• Folders for email fragments – submitted by Selliers
• Usage of the folder structure for landings pages – submitted by Selliers

Thank you for helping shape AJO! We love seeing your ideas come to life. 

Accepted Ideas – Hang Tight, It’s Coming! 

These ideas have been reviewed and accepted by the product team. They’re on the roadmap, and we’ll keep you posted as they move closer to delivery. 

• UI to create several test user – submitted by KarinKu
• System or AI mined alerts and guardrails – submitted by Caveman77
• Send Time Optimization - AJO Campaigns – submitted by montezh2001

Got thoughts or use cases to add? Drop a comment on the idea thread to help the team refine the implementation! 

Under Investigation – Stay Tuned! 

These ideas are currently being investigated. The product team is exploring feasibility, impact, and use cases. If you’ve submitted one of these, keep an eye out! You might hear directly from the team soon. 

• Object access control inheritance through folders or automatic assignment by current user groups – submitted byLuGeb
• Desktop and mobile friendly images when designing email content – submitted byLuGeb
• Schedule when to temporarily paus an active offer for a profile – submitted byMikael_Strangnefjord
• Ability to create an audience based on the the Journey or Campaign Name, not just the Journey ID and Message Name – submitted byCaveman77
• Smarter Search functions in AJO/AEP for audience and journeys – submitted byCaveman77
• 2step opt-out process for email unsubscribers – submitted byMarkus40235de
• Provide an option to fetch Batch Instance ID from journey properties attributes in expression editor – submitted byShashiCh
• Use user groups when locking content in email templates – submitted bySelliers
• View and edit conditional content in code mode when editing email content – submitted bySelliers
• Configure your email variables from the email preview window – submitted bySelliers
• Allow profile attributes for URL tracking parameters at channel config – submitted byKotiSyamala
• Deduplication Logic in Batch Deliveries – submitted bycalebhill
• Feedback form wizard using landing pages – submitted byKotiSyamala
• Add Audience Details to Send Logs in AJO Message Feedback Dataset – submitted byKotiSyamala
• Batch possibilities when deleting Email templates or archiving fragments – submitted bySelliers
• Update an existing email Fragment from a imported package – submitted bySelliers
• Centralized editing possibilities of the Head section in email templates – submitted bySelliers
• Creating condition on a whole fragment - on the fragment it self – submitted bySelliers
• Editing control working with email content and Journeys – submitted bySelliers
• Increase maximum number of nodes per journey – submitted by roisinm16195226
• Seedlist for Push delivery – submitted by FabianKramer
• Ignore capping -> frequency rules – submitted by Michael_Soprano
• Enable “Stop and Re-Publish” for Journeys in AJO Instead of Duplicating – submitted byAJODev
• Feature Request: API Access to “Copy Technical Details” JSON in Adobe Journey Optimizer – submitted bysanchesan
• AI-Powered Anomaly Detection in AJO for Real-Time Journey Health Monitoring – submitted byshefali_h_singh

Want to help these ideas gain traction? Add your vote or comment to share how it would help your workflows. 

Declined Ideas – Here’s Why 

Some ideas didn’t make it to the roadmap this time. We know this can be disappointing, so we’re sharing brief context to keep things transparent. 

• AJO API to Preview Email Template for a Given Profile – declined due to prioritisation as the product team does not currently have plans to offer this sort of API.  

Thank you for sharing these. Even if they weren’t picked up, they help us understand your needs better. 

Top Ideas to Show Love On 

Not every idea is accepted right away, but community support can make all the difference. Here are a few popular requests currently gathering momentum. Drop a comment, add your vote, or share your use case to help them gain visibility with the product team: 

• Exit criteria in journey based on customer attribute – Allowing customer attributes to serve as journey exit criteria, such as exiting when an attribute changes or meets a defined condition, would reduce reliance on audiences or custom events, streamlining setup and minimizing operational complexity.
• Ability to Organize AJO Campaigns in folders – With multiple brands and teams operating in a shared sandbox, organizing campaigns becomes challenging, introducing folder functionality for campaigns, similar to audiences, would greatly improve manageability and collaboration.
• Change scheduled time after Journey has been published – Users need the flexibility to adjust the schedule of a published journey, such as changing from 'As Soon As Possible' to 'Daily at 10 PM', without having to recreate the journey, which currently disrupts active profiles and adds operational overhead.
• save copy of the messages SMS/Push – Unlike email, SMS and push messages currently lack a way to retain a copy of the exact message sent to the end user. Introducing a temporary dataset to store these messages for export could support compliance needs for industries like banking and insurance.
• Possibility to use event data in computed attributes – Exploring the potential to use event data in computed attributes could unlock more dynamic rule-based audience creation, reducing reliance on streaming segments and overcoming current system limitations.

Your engagement matters. Let’s keep the momentum going! 

We’ll be back next quarter with more updates. Until then, keep those ideas coming and thank you for being such an incredible part of the AJO Community! 

Together, we’re shaping the future of AJO. 

Got an idea? Post it here!