2026 release notes 2026-release

You can now manage offers end-to-end directly from the Campaign Web User Interface. Configure offer environments and offer spaces, build your offer catalog and categories, create offers with eligibility rules and priority weights, and approve and deploy them for use in your deliveries. Advanced configurations remain available in the Client Console.

For more information, refer to the detailed documentation.

Technical administrators can now create and configure brands directly from the Campaign Web User Interface, without using the Client Console. All brand settings, including identity, subdomain and protocols, email header parameters, and URL tracking parameters, are now available in the Web UI.

For more information, refer to the detailed documentation.

When adding images to your emails, you can now select public resources. This allows you to choose an image already available on your Adobe Campaign instance, such as a file previously imported in the Email Designer or a public resource uploaded from the Client Console.

For more information, refer to the detailed documentation.

The Data loading (RDBMS) activity is now available in the Campaign Web User Interface. Use this activity to load data directly from an external relational database into your workflow. The extracted data is available throughout the workflow and can be used for targeting, enrichment, or further data processing.

For more information, refer to the detailed documentation.

Dynamic JavaScript pages (JSSP) let you build server-side pages that generate dynamic content when accessed through a URL, such as custom APIs, exports, or web application logic. You can now create, modify, duplicate, and delete these pages directly from the Campaign Web User Interface.

For more information, refer to the detailed documentation.

The schema authoring feature is now available to all customers (GA). This capability allows you to create and manage schemas directly from the Campaign Web User Interface. You can create new tables, extend existing schemas and create custom forms. You can define custom data structures to support your specific business needs without requiring access to the Client Console.

For more information, refer to the detailed documentation.

Themes provide an improved authoring experience for emails by allowing you to define reusable theme styles that fit your brand guidelines. You can now use theme variables in fragments, ensuring consistent styling across your email templates. This feature enables you to build emails faster with predefined modules that abstract content elements such as titles, descriptions, images, and links, while maintaining brand consistency.

Note: this capability is only available for a set of organizations (Limited Availability), and will be rolled out globally in a future release.

For more information, refer to the detailed documentation.

Enable seamless integration of standard and custom Firefly models, along with approved third-party image models, to provide greater flexibility, control, and brand alignment when generating images.

Choose the right model for your needs:

• Adobe model (powered by Firefly Image Model 4) for immediate image generation without additional setup
• Partner model (powered by Gemini 2.5 Flash) for specialized capabilities
• Custom models (brand-specific models trained on your own assets) for on-brand generation that aligns precisely with your brand identity, style, and visual guidelines.

For more information, refer to the detailed documentation.

The Automated delivery workflow activity is now available in the workflow palette. You can use it to create or execute delivery actions (prepare, send a proof, prepare and start, etc.) directly within your workflow. Select an existing delivery created outside the workflow to reuse it on every run, or create a new delivery from a template each time the activity executes.

For more information, refer to detailed documentation.

Multiple branches are now supported. Instead of using a Fork, you can click Add branch on the toolbar. The AND-join activity has also been improved. It is now a generic Join activity that lets you choose between AND and OR join options.

For more information, refer to Orchestrate activities and Join documentation pages.

The campaign inventory now includes a Timeline view that lets you visualize and manage campaigns over time: switch between list and timeline, navigate by week, month, or day, use the Today button to jump to the current date, and open campaign details (status, workflows, deliveries) in a right-hand panel—with the same filters and search as the list view.

For more information, refer to the detailed documentation.

You can now create and manage schemas directly from the Campaign Web User Interface. This feature allows you to create new tables, extend existing schemas and create custom forms. You can define custom data structures to support your specific business needs without requiring access to the Client Console.

Note: this capability is only available for a set of organizations (Limited Availability), and will be rolled out globally in a future release.

For more information, refer to the detailed documentation.

The Multilingual delivery feature is now available to all customers (GA). This feature allows you to send multiple messages in different languages in Adobe Campaign Web User Interface. You can choose the default language of your delivery as well as the different languages in which the delivery can be sent. You can also preview these deliveries in the languages you have chosen.

For more information, refer to the detailed documentation.

The following improvements have been made to multilingual push notifications:

• You can now quickly populate all language variants by uploading a CSV file containing your multilingual content. Read more
• Rich push notifications are now supported.

The Profile enrichment in Transactional Messages capability is now available to all customers (GA). In addition to emails, SMS and push notifications are now also supported. This feature allows you to personalize transactional messages by linking Adobe Campaign database fields to the message content. You can select target mappings, enrichment columns, and a reconciliation key to ensure accurate, real-time personalization while maintaining performance thresholds.

For more information, refer to the detailed documentation.

The Adobe Experience Manager content integration allows you to access all language and live copies created in Adobe Experience Manager directly within Campaign when building deliveries. You can refresh content in real-time to fetch the latest Adobe Experience Manager versions. This integration eliminates manual content synchronization between Adobe Experience Manager and Campaign, streamlining your multi-language campaign workflow.

For more information, refer to the detailed documentation.

Content experiments in Adobe Campaign Web allow you to define multiple A/B testing delivery variants in order to measure which performs best for your target audience. You can vary the delivery content, subject, or sender to test different versions and determine which variant produces the best results. You can conduct A/B tests on various email elements such as subject line, sender name and email body content.

For more information, refer to the detailed documentation.

The Continuous delivery activity allows you to add new recipients to an existing delivery. This delivery type avoids having to create a new delivery each time, making it more efficient for low-volume alerts or notifications sent as needed. A continuous delivery creates a single delivery instance. All delivery logs (broadLog) and tracking logs reference this one delivery, simplifying monitoring and reporting.

For more information, refer to the detailed documentation.

The approval process helps coordinate multiple stakeholders and ensures quality control before deliveries are sent. Use approvals when your organization requires validation from different teams, such as marketing managers reviewing content or data analysts validating target audiences.

For more information, refer to the detailed documentation.