Product Communities

Description - I would like to be able to append an unique coupon code/url link to an individual email. This would be a 1:1 append. Why is this feature important to you - My client has different retail partnerships they would like to send a coupon to as part of a "surprise and delight" or nurture program. How would you like the feature to work - I would like to be able to load the coupons into AEP and during deployment have AJO append a coupon to the email. Example, if I have an audience of 200K and 200K unique coupons, AJO would select a coupon, append to email  during deployment and "burning" the coupon once used.  Current Behaviour - Does not currently exist in AJO

OverviewThis change request proposes adding functionality to allow users to delete multiple journeys simultaneously from the Journey overview, with built-in dependency checks to prevent deletion of journeys in active states.Current BehaviorCurrently, users can select multiple journeys in the Journey overview (indicated by a blue line showing the number of selected items), but must delete journeys individually through each journey's ellipsis menu.Proposed ChangesEnable bulk deletion of multiple selected journeys through a single actionImplement/Keep as is - dependency checks to prevent deletion of "Published" (including "In review", "Dry Run") journeys. Only delete when status is Draft, Draft (Test), Finished or similar. Add a "Delete Selected" button that appears in the blue selection bar when multiple journeys are selectedDisplay a confirmation dialog showing:Number of journeys that will be deletedNumber of journeys that cannot be deleted (with their states)Option to proceed with

BackgroundAudiences currently tracks Audience lifecycle statusThere is no way to know when the lifecycle status was last changed or who changed itBusiness NeedTrack the timestamp when an Audience's lifecycle status changesTrack which user or system process made the lifecycle status changeEnable reporting and analysis based on status change dates and responsible partiesSupport accountability and audit trail for audience managementProposed SolutionAdd two new columns to the Audience table/entity:"Lifecycle Status Updated Date" - timestamp of the last status change"Lifecycle Status Changed By" - identifier of the user or system that made the changeConfigure both columns to automatically update whenever the lifecycle status field is modified:Date field: current timestampChanged By field: current user ID or system identifierMake these fields visible in the IU interface alongside the lifecycle statusInclude these fields in relevant reports, audit logs, and analytics viewsBenefitsComplete aud

Description -Why is this feature important to you - Client requirementHow would you like the feature to work - On the kanban board we want to show the details of checklist items or sub task which we added into the ticket can show on board itself along the with ticket name. So user no need to go inside the ticket everytime to see the checklist items and can mark complete from the board.Current Behaviour - We need to go inside of each ticket to get the details.

Today: Landingpages are used for opt out (unsubscribe) to emails. Link to this page is placed in a email fragment in the footer of all email. A standard way of doing this. When this link to this page is created in the email designer tool, it adds a landing-page-id to the link. This in a unique ID that need to be there present for the link to work. And here comes the challenge .... If you use a Sandbox for testing, that many do. We have all our email fragments present in the test Sandbox. And it you then have created links to a landingpage for opt out, that page does not exist in the test Sandbox, or the other way around.The problem:We are running into a problem either way we look at this. If we create the link to the opt out page from the test Sandbox, this will not work when moving the fragments to a Prod Sandbox. Or if the link is created in Prod it will not work in Test. The result of not having the right landingpage present in eighter Test or Prod we are not able to send

When moving email fragments from a test Sandbox to a prod Sandbox all Fragments are by default set to Draft when moved. And that is OK. But you need to go into one and one of the moved Fragments and publish them. It would be a faster and more easy way of working it we could select several fragments at once and publish them in one batch. That saves unnecessary repeatable work.  

I get an error in the Journey canvas about missing opt out link in the email body. Se attached image. This is not correct - since there is a opt out link present in a Footer fragment in the same template. The opt out link i coded in the fragment, and are present in the same way with the same ID-s that is needed for the link to work. But for some reason this manually coded link is not recognized as a out out link when AJO checks the code/template. Se picture of the code with the link. It would be nice if manually placed code also could be recognized when it is actually the same code that AJO is creating. This is an unnecessary error message that cases a lot of confusion.     

Please give us a savable filter for the Campaign list in Adobe Journey Optimizer. We will have a large number of users creating Campaigns and this list will grow very fast. So we need a way to focus the view of these users to what they should see when they look at the list. Great would be multiple savable filters and a DEFAULT option. So one of the saved filters is enabled when a user enters the page.

In Adobe Journey Optimizer Campaigns there is a feature checking if a mail has any issues or problems.  We would like to extend this functionality and make our own custom checks if a mail (or any other channel) fulfills our quality standards. This would include the following checks: - (profanity) word filter- image size- overall size- branding guides (fonts, colors, having color palettes or other brand related restrictions while content editing is also desirable…)- remove tracking pixel if no consent for tracking exists (we want to send to both with the same campaign, recipients that consented and those who didn’t)- check URLs- missing assets- when an audience is selected and we include personalization, let us know how many empty or ’invalid’ records for this personalization exist- audience checks before send (this could also become a part of approval process)- let us do audience count validations before sendout (final numbers, blacklist (suppression) subtracted, quarant

It is nice to be able to store/move and organize Fragments in a folder structure. But when you start to have many Fragments and you want to organize them, it is hard to know witch Fragments is in witch folder, and if a Fragment has been placed in a folder or not. So to be able to work faster and easier we would like to have a feature that could show the name of the folder where a Fragment is stored in the folder structure. It would/should then also be easy to see if a Fragment is still on Root, and has not been moved into any folder. This option would make it easier for the user to manage the Fragments in a folder structure. And with a increasing number of Fragments a fast and easy working process is needed to not spend to much time on administration that should be used on running you business. 

We are today able to use folders to structure our e-mail templates in a folder tree. The same folder tree is not visible then you are creating a new email and are picking a template from the customized stored. The folder structure should also bee visible when creating the emails, and not just when to administrate them. It is when you are looking for a specific template in the list of templates you really need the folder structure, and not from a administrative perspective. It seems a little meaningless to having a folder structure when the end user cant see it and use it - the one user that really need it to make the workday faster and easier. 

We are today able to use folders to structure our e-mail fragments in a folder tree. The same folder tree is not visible then you are creating a new email and are picking fragments from the customized fragments you have created earlier. The folder structure should also bee visible when creating the emails using fragments, and not just when to administrate them. It is when you are looking for a specific fragment in the list of all your fragments you really need the folder structure, and not from a administrative perspective. It seems a little meaningless to having a folder structure when the end user cant see it and use it - the one user that really need it to make the workday faster and easier, is the user that creates emails - where the fragments is actually been used. We would love if the folder structure became visible also when creating emails, from the email designer. 

When you are working with creating fragments or creating email templates you can store these in a folder structure. If you then go into the structure, open a template or fragment to make some changes and save when you then goes back in the GUI you start again from a "closed" folder structure. You dont come back to where you was in the structure. We would like the system to remember the folder you have open, and that you return to that folder after you have saved your changes to eighter a email template or a fragment (both where there is a folders structure created). Not go back to root, and you need to navigate again to find your "work" that you are working on.

Description - Add personalization (direct profile attributes and PQL functions) support to Offer custom attributes to be able to pull content from the attributes inside decision policy used in code-based channel. Why is this feature important to you/How would you like the feature to work - Only way to have content (with personalization) and offer (capping & eligibility etc) configured in one place i.e. in the offer item. Otherwise content need to be written directly in code-based channel personalization editor or in a separate content fragment resulting in long if/else conditions inside decision policy (when there are many offers in the collection used in the policy) that are not user friendly or easy to maintain. This way, business users would not need to touch the code-based channel editor, only the offers. Ideally, personalization code could be written in one custom field and called in another one for easier maintainability. Please refer to image attached. Current Beha