Oracle Eloqua 26A: Redwood Experience, Smarter Integrations and Stronger Marketing Automation Control

Oracle Eloqua 26A is an important update for marketing operations, demand generation, campaign execution and customer experience teams using Oracle Eloqua for B2B marketing automation. The release focuses on a more modern Redwood experience, better Salesforce integration flexibility, stronger asset governance, more accurate lead scoring behavior, improved fatigue analysis handling and new integration capabilities for developers. Oracle’s Eloqua 26A Customer Overview covers release dates, 26A updates, important notifications, additional resources and Q&A for Eloqua customers. The update also reinforces Oracle’s direction toward a cleaner, more efficient and more consistent user experience across Eloqua campaign, content, integration and administration workflows. For businesses that depend on Eloqua for lead nurturing, segmentation, campaign orchestration, email marketing, Salesforce synchronization, reporting and revenue marketing operations, 26A is not just another release. It is a practical step toward better usability, stronger governance and more reliable marketing data operations. 

Why Oracle Eloqua 26A Matters for Marketing Teams 

Marketing teams are expected to do more with less. They need to launch campaigns faster, maintain brand consistency, personalize communication, manage segmentation rules, connect Eloqua with CRM systems and report on performance accurately. At the same time, they must protect data quality, avoid campaign fatigue and ensure marketing assets remain controlled across teams. Oracle Eloqua 26A supports these needs through updates that improve user productivity and platform reliability. The release includes new Redwood capabilities, protected template support, persistent selections across launchpads, program template management, audit log updates, Salesforce Integration App enhancements, contact modification handling, lead scoring changes, asset permission improvements and API-related updates. These updates are especially relevant for organizations with mature marketing operations teams, multi-region campaign teams, strict brand governance requirements or complex Salesforce-Eloqua integration models. 

Redwood Experience: A More Modern Eloqua Interface 

The Oracle Eloqua Redwood Experience continues to expand in 26A. Redwood is designed to make Eloqua easier to navigate, more consistent to use and more aligned with modern Oracle Cloud experiences. One of the key updates is HTML Email Source Editor protected template support. Oracle states that this increases consistency and brand integrity across marketing communications. Template designers can lock sections and define editable or delectable areas, helping prevent unauthorized message changes using left-side design elements. Oracle also notes that this design lock feature is unique to Redwood and not available in the classic editor. This is a strong update for marketing teams that manage brand-sensitive email campaigns. It helps central marketing teams protect approved templates while still allowing campaign users to make permitted edits. The result is faster campaign creation without losing brand control. 

Protected Templates for Brand Governance 

Brand consistency is one of the biggest challenges in distributed marketing. Regional users, campaign managers and demand generation teams may all need to create or edit emails, but not every user should be able to change core design elements, disclaimers, headers, footers or regulated messaging. Protected template support helps solve this. Designers can lock important sections while keeping selected areas editable. This gives businesses a better balance between flexibility and control. For enterprise marketing teams, this supports stronger governance across product campaigns, event emails, nurture campaigns, customer communications and partner marketing programs. It reduces the risk of inconsistent branding, accidental layout changes or unauthorized edits reaching customers. 

Persistent Selections Across Launchpads 

Oracle Eloqua 26A also improves user productivity through persisted selections across launchpads. Oracle explains that search results remain visible when users leave and return to the same listing page. Search only resets when users move to a different launchpad. Eloqua also retains individual user configurations and navigation state, including advanced filters, context filters, folder breadcrumbs, column order, sorting and visibility. This is a practical improvement for users who spend time navigating large asset libraries, campaign lists, forms, landing pages, emails and segments. In daily marketing operations, users often move between assets while building campaigns or checking campaign dependencies. Losing filters, sorting or folder context slows down execution. Persistent selections help users stay in their workflow, reduce repeated clicks and improve efficiency. 

Program Template Manager in Redwood 

Program templates are important for teams that want to standardize repeatable marketing processes. Oracle Eloqua 26A introduces the Program Template Manager as a Redwood-exclusive capability. Oracle states that it improves efficiency in managing and reusing program templates and follows the same implementation and user experience as other template managers. This helps marketing operations teams build more scalable campaign processes. Instead of rebuilding programs from scratch, teams can manage reusable templates for lead nurturing, data processing, campaign automation, event follow-ups, re-engagement flows and operational workflows. A better template manager supports faster execution and more consistent program governance. 

Audit Log Becomes Default in Redwood 

Auditability is critical for marketing operations. Teams need to know what changed, who changed it and when changes occurred. Oracle’s 26A update states that the Audit Log uses the Redwood experience and becomes the default experience with the Eloqua 26A release. It is no longer governed by the “Use Redwood Experience” setting. This is important because audit logs support accountability and operational control. When campaign assets, templates, settings or permissions are changed, teams need traceability. A modern audit experience helps administrators investigate changes faster and maintain stronger platform governance. 

Ask Oracle Navigation Direction Update 

Oracle has also updated its direction around Ask Oracle navigation. Based on user feedback and continued improvement, Oracle will introduce navigation based on Redwood’s in-app navigation. The navigation will include cascading menus, preserve Eloqua’s familiar menu structure, avoid long menus and extra steps, and help users stay in the flow of work. Oracle states that the timeline for the new navigation remains the 26B release. This update matters because navigation directly affects adoption. Eloqua users are already familiar with established workflows, so preserving familiar menu patterns can reduce training effort and transition friction. For businesses planning Redwood adoption, this also means user readiness should continue into future releases. 26A strengthens the Redwood foundation, while 26B is expected to continue the navigation evolution. 

Eloqua Redwood Experience: Broad Availability Across Areas 

Oracle’s Eloqua Redwood Experience is already available across many areas, including campaigns, dynamic content, email headers and footers, emails, field merges, files, forms, hyperlinks, images, landing pages, lead score models, programs, segments, shared content, shared filters, shared lists, signature layouts, signature rules, audit log, settings and several campaign-related capabilities. This shows that Redwood is no longer limited to a small set of screens. It is becoming a broader Eloqua user experience layer. For marketing operations leaders, the priority should be to review which teams are still using classic experiences, where Redwood access is needed, which users require training and which workflows should be tested before full adoption. 

Salesforce Integration App Enhancements 

The Eloqua Salesforce Integration App receives several incremental enhancements in 26A. Oracle states that users can update Salesforce Custom Object records from Eloqua Marketing Activities, allowing synchronization beyond standard objects and supporting more personalized and complex marketing workflows. Users can also use Salesforce Related Object attributes as unique identifiers for imports, improving accuracy and reducing data mismatches. This is a major area for B2B marketers. Salesforce-Eloqua synchronization is often central to lead management, campaign attribution, account-based marketing, sales follow-up and lifecycle reporting. The ability to work with Salesforce custom objects and related object identifiers gives teams more flexibility. It can support richer segmentation, better personalization and more accurate CRM-connected marketing operations. 

Better Notifications and Controlled Batch Sequencing 

Oracle also notes that email notifications now include the asset name in the body of the email, helping users identify relevant actions or items more clearly. Another update is the controlled availability of user-defined record order in batch for CDO Programs upsent actions, giving users more control over processing order in a batch. These may sound like small enhancements, but they support real operational efficiency. Clearer notifications reduce confusion and unnecessary follow-up. Controlled batch sequencing helps teams manage data processing more precisely, especially when record order matters for automation scenarios or complex data update flows. 

Fatigue Analysis Contact Modification Change 

Campaign fatigue is a serious issue in modern marketing. Businesses need to avoid over-communicating with contacts while still maintaining accurate segmentation and trigger behavior. Oracle Eloqua 26A changes how fatigue analysis affects contact modification dates. Oracle states that clients with fatigue analysis enabled will no longer have the contact date modified changed when a contact’s fatigue level is updated. This supports more accurate targeting and triggers for segments that use date modified in filters. Oracle also notes that auditing contact changes becomes easier with fatigue analysis enabled. This is a meaningful improvement for segmentation accuracy. If fatigue-level updates unnecessarily changed the modified date, contacts could enter or leave segments incorrectly. 26A helps reduce that risk. 

Lead Scoring Activity Change 

Oracle Eloqua 26A also updates lead scoring behavior. Oracle states that lead scoring will only use activities moved to the contact activity table. This avoids situations where a contact is scored for an activity that is later removed by bot detection or another system action. The change improves lead score accuracy and aligns with segmentation and APIs that only return activity table data. This is important for sales and marketing alignment. Lead scores must be trusted by sales teams. If scores include activities that are later removed, lead quality signals may become unreliable. By aligning scoring with retained activity data, Oracle helps improve confidence in lead prioritization, nurture routing and sales handoff. 

Import Asset Permissions for Security Groups 

Oracle Eloqua 26A introduces a new security group action: Import Asset Permissions. This allows users to grant a security group permission to existing assets by importing permissions from one or more existing security groups. Users can select permissions such as View, Edit, Delete, Security and Activate. Oracle notes that the action only adds permissions, never removes existing access, is available only to users with Asset Manager access and is recorded in the Audit Log. This is highly useful for administration. Managing asset permissions manually can be time-consuming, especially for large teams, new business units, agency users or regional marketing groups. Import Asset Permissions can reduce setup effort while preserving audit visibility. 

Eloqua API Gateway Advance Notice 

Oracle provides advance notice that the Eloqua API Gateway will be available for Early Preview with the 26B release. Oracle states that the API Gateway provides a more reliable integration experience, will include an update to the login endpoint to return new API URLs, will support longer OAuth tokens and may return a 429 Too Many Requests response when a user exceeds the flood protection limit. This is important for integration teams, middleware teams and Eloqua app developers. Businesses with custom integrations, data sync jobs, campaign automation extensions or reporting pipelines should start preparing early. API behavior changes can affect authentication, rate limiting, endpoint management and error handling. 

New App Developer Endpoint for Active Executions 

Oracle Eloqua 26A introduces a new app developer endpoint to retrieve active executions for an install instance. The endpoint is GET /Api/cloud/1.0/apps/{id}/active Executions, with authentication using the install instance and query parameters such as start Date, end Date, service Instanced, offset and limit. This gives developers better visibility into active execution activity. For businesses that rely on custom apps or integrations, this can improve monitoring, troubleshooting and operational support. Better execution visibility helps teams diagnose issues faster and maintain more reliable Eloqua integrations. 

Bulk API Support for Email Group Status 

Oracle Eloqua 26A also adds Bulk API support for the STATUS operator for Email Groups. Oracle states that users can export Email Group subscriptions in contact exports using the STATUS operator, with status values of subscribed or unsubscribed. To match Segment execution of Email Group subscriptions, Oracle notes that the contact email subscribed filter should be included. This is valuable for marketers and developers working with subscription management, consent-related segmentation and email group reporting. Accurate email group export logic can improve compliance workflows, reporting quality and downstream campaign data processing. 

Salesforce Native Integration Removal: What Customers Must Watch 

One of the most important notices in the 26A overview is the update on Oracle’s Eloqua Salesforce Native Integration removal. Oracle states that removal of the Salesforce Native Integration, originally planned for November 2025, has been postponed until April 2026 due to a technical issue that could affect Salesforce Campaign ID availability within Eloqua. Oracle also states that customers still using the deprecated native integration should transition to the Salesforce Integration App as soon as possible to ensure uninterrupted synchronization between Eloqua and Salesforce CRM. 

This is a priority action item. Organizations still using the legacy native integration should not delay migration planning. They should review current integration dependencies, field mappings, campaign ID usage, custom objects, imports, exports, sync behavior, error handling and reporting dependencies. A structured transition to the Salesforce Integration App can reduce business disruption and support stronger long-term integration performance. 

How NexInfo Helps Oracle Eloqua Customers 

NexInfo can help organizations assess, plan and execute Oracle Eloqua modernization with a focus on marketing operations, CRM integration, campaign governance, automation and managed services. For Oracle Eloqua 26A, NexInfo can support Redwood readiness assessment, Salesforce Integration App migration planning, campaign template governance, protected template strategy, audit log review, security group permission setup, lead scoring validation, fatigue analysis review, Bulk API readiness, API Gateway impact assessment and user training. NexInfo can also help businesses identify where Eloqua workflows need optimization across campaign execution, lead nurturing, segmentation, CRM sync, reporting and marketing operations support. The goal is not only to adopt new features. The goal is to make Eloqua more reliable, scalable and aligned with revenue marketing goals. 

Conclusion 

Oracle Eloqua 26A brings meaningful updates for modern marketing operations. The release strengthens Redwood user experience, protected email templates, program template management, audit logs, Salesforce Integration App flexibility, fatigue analysis behavior, lead scoring accuracy, security group permissions and developer integration support. For marketing teams, the value is clear: better brand governance, stronger CRM synchronization, improved lead scoring confidence, cleaner segmentation behavior, more efficient administration and stronger readiness for future Eloqua innovation. Organizations using Eloqua should review 26A carefully, especially if they rely on Salesforce integration, campaign templates, advanced segmentation, fatigue analysis, lead scoring or custom API integrations. With the right planning, Oracle Eloqua 26A can become a strong step toward smarter, cleaner and more scalable marketing automation operations. 

FAQ
What is Oracle Eloqua 26A?

Oracle Eloqua 26A is a release update focused on improving the Eloqua user experience, integrations, security administration and marketing automation reliability. It includes Redwood updates, Salesforce Integration App enhancements, fatigue analysis changes, lead scoring improvements, new API capabilities and important notices for Eloqua customers.

How does Redwood improve Oracle Eloqua?

Redwood improves Eloqua by creating a more modern and consistent user experience across several areas of the platform. It supports protected templates, persistent selections, program template management, audit log updates and broader launchpad availability. These changes help users work faster and reduce friction in daily marketing operations.

What is protected template support in Eloqua Redwood?

Protected template support allows template designers to lock specific sections and define which areas can be edited or deleted. This helps protect brand integrity while still allowing campaign teams to customize approved content. It is especially useful for companies with distributed marketing teams or strict brand governance standards.

Why is the Program Template Manager important?

The Program Template Manager helps teams manage and reuse program templates more efficiently in the Redwood experience. This supports repeatable automation processes such as nurture flows, data programs and operational workflows. It helps marketing operations teams standardize execution and reduce time spent rebuilding programs.

What changed in the Eloqua Salesforce Integration App?

Oracle Eloqua 26A adds enhancements such as updating Salesforce Custom Object records from Eloqua Marketing Activities and using Salesforce Related Object attributes as unique identifiers for imports. These improvements support more flexible CRM synchronization and reduce data mismatch risk in complex Salesforce-Eloqua environments.

Why does the fatigue analysis contact modification change matter?

With 26A, fatigue level updates no longer change the contact modified date for clients using fatigue analysis. This helps prevent incorrect segment triggers when filters depend on the modified date. It also improves audit clarity by reducing unnecessary contact modification updates.

How does Oracle Eloqua 26A improve lead scoring accuracy?

Lead scoring in 26A only uses activities that have moved to the contact activity table. This avoids scoring contacts based on activities that may later be removed by bot detection or system action. The result is cleaner scoring logic and better alignment with segmentation and API behavior.

What is Import Asset Permissions in Eloqua?

Import Asset Permissions is a new security group action that allows administrators to grant access to existing assets by importing permissions from other security groups. It can add View, Edit, Delete, Security and Activate permissions. The action is recorded in the Audit Log and helps simplify permission management.

What should customers know about the Eloqua API Gateway?

Oracle has provided advance notice that the Eloqua API Gateway will be available for Early Preview with 26B. It is expected to provide a more reliable integration experience, new API URL behavior, longer OAuth tokens and 429 responses when flood protection limits are exceeded. Integration teams should prepare for API impact review.

How can NexInfo support Oracle Eloqua 26A adoption?

NexInfo can help customers review Eloqua 26A readiness, plan Redwood adoption, assess Salesforce Integration App migration, validate lead scoring and fatigue analysis behavior, review security permissions, prepare API changes and support campaign operations. NexInfo helps businesses turn Eloqua updates into stronger marketing automation performance.