Build better products with our product team
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 Current Behaviour -Cannot find a solution for this in AJO, though all the capabilities described should be feasible within what the platform is capable of today.
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.
Description: We would like to define our own customer alerts in the UI for specific audiences and journeys.Why is this feature important to you: Due to lack of proper monitoring in AJO itself we often miss issues in audiences where they either increase or decrease quickly and we are then at the risk of sending campaigns to the wrong customers. As we're a big company, with many active segments, journeys and offers it's impossible for us to manually monitor everything all the time.How would you like the feature to work: We can define a custom alert which for selected segments (ex: A, B & D). At what % of discrepancy it should send an alert (ex. +/- 15%) and then an email is sent to a selected list of users X,Y,Z.Current Behaviour: There is no feature to have custom alerts for audiences.Extra bonus feature: If the alert could also include an automatic pause of any journey or offer that use the selected audience.
Currently we are using AJO email action to send out emails and we also have a custom action to log the AJO email activities through a custom action into a custom contact history table for our own reporting and tracking purposes. Right now we have to manually find the messageId for the specific email activity and enter that hardcoded value into the custom action configuration. This is time consuming. Also when we need to duplicate the journey, the messageId in the journey copy changes, and then we need to reconfigure it. Ideally, we would like to see messageId and other message related attributes such as messageName be variables in the interface we can pull in to use through custom actions. If there are multiple email messages in a journey, perhaps multiple email messageId available for pulling or at least the latest email messageId should be available.
We right now have a scenario where journey is used to debug AEP segment. AEP segment can often have a lot of targeting criteria. Often times when the count is off, it is very hard to pin point which criteria is causing the issue and which criteria there may be an underlying data issue. So a journey is created for this "waterfall count" purpose. It starts with a Read Segment that references the segment to be debugged and it is followed by a series of conditions and each condition is using a specific targeting criteria. After the journey is published, we can then see counts through journey reporting for each step. This type of journey we often need to run again and again. Currently we need to duplicate journey and rerun it after it first ran. So we ideally are seeking a solution to be able to run a journey again and again for this purpose without having to recreate a journey. Perhaps something like "test run/soft launch" that is different from the "publish" concept. And if the journey has components such as sending email or logging data - those steps will actually be disabled during the "test run". We currently do have "test mode", so perhaps need better naming etc so not to be confused with "test mode". Additionally, we are also pursing a separate AEP enhancement request to allow for segment debugging through perhaps AEP features.
Hi Team,We are not able to change the timezone when we are trying to schedule a campaign at a particular time and date.The timezone is being considered of the user and there is no option to change this in order to send a PN to the customers based on their local time. Sending a PN as per the customers local time zone is a feature available in the journeys but are not available in campaigns. Steps to reproduce: 1. Go to the AJO platform in the AEP dashboard.2. Click on Campaigns from the left side panel in the Journey Management List. 3. Click on create a new campaign 4. Click on Scheduled Push Notification Campaign 5. select the appropriate app surface6. Now click on create in the top right corner 7. Now scroll down and go to the Schedule section. 8. Select the on a specific date and time option in the schedule section 9. Try to change the time zone, and you won't be able to change it.
Description -Why is this feature important to you - currently we are seeing certain journey steps show up either multiple times or blank when we are querying for journey steps in a journey run and for more accurate reporting methods it would be great if this feature can be updated as it didn't use to be like thisHow would you like the feature to work - ideally features like a wait time should only show up once in a step event and the timeout branch should behave just like how any other node does.Current Behavior - As of now a wait time shows up twice when querying for journey step events (once for wait start and once for wait end) and time outs on an audience qualification have an additional blank node show up in step events for no reason.
Description -Why is this feature important to you - sending sms in weekend to client is really not acceptable , emails send during weekend are tend to be ignored How would you like the feature to work - i suggest to put this configuration on the surface of the sms/email then when you using this action on the journey , the message will wait until the first working day. i suggest like "outlook" , define global working days .Current Behaviour - for now , each time i need to spilt the action like this https://experienceleaguecommunities.adobe.com/t5/journey-optimizer-questions/send-emails-only-on-weekdays/m-p/606658#M602and i need to do it on every action on every journey this is very cumbersome and make the journey unreadable while if i have it on the surface level i can choose if this message will use that surface and avoid sending on weekends . then i can reuse this surface in all of my journeys but define it in one place. i would like to add also calendar with holidays to avoid sending messages too
Description:Not all clicks are equal value. I would like for clicks in an email to be classified as positive, neutral or negative. Why is this feature important to you: - Evaluating campaigns based on clicks, is now more important than opens as a metric to determine actual engagement. Quality of engagement is then unknown without looking at destination of clicks. How would you like the feature to work -Reporting on Positive clicks (Desired CTA) should be classified differently than Negative click (Unsubscribe/preference centre options), than Neutral clicks (Click on Company Logo). This would provide a better metric reporting within the tool in the dashboard. When tagging the email, I want to assign a value to the click. Current Behaviour -Not an option in the current model.
DescriptionLike many other marketing automation softwares out there, they come with some sort of functionality allowing you to generate a mirror page URL dynamically for specific deliveries sent to recipients / profiles. The means of doing so is not really important in my opinion, it is more the actual opportunity to do it that is important here. Why is this feature important to youLike many other businesses, we have a customer service department that are dealing a whole lot with questions like: "You just sent me this email, why is that" for instance. It has been really beneficial for us to allow the agent to actually look up the email and see a preview / mirror page of that email to increase the customer experience in that specific scenario. We are currently using Adobe Campaigns feature to generate a mirror page using the API's.var url = nms.delivery.GetMirrorURL(000000001,"00000002") How would you like the feature to workIn my opinion an api solution for this would be the way to go. So similar to ACC, but just using REST api framework to generate the URL. Current BehaviourCurrently not possible
Description - Add filters to audience section in AJO to have a better understanding of in which journeys the audiences are currently being used (in journeys in particular, but also destinations).Why is this feature important to you - This would be extremely helpful when it comes to organizing (and deleting) segments and to quickly see which audiences are currently in use (and used in which particular journey). Right now, we have to go through every single journey and document the audience being used.How would you like the feature to work - It would be great if there was a filter (or customize table option) of some sorts that would tell you the journey in which the audience is used. But destinations could also be added as well for example.Current Behaviour - This is currently not an option
During the discovery phase of the project, our company has stated that the banners/offers proposed to an actor/customer may vary in case the customer is at a certain stage of a given customer journey (also called digital experience). Our requirements state: - We want to make changes on priority or eligibility in banners depending on the phase of the digital experience the customer is in. Example: We want to promote banners Home1, Home3 and Home5 if customer is in stage - Near real-time requirements (this disables the Query Service option) - This could be applied to any customer experience that makes uses of the phases defined for our journeys This enhancement request is raised to get an out of the box integrated solution covering our needs. The (updates to) journey stages should be available to be used within Offer Decisioning Engine, ready for use in offer prioritization and eligibility. This should be available out of the box, without need to build a 3rd party backend
Currently when within an Offer Decisioning call deduplication is required between decision scopes a Round Robin principle is applied between scopes, meaning that every scope in turn gets an Offer assigned, even if the first scope in the decision requires two or more Offers. It should be possible to first return all Offers required for the first scope before turning to assigning Offers to the next scopes.Applying the Round Robin principle causes sub-optimal Offer assignments to scopes. An Offer with a higher priority gets assigned to the second scope in the decision instead of to the first scope. The order of the scopes in the decision is in that sense not respected.
Currently Offer Decisioning context parameters cannot be used to personalize content. It should be possible to use Offer Decisioning context parameters in content personalization.In some cases we want to differentiate content based on context parameters of the Offer Decisioning Request. E.g. language parameter : customers can use our apps in a language that differs from the language known in their profile, we want to propose content in the language that they are using the app in. We must avoid having content in a different language from the language the app is used in.
Currently the language parameter in the content definition screen is not of any use. It is not possible to have more than one content per Offer per Placement, even if they are in a different language. So content differentiation on language needs to be done through if statements in the same single JSON per Placement. It should be possible to define a content per Placement per language.We need to have the same content always in two languages, Dutch and French. It would be most logic to be able to indicate in the language parameter in which language the content is defined. Now this language parameter is not of any use in the content definition screen. Adding the possibility to define a content per Placement per language would also simplify the JSON definition of the content because additional if statements can be avoided.
Currently Offer Decisionig Simulations via UI can only be executed for customers flagged as 'test' customers. It should be possible to execute Offer Decisionig Simulations via UI for all customers without having impact on for example capping parameters. It should be posible to execute an Offer Decisioning request and seeing the result without impactig customer profile, this means as a real 'simulation' via UI (not realistic call).There is no way in the UI to check a customers' eligibility or Offer scores for specific Offers. In case of complaints or inquiries on what Offers a customer sees, we need to be able to simulate the customers' situation without impactig it to understand what is happening. This means not influencing the future behaviour of the Offer Decisioning for the customer itself. E.g. A customer should not reach the capping of an Offer because we simulated the behaviour of the Offer Decsisioning for him or her.
Currently there is no UI support at all for writing Ranking expressions (no operator suggestions, no profile attributes lists, no offer attributes lists, …). It should be possible to get some UI support when writing Ranking expressions.Avoid having to know all eperators and all profile and offer variable names by haert to more easily develop Ranking expressions.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
