Build better products with our product team
Currently, AJO does not include audience id in the Send Logs of the AJO Message Feedback dataset. This makes it difficult to analyze which specific audience groups are associated with a given campaign, track the effectiveness of messaging per audience segment, and integrate campaign performance data seamlessly with other Adobe Experience Platform (AEP) datasets. Why is this feature important to you?•Helps in measuring campaign success across different audience segments.•Enhances reporting and analytics by allowing segmentation-based performance tracking. Current Behavior•The AJO Message Feedback dataset provides logs for sent, delivered, opened, and clicked messages but does not contain audience segmentation details.
Description For an offer in the Decision Management, I would like to be able to configure how many times a profile should be able to see an offer during a chosen time period. It's already possible to set up a capping count and reset capping frequency but I would like to have an extra option for adding time periods when an active offer can be temporarily paused for a profile.Use case:Asking customers to fix their interest rate on their housing loan from a short time frame to 5 years.The offer capping is three and the reset frequency is monthly. After two months of showing this offer, the offer should be paused for 6 months, thereafter again showing to the customer with a capping of three times and two monthly resets. And so on... Why is this feature important to youWe have offers that are "always on" type of offers - not changing over years. However, we don't want to spam our customers with this type of offers and because of that we would like to have the option of a temporarily paus for any customer who has seen the offer for some time. How would you like the feature to work Add an extra option in the offer creation to be able to set a schedule for when the offer should be temporarily paused for an eligible customer that has seen the offer (capping) for some time (reset frequency).
I see when we add e-mail addresses or domains to the Allowed list under the E-mail settings we are not able to edit this after it is saved, and the description field is to short. You cant read the whole description text. It would be a good idea to be able to edit on a added "user" instead of deleting and adding the same person with a new address this is changed.
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 template language to generate tracking links. This results in incomplete data for email campaign performance and creates uncertainty about how to address this issue. PS: Here is a support ticket where aspects of the issue were discussed more in details:https://jira.corp.adobe.com/browse/PLATIR-36089
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 Reliability: Reduces the risk of missing opens from recipients who don’t scroll through the entire email. 3. Optimized User Experience: Ensures tracking accuracy even in emails with heavier content that might delay full loading. 4. Device and Client Consistency: Makes tracking more reliable across different email clients and devices, including those that truncate or partially load emails. How would you like the feature to work:The UI should include a simple option to select the desired tracking pixel placement (top or bottom). The system should automatically adjust the email structure to ensure proper pixel functionality, providing flexibility to suit diverse use cases. Current Behaviour:Currently, the tracking pixel is fixed at the bottom of emails, causing delays in engagement tracking, inaccuracies in open-rate data, and reduced reliability across different devices and email clients. This limitation impacts the effectiveness of performance insights and optimization efforts.
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 the right person. Ta make this easier for the end user it would there be nice to have a AJO report on witch customers that has a duplicate and give them and Attribute we can act on, straight and right out of the box.
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 -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 to content fragments and all special markup for conditional content. Only "simple" templates can be shared and used outside AJO making it simpler to move the templating to the other platform and simply pass across additional attributes such as segment membership to enable conditional content rendering within the other platform.
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
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.
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK