Build better products with our product team
We'd like to have the option to apply contouring (i.e. edit the distribution of the allocated hours per day/week/month) to tasks & issues in the "Unassigned Work" section of WLB. The UI would be the same as that in the Assigned Work section. A task's resource needs fluctuate during the span of the task and it is often known before a user is assigned but can't be captured via the Workload Balancer UI at the moment. This would make resource planning easier and more real-life.
🧾 Description We are currently migrating from Adobe Analytics API 1.4 to 2.0 and have identified critical gaps that prevent us from fully deprecating API 1.4. API 2.0 does not provide feature parity with 1.4 in terms of report suite configuration and variable metadata, which creates a blocker for automation, governance, and documentation use cases. 🚨 Key Gaps 1. Missing eVar Metadata The API 2.0 /dimensions endpoint does not return essential configuration fields such as: expiration_type expiration_custom_days merchandising_syntax allocation_type These fields were available in API 1.4 and are critical for: Automated documentation Data governance Attribution validation Migration verification 2. Missing Admin / Configuration Endpoints API 2.0 does not support: Creating or updating eVars, props, events Managing Marketing Channel rules Accessing or modifying Processing Rules Equivalent functionality existed in API 1.4 via ReportSuite.* endpoints. 🎯 Impact This is not a minor limitation — it is a migration blocker. We currently: Cannot fully migrate to API 2.0 Must continue using API 1.4 in parallel Lose visibility into critical configuration logic ✅ Requested Solution Option A (Preferred) Extend existing endpoints to include missing metadata fields. Option B Provide new endpoints for full report suite configuration management (parity with 1.4). 💬 Additional Context This is not a request for new functionality, but for feature parity with API 1.4, which is still required for enterprise use cases.
If you've ever launched a large-scale campaign and watched your call center buckle under a flood of responses — or worse, seen your email deliverability tank because ISPs flagged you for sending too much too fast — wave sending in Adobe Journey Optimizer (AJO) is the feature you need to know about.In this post, I'll walk through what wave sending is, when to use it, and how to configure it effectively for real-world scenarios.What Is Wave Sending?Wave sending lets you split a single campaign's audience into multiple batches (called "waves") and deliver them on a staggered schedule. Instead of blasting your entire audience at once, you control the pace — sending in 2 to 10 waves, each with its own size and timing.This applies to all outbound actions in AJO: Email, SMS, Push, and Direct Mail. Why Should You Care?Three words: control, reputation, and capacity.1. Protect Your Sender ReputationISPs watch your sending patterns closely. A sudden spike in volume from a domain or IP can trigger spam filters. Wave sending lets you spread delivery over hours or even days, keeping your sending profile consistent and trustworthy.2. Manage Downstream CapacityMarketing doesn't exist in a vacuum. If your SMS campaign drives calls to a support center, flooding 500,000 messages at once means thousands of simultaneous calls your team can't handle. Waves let you match outbound volume to your operational capacity.3. Ramp Up Safely on New InfrastructureMigrating to a new sending platform or warming up a new IP? Gradual volume increases are essential. Wave sending makes this easy — start with 10% of your audience, then 15%, then 25%, and scale up as your reputation builds. How to Configure ItSetting up wave sending takes just a few steps:Create or open an Action campaign with an outbound action (Email, SMS, Push, or Direct Mail). Navigate to the Schedule tab and enable "Deliver campaign actions in waves". Choose the number of waves (minimum 2, maximum 10). Pick your distribution strategy. Option A: Equal WavesThe simplest approach. AJO splits your audience into equal-sized groups. You set the first wave's start time and a fixed interval (e.g., 2 hours), and the system handles the rest.Example: 4 waves, 2-hour intervals, starting at 9:00 AM → waves fire at 9:00 AM, 11:00 AM, 1:00 PM, 3:00 PM.Option B: Custom DistributionNeed unequal splits? Define each wave's size as a percentage (must total 100%) or as absolute numbers (e.g., 10,000 per wave).This is ideal for ramp-up scenarios: Wave Size 1 10% 2 15% 3 25% 4 50% Option C: Custom ScheduleFull control — set a specific date and time for each wave independently. Waves don't need to be evenly spaced. The only constraint is a minimum 30-minute gap between wave starts.Example: Wave 1 at 9:00 AM, Wave 2 at 11:00 AM, Wave 3 at 5:00 PM, Wave 4 at 8:30 PM — useful when you want to align sends with different time zones or peak engagement hours. Real-World Scenarios Scenario 1: Call Center AlignmentA financial services company sends appointment reminder SMS messages. Their call center can handle 200 inbound calls per hour. They configure 5 waves of 1,000 messages each, spaced 1 hour apart, keeping response volume manageable.Scenario 2: Product Launch EmailA retail brand is launching a new product to 2 million subscribers. Instead of one massive send, they split into 4 equal waves over 8 hours. This protects deliverability and lets the marketing team monitor open rates and adjust subject lines between waves if needed.Scenario 3: IP Warm-UpAfter migrating to AJO, a media company uses custom distribution to gradually increase volume over their first week of sends:Day 1: 5,000 emailsDay 2: 15,000 emailsDay 3: 50,000 emailsDay 4: 150,000 emailsEach day's campaign uses wave sending to further spread the daily volume across morning and afternoon sends. Final ThoughtsWave sending is one of those features that separates a good campaign operation from a great one. It's not flashy, but it directly impacts deliverability, customer experience, and operational resilience. If you're running campaigns at any meaningful scale in AJO, this should be part of your standard playbook.Have questions or want to share how you're using wave sending? Drop a comment below — I'd love to hear your use cases.References: Adobe Journey Optimizer Documentation — Send Using Waves
As part of 23.2 release, the option to post a comment on each project during a batch update was removed. This is a feature that we used on a very regular basis for cleanups, etc. Please reinstate this feature!
Description -When you update a calculated field on a custom form, the change to the calculated field is not changed in other custom forms where the same field is used. The calculated field needs to get updated in each custom form it is used in. Workfront Support Response > "After speaking with my team and running some tests, this is currently working as designed, and why we recommend copying the calculation into the instructions of the field settings so they can be copied and pasted into the calculation after it is added to the new form. Currently, if you update the calculation in one form it will not carry over to another form where that field lives." REF: Case Number 00431554 Why is this feature important to you -Having to update a custom calculated field in multiple forms adds to the administrative burden and can lead to user error or inconsistencies in the calculated value across forms. How would you like the feature to work -Calculated fields should work like all other custom fields. Updates to the fields show be universal to all the forms it is used in.
!!NOT the same as being able to apply segment to calc. metrics!!Goal:Segment Visitors based on calculated metrics (such as AOV)Problem:Calculated metrics is NOT available in Segmentation console.
I would love to be able to filter a time off calendar on any team, rather than just on home team. We are an agency and our users are on many client “teams”, and sometimes a project manager may want to see all of the users that are out on a given client team rather than a given home team.
We have one app and several web properties tracked in abobe analytics. We use the LiveStream API to push our app and web data into an external repo. Mobile App ID is, in my opinion, the easiest and quickest way to segment out traffic to/within the app from the web properties.But Mobile App ID is not one of the fields sent in the Livestream API! Please do the engineering work to change that and include mobileappID in the livestream. You may be saying to yourself, now why don’t you just track them in separate report suites.. great question! I didn’t make the decision to combine them in the same suite - that predates my time here.
When exporting a large number of records with a large number of fields, Marketo will often complete the export, with a UI confirmation, but the download will not work. This appears to be a silent failure of the “download now” button. Sometimes large exports download without issue, and other times they don’t download, no matter how long you wait. The UI should provide an error or otherwise indicate when a download can be completed successfully.
Hello. When we use an Email Program with time-zone feature enabled, the smart list is calculated at the time of program launch / approval and the emails are sent to everyone at once. Then they are delivered by time zones even to those who has unsubscribed or has been marked as marketing suspended after the email was sent but before it was delivered (this period can be up to 24h long). The support team has advised that this behaviour is expected and as a fix we should adjust the messaging to “unsubscribe will be applied within 24 h”. I’d like to request a feature to prevent all non-mailable people from delivering a time-zone sent email, including unsubscribed, marketing suspended, email invalid or block listed. Reasoning:although legally we can protect ourselves with the 24h notice, this still creates a bad customer experience as often these emails are delivered just hours after the unsubscribe request. It can create a feeling of frustration and lead to reporting the sender as spam. among the suspended reasons, there are customer accounts who are going through deployment and either their customer success team or the account admin requested to pause all emails to avoid confusion among users. Delivering the email to them after the request has been processed also creates an unpleasant experience for the customer. lastly, when setting up monitoring campaigns to review that new exclusion approach works well, we had to review a lot of cases of emails being delivered due to the time-zone functionality as we couldn’t find an easy way to exclude such emails from the report. To sum up, current state: (1) Email is sent to the calculated smart list; (2) A person on the list unsubscribes; (3) The unsubscribed person receives the email.Desired state: (1) Email is sent to the calculated smart list; (2) A person on the list unsubscribes; (3) The unsubscribed person is either marked as bounced, or pending, or some other way to mark a non-delivered email.
In all Sandboxes, prod and test, we sometimes need to clean up the environment. Meaning f ex deleting old Journeys, not used Journeys and Journeys used for testing. Today it is only possible to delete Journeys one by one. It would be better if there where a option where you could select several Journeys and batch delete them with one click. Deleting one by one seems unnecessary and time consuming.
Just like we can delegate project/task/issue approvals, and with 22.3 can delegate task/issue assignments, PLEASE have the ability to delegate proof approvals! There are other ideas for this with 'Not Planned' labeled, hoping power in numbers can help sway this bc this is something WF really needs. Hoping it is part of near-future proof enhancements.
Description - Once an issue has been approved, we convert it into a project, and I would like to lock the comments (updates section) in my issues (nobody can enter a new comment) once it has a resolving project related to it. Why is this feature important to you - once the issue is approved, we follo up everything in the converted project but many time requestor does not know and he/she comment in the issue instead of the project this causes confusion in the Requestor because, he does not know that the latest updates are in the project or the executor do not see the comments because He is now working in the project. It results in lost the conversation chain and often gets missed. How would you like the feature to work - A feature where it detects the issue has a resolving project and lock any new comment. Current behaviour - only technical method to achieve this is by revoking users' sharing permissions from the issues. Yet, this action would result in users being unable to view or access the issue unless they possess system administrator privileges. We still need Requestor has access to the issue, but he should not be able to modify or comment it.
The Problem: Displaying inactive users creates a poor user experience when trying to confirm if object is shared or not. Currently, active users are mixed alphabetically with "No Access" or inactive users, forcing our team to scroll excessively and manually click the "X" to clean up share list. This manual maintenance is a time-sink, diverting our team from their primary goal: supporting our customers.Requested Enhancements: Collapsible or Hide "No Access" View: implement a collapsible section for users with no access, similar to how inherited permissions are handled. Users should have the "choice" to expand this list via a toggle (>) only when needed. Automated Team Offboarding: way to automate the removal of inactive users from Teams. Currently we either have to have team owner go and remove or our ops team need to go into the user and X all the teams they are tied to. Again takes away from our doing our day to day jobs. The Goal: Minimize administrative overhead so our team can focus on customer-facing tasks rather than manual permission management.
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