Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

mariusvf
mariusvfLevel 2

API 2.0 Missing Feature Parity with 1.4 – Report Suite Configuration & eVar Metadata (Migration Blocker)New

 🧾 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.

Shubham-GoelAdobe Employee

Mastering Wave Sending in Adobe Journey Optimizer: A Practical GuideNew

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

EmilySo2Level 2

More proof notification optionsNew

Description:Currently, notifications for "replies to my comments" and "resolve comment" actions are grouped together in Adobe's notification system. This proposal suggests separating these two notification types to provide users with more granular control and clearer insight into the status of their commented items.Why is this feature important to you?Directly from a Designer on the team who gets a lot of these notifications: “Being able to turn off “comment resolved” notifications while still receiving immediate replies to proof comments would significantly improve my workflow and efficiency. I collaborate closely with my design team using proofs to provide edits, art direction, and feedback. As designers address those comments, they mark them resolved, which currently triggers notifications I don’t need. These updates clutter my inbox and make it harder to identify messages that actually require my attention. Resolving comments is an important part of the designers’ workflow for tracking progress, but it doesn’t require my involvement. Reducing these unnecessary notifications would help me stay focused and manage my email more effectively.”How would you like the feature to work?Ideally, the feature would introduce a distinct notification type for "comment resolved" actions, separate from the "replies to my comments."Current Behavior:Presently, both direct replies to a user's comment and actions where a comment they made is marked as "resolved" trigger a generic "replies to my comments" notification.

jwachAdobe Employee

Download Button for Sites page in AEMaaCSAccepted

Request for Feature Enhancement (RFE) Summary: Download Button for Sites page in AEMaaCS Use-case: This product enhancement request is to be able to download an image (pdf, gif, jpeg, etc.) from the preview page of a Sites page in AEMaaCS Sites. Current/Experienced Behavior: This is a requirement for larger multi-level organizations (in this case a large Adobe retail customer), which have Third Party & VPs/Executive leadership that do not normally access or do be granted access to go into AEMaaCS to view or approve a campaign. Thus, exporting the Site page from the preview page is a critical step in the approval process. Currently, there is no built-in functionality to download an image/PDG of a Sites page in AEMaaCS Sites. Improved/Expected Behavior: The scale of which the Adobe Retail customer plans to be creating emails and other marketing materials in AEMaaCS makes it unreasonable to go through a multi-step process in order download an image of a marketing component. There could be hundreds of emails/Sites pages that they are creating in AEM that would need pulled down and placed in to a document for leadership review. The system that the customer is currently using for email creation has this feature integrated in to the software. Moving to AEMaaCS and losing this functionality is a large area of concern for the creative team.   The easiest solve that the customer would hope to see as a product enhancement is to add a download button on the preview page of a Sites page (screenshot mock up image include). The addition of this one-step functionality would save countless hours of new work for the customer's creative team and parody the functionality that they currently have (before completely moving to AEMaaCS). It would make our transition to AEMaaCS easier, and would be a benefit to the customer's Executive team. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS, AEM Sites Customer-name/Organization name: DicksSporting Goods (DSG) Screenshot (if applicable):   Code package (if applicable):  

Deliver email to mailable people only when sending by time zonesNew

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.