Adobe Journey Optimizer

Hi, I'd like to propose an enhancement to current Content template & Fragments by introducing Access level control Default Content templates & Fragments: These should be accessible only by admins or super users to prevent unauthorized modification. User-created templates & Fragments: Users can create templates/Fragments and have control over who can access or edit or delete them. Why is this feature important to you Improved governance - making sure critical or pre-approved templates/fragments are not unintentionally altered by non-admin or super usersUser control - Enables users to create templates tailored to their need without option to add restrictions. How would you like the feature to work -Add access level control similar based on role and user groupsIn UI user should have a drop down to choose who should have access - several roles can be assigned.Admin always have default access to assign or update permissionsUsers trying to access / modify

Description:Dynamic URLs generated from individual offer content are currently not being tracked for email click tracking, even though template language is used to create the tracking links. We need a solution to ensure these links are properly tracked. Why is this feature important to you:Accurate tracking of dynamic URLs is crucial for understanding customer engagement and measuring the effectiveness of email campaigns. Without this functionality, we lose valuable insights into user behavior and campaign performance. It also impacts decision-making and reporting accuracy. How would you like the feature to work:The system should support the tracking of dynamic URLs, ensuring all links generated using template language are automatically converted into trackable links. Additionally, it should provide a clear resolution path and guidance for implementation. Current Behaviour:Currently, dynamic URLs created from individual offer content are not tracked, despite using the te

Description:Introduce functionality to allow users to choose the placement of the tracking pixel, either at the top or bottom of emails, directly through the UI interface. This feature would enhance tracking accuracy and improve the overall user experience. Why is this feature important to you:The current placement of the tracking pixel at the bottom of emails limits the accuracy and speed of engagement tracking. Allowing placement at the top would address key challenges, including missed opens from recipients who don’t scroll through the email, delayed pixel loading in heavy-content emails, and inconsistencies across devices and email clients.Allowing the user to place the tracking pixel to the top of the email could bring several benefits, and we wanted to share why we believe this enhancement would add value: 1. Faster Engagement Tracking: A top-placed pixel activates as soon as the email is opened, providing immediate and accurate open-rate data. 2. Improved Metrics Reliabilit

It is important for a AJO user to be able to create both subscription lists and landing pages on there own. Today this feature is connected to a "high level" of user access, like site admin or site owner. In our daily work it is then difficult to test and use this where nice feature because it it not accessible. Could it be an idea to separate this accesses from the high level access that we need today to be able to use this feature. Then admin can keep there admin and owner rights and we can still use this feature when and as we like. 

When we run our daily batched to ingest data to AEP we know that many customers has the same e-mail address and/or Mobil number. There is several reasons for this. But it means also that this data points cant be the validator for a unique customer. This again is creating some issues reaching out to the right customer, it the contact data is duplicated.  Before customer data is ingested it would be nice it the system did a duplicate check  on e-mail and on mobile phone number, customers with one or several duplicates can then been flagged with a Attribute. We can then create Audiences on the customers with "error" in the contact data. This makes it easy to contact the customer in another cannel and inform the customer.  We see that this in many cases can happen when you have under 18 years customers, that needs to have there parents contact info. And when the older this is still the data connected to them. Or it can be man and wife. We need to be able to contact

Description - It is a new feature where global exit criteria introduced. we wanted this feature in our initial time itself. we wanted to reduce number of audience creation in many ways. this will help us to reduce the number of audience count as well. so, we need a attribute based filtering condition in the exit criteria not only audience and eventsWhy is this feature important to you - Already, we received the threshold of audience count and we are not using edge events, so custom event also we can't use much. we want to use this feature because we use to check "still a customer" etc.. So, we need this feature How would you like the feature to work - As we have restriction on creating number of audience why we use audience for an option which will increase the count instead, we can give attributes directly to use it for exit criteria. Current Behaviour - It allow us to use either custom event or audience based exit criteria 

Description - We need approval process in more detailed way instead of simple way like the current limited availability. We want to choose the approval policy during approval process or select the user directly from approval process. Why is this feature important to you - We have 4eye check in our organization where it will be assigned to specific person, it will record as log as well. so it is important for us.How would you like the feature to work - Expect to select the user directly during the request approval process instead of approval policy. otherwise, we need option to select the approval policy if we can create more than one in the backendCurrent Behaviour - Based on approval policy for a whole sandbox, it will process the approval process.   

Description -We use a specific naming convention for our Journeys and Messages.   Based on these, we can quickly determine if this is an offer or if it's an update.     We want to be able to cap the number of offers sent to a customer but not the number of updates sent.  As such, we need to be able to set the Caps based on our naming, not just if this is an marketing or transactional email.   Why is this feature important to you -We cannot scale decentralized marketing without these types of guardrails.   Current Behaviour -  can only cap based on marketing or transactional emails.

Description -In AEP/AJO we can see the events on the customer profile, however it would be beneficial to be able to see just summary of specific event types.  Why is this feature important to you -Need to see a summary of the customers email experience within the AJO tool. How would you like the feature to work -1) Either an additional tab, that shows all sent/delivered emails to a customer - with their open/click.  This would use the Journey & Message Name, with a link to view the journey. Current Behaviour -  only able to see a list of message feedback events in the profile, which does not include the journey names only the Journey IDs.  No Abiltiy to filter by event type, so just endless scrolling.

Description -Enable AJO to perform email content generation from a template without needing to also deliver this email directly, enabling use of the AJO templating when interfacing with third part APIs to deliver content. Why is this feature important to you -Lack of support for attachments in AJO means these emails must flow via a third party (eg InfoBip).  Having the option to generate email body content from templates using content fragments and conditional content would enable all our personalisation and content activities to remain within AJO but with the delivery and attachment handling handed off to a third party. How would you like the feature to work -A variant of the Email action should be available which generates email body content and stores it in a variable which can later be used in another action to pass to the third party API. Current Behaviour -Templates can be extracted from AJO by other platforms however this is the "raw" template with references

currently there is only way to subscribe to a subscription list via landing page.  Subscription list is a powerful feature that AJO offer but it's hindered by limiting it's ability only for landing page use cases. My suggestion it to enable the update activity in journey to use subscription list to subscribe from journey and also to have a history of tracking when a profile unsubscribed from list and when a profile subscribed, the trail will help us debugging and have a tracking details to help on prod issues like accidental un subscriptions from landing pages. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/landing-pages/subscription-list 

DescriptionWhen setting up transactional campaigns for sending out transactional emails containing contextual data, it is currently not possible to simulate the email with contextual data. That means that if a receipt is made up from contextual data points, we will have to simulate the final email by sending in API calls. That is an issue when changing something in an email that is already live, since our only option to test it is to then hope for the best, set it live and see how it looks. Instead we "could" copy the campaign to test an entirely new campaign, but that seems kind of overkill if we are simply aiming to making small adjustments to the live receipt.  Why is this feature important to youThe workflow of making changes to a live transactional email with contextual data and testing those changes is very heavy and time consuming. How would you like the feature to workWould like to be able to modify an existing live transactional campaign containing contextual da

We are missing some kind of feedback from the system after uploaded a list with the list upload feature. It would be nice to know how many rows has been uploaded (number of customers) had there been any rowns declined in the process, how many of the uploaded customer match a row in AJO. This is imported to know because we want to know if there is any ban data in the list, or if there of any reason is a mismatch between list and customers - and can then explore why. Today there is non feedback given. The feedback could be given in a popup or a report window after the import is done, and/or it can be sent be email. We have little or no control of what happens with the data vi import. 

To day we are facing a challenge with the audience threshold. Many audiences is created to be used in offers and Journeys in an AdHoc activity, and is not deleted and not set as inactive. Why is it like that, maybe because it is a to manual routine to remember from day to day. And it could also bee some amount of work if the activity is high every month - remember all audiences been used and who do inactivate or not. To save time and have better control over the audiences in use, and keep us under the threshold we have been looking for a new feature. What if there has been a possibility to set a "end data" when you create a audience (optional) . This date can then be set to be after your activity has ended, and the audiences that shall not be used anymore at this time is automatically set to inactive. This will save time for the users and it will save pressure in the system - by having more audiences in an inactive status. 

Description -In case we need to stop and restart journeys due to e.g. issues there are profiles which were left out. We need to find a way to process these profiles and get them included in the journey afterwards because they will not be selected by the audience anymore due to the chosen criterias.Why is this feature important to you -Otherwise we will miss profiles/customer in the journey and therefore the chance to contact them. This will crash their whole customer life cycle.How would you like the feature to work -Have the possibilty to include an audience as a kind of one time import.Current Behaviour -We need to create a copy of the journey with an adjusted audience and let it run only once. 

Description -We have several dashboards. We want to see aggregated report of campaign, journeys and failed jobs for all sandboxes in one page. Why is this feature important to you -For efficiencyHow would you like the feature to work -One dashboard what will show following information:1. Number of journeys per dashboards with nameLast execution of the Journey with number of persons selected2. Number of campaigns per dashboards with nameLast execution of the campaigns with number of persons selectedAll failed jobsCurrent Behavior: Only overview page of journey with limited option. It does not even option of selecting time. Furthermore, it is just per sandbox.  

Description - Please add the ability to add a superscript tag in the Text Block editor in the AJO Template Authoring tool. This will allow us to reference dislaimer copy in the fine print of the email up in the body without having to break the content block into a HTML block which loses all of the GUI flexibility of a test blockWhy is this feature important to you - We use this super script tag consistent i n all of our emails to reference fine print in the disclaimerHow would you like the feature to work - A tag selection in the style bar like the bold or italicCurrent Behaviour - there is no GUI support for Super script

Description -This ability to create an audience and exclude anyone with an email on the master suppression list Why is this feature important to you:Allows accurate counts for email campaigns  How would you like the feature to work:1) ability to create an audience that could be added as an exclusion OR exported for source system clean up.   Current Behaviour - Not possible.

In the reporting tool I would like to be able to see witch Live Journeys that has zero send out on a daily basis. We can then easily see witch Journeys that has no activity - and can probably bee closed or Archived. This mot be done manually since there can be Always on Journeys that in some days has count like zero. and that is normal. But this report can fast tell us what we can delete or archive - and save server resources..

Description - Expansion of Object Level Access Control (OLAC) to the type of campaign which can be created in Adobe Journey Optimizer Why is this feature important to you - End users creating campaign in AJO will have different surfaces which they can interface with and perform campaigns against. How would you like the feature to work - Ability to expand OLAC to include AJO > Campaigns > Code base, DM, EM, in App, Push, SMS, or web. Current Behaviour - Object Level Access Control (OLAC) only grants permissions to all types of campaigns.

Description - Ability to choose an attribute from a lookup table that has a relationship defined with profile attributes within data sources Why is this feature important to you - This will significantly reduce data storage size as the same information is not repeated in the underlying schema and data records, and enables more personalization flexibility when dealing with custom actions. How would you like the feature to work - Similar to the May 2024 Release,  allow for lookup tables to be configurable & retrievable in data sources, and can be used in advanced expressions & custom actions. Current Behaviour - Doesn't allow using lookup features.

Description - Given AJO developers that ability to quickly retarget profiles that were either mistakenly missed / went to the wrong path / errored out due to human errors like wrong rules set in conditions or vice versa, exclude customers who received xyz notifications from AJO already.  Why is this feature important to you - Human mistakes happen and teams often need to respond quickly to them. It would be super helpful to quickly identify those who were targeted, went to a specific path by mistake, or even exclude those who were targeted, so business can quickly recoup loss sales or communications. How would you like the feature to work - Some sort of querying / ability to define rules for retargeting Current Behaviour - It seems like building a segment and waiting 24 hours to be used is the only way, which often times marketing / leadership team is not happy with the wait time. 

Description Custom Action in a Journey that triggers a notification event     Why is this feature important to you When an email is sent to a specific audience group, I want to send a notification to the Sales rep (On customer profile0 immediately to set up a call or follow up action. The ability to create a custom action would be great.     How would you like the feature to work -I want to be able to build this custom action in AJO by our admin team so that users can drag this into a journey.  When a customer profile moves through the stages in the journey it will pass through this action, which will trigger a notification to a preset email.   Ideally when building the custom action, I would be able to set up the conditions that if Rep ID = X then sent corresponding Rep email address.  The notification could be a basic  email that lets rep know that customer with Customer ID has reached a specific stage&nb

For activation from a customer journey, policies can be applied to respect privacy and consent limitations. Currently policies cannot be applied to Offer Decisioning which means you have to include these limitations into Offer eligibility rules or decision parameters for example. It should be possible to apply policies to Offer Decisionig as it can be applied to other activations in Customer Journeys.Not being able to apply privacy and consent limitations as a policy for Offer Decisioning increases the risk of not being compliant.

In the customer profile UI there is currently no possibility to quickly check Offer Rankings or Decisions (for all active Offers). It should be possible in the customer profile UI to check the Ranking of Offers and results of Offer Decisionings.Operational efficiency when performing testing or investigation tasks required for a customer inquiry.