Product Updates

 Adobe Express connector now available in Workfront FusionWe’ve added a new Adobe Express connector so you can automate common Express workflows—like listing tagged documents, creating variations, exporting renditions, and checking operation status—directly from Workfront Fusion integrations and automations.OverviewThe Adobe Express connector exposes the primary Express API surface so you can programmatically interact with Express documents and tagged elements from your Fusion scenarios. The connector maps the Express API endpoints into modules that make it easy to include Express operations in integration flows, automation canvases, and scheduled jobs.Connector capabilities (API endpoints)Tagged documents — List all documents that contain tagged elements so you can discover assets to process. Tagged document details — Retrieve metadata and the tagged-element structure for a specific document to inspect editable regions and element IDs. Generate variation — Create new document variations by modifying tagged elements (for example, swap text, replace images, or change colors) and kick off asynchronous generation. Export rendition — Export a document or variation to JPG, PNG, MP4, or PDF renditions for downstream delivery or archival. Status — Check the status of asynchronous operations (such as variation generation or export jobs) so you can poll and take action when processing completes.What you can do with the Adobe Express connectorAutomate batch exports of finalized Express documents to your DAM or cloud storage (PDF, JPG, PNG, MP4). Drive templated content production by generating variations programmatically—populate tagged text, swap tagged images, or apply style changes for personalized outputs. Build end-to-end flows that discover documents, create variations, wait for generation to finish, export renditions, and then notify stakeholders or update records in downstream systems. Integrate Express document workflows with marketing automation, publishing pipelines, or asset management systems using Fusion’s mapping and conditional logic.How to get startedOpen your integration or automation canvas in Workfront Fusion and add the Adobe Express connector. Select the module that corresponds to the Express operation you need (Tagged documents, Tagged document details, Generate variation, Export rendition, or Status). Generate credentials at developer.adobe.com. Configure module inputs—document IDs, tagged element updates (payload), export format and options, and polling intervals for async operations. Map outputs into subsequent steps in your flow (for example, pass exported file URLs to an HTTP module, upload to cloud storage, or notify via email/Slack).Tip: Use the Status module to poll asynchronous jobs (variation generation or exports). Chain the Status check with conditional steps so your flow only proceeds when processing is complete.Behavior and tipsVariation generation and some export operations are asynchronous. Request a job and use the returned job ID with the Status module to determine completion. When updating tagged elements, include the element IDs and the correct edit payload as returned by the Tagged document details call to ensure modifications apply to the intended regions. Exported renditions return downloadable URLs (or files) that you can immediately ingest into other systems or store in Fusion-managed connectors. Saved credentials for Adobe Express are reusable across multiple Adobe connectors and modules—create the credential once and select it wherever Express auth is required.Where to find documentationStep-by-step instructions and reference details are available on Experience League: see the Adobe Express connector docs for module references, payload examples, and troubleshooting tips.Need help or want to give feedback?If you have questions or run into issues, post a comment below, start a thread in the Experience League Community, or contact Adobe Support through the Admin Console Support portal. Your feedback helps us prioritize enhancements (for example, additional export options, more granular variation controls, or deeper integration with Adobe storage and asset services). 

 Product update:mTLS support for custom webhooksTo meet stronger security requirements, you can now use mutual TLS (mTLS) with custom webhooks. Add a client certificate and private key to a webhook so Experience League integrations and automations authenticate to the receiving service using client-side TLS credentials.OverviewCustom webhooks now support Client certificate authorization. When you configure a webhook to use a client certificate, Fusion will present that certificate and private key during the TLS handshake so the remote service can verify the client. This provides an extra layer of security for server-to-server webhook delivery when the endpoint requires mTLS.How to configure mTLS for a webhookOpen the Add a hook dialog for the webhook you want to create or edit and check Show advanced settings. Under Authorization type, select Client certificate. In the Credentials field, click Add. This opens the Create a key dialog. Give the key a descriptive Key name (for example, “My HTTPS Client Certificate Auth key”). Paste the client Certificate (PEM) into the Certificate field. Use Extract if your certificate is bundled with other data. Paste the corresponding Private key (PEM) into the Private key field. Use Extract if the private key is in the same PEM bundle. Click Create a key to save the credential. Back in the Add a hook dialog, select the new key from the Credentials dropdown and click Save.Tip: Use a descriptive key name to make it easy to identify which certificate is used for which environment (dev, staging, prod).Reuse keys in HTTP modules and other placesThe client certificate keys you create for webhooks are not limited to use with webhooks. The same saved credentials (Basic auth and Client certificate keys) are selectable in HTTP modules (for example, HTTP > Make a request), so you can reuse one saved key for outgoing requests to the same mTLS-protected endpoint. Create the credential once and use it anywhere the matching auth type is supported.Notes and behaviorCredentials (both Basic auth and Client certificate keys) are saved once and can be reused across multiple webhooks and HTTP modules — you don’t need to re-enter them each time. Leaving the Credentials field empty means Fusion will send the received webhook data without presenting a client certificate. The Extract buttons in the Create a key dialog can parse a certificate or private key out of a pasted PEM bundle so you don’t have to split combined files manually. Stored keys are used for authentication during the TLS handshake; they are not sent as part of the webhook payload.How to get help or give feedbackIf you have questions or run into issues when configuring mTLS, post a comment below, start a thread in the Experience League Community, or contact Adobe Support through the Admin Console Support portal. Your feedback helps us prioritize enhancements (for example, additional certificate formats, automated rotation, or private key management integrations).Where to find documentationStep‑by‑step instructions and reference details are available on Experience League: see the Webhooks and HTTP module authentication topics for configuration examples and troubleshooting tips. 

Product update: Workfront Planning v2 connectorWorkfront Planning v2 connector now availableWe’ve released a new connector that exposes the expanded capabilities of the Workfront Planning API version 2 so you can automate and integrate Workfront Planning resources directly from Experience League integrations and workflows.OverviewThe new Workfront Planning v2 connector adds modules that map to the Planning API v2 surface so you can programmatically manage Workfront Planning workspaces, record types, records, fields, and access workflows. The connector also includes user and permission queries and a generic custom-call module so you can call any remaining endpoints not covered by the dedicated modules.What you can do with the Workfront Planning v2 modulesCreate, read, update, and delete workspaces, record types, records, and fields. Retrieve user-level info such as authorization ID and permissions. Request access to a resource and view pending access requests. Make custom API calls to any Workfront Planning v2 endpoint via the generic request module.How to get startedOpen your integration or automation canvas and add the Workfront Planning connector. Select the Workfront Planning v2 modules for the operations you need (Workspace, Record Type, Record, Field, User, Access Requests, or Custom Request). Authenticate with your Workfront Planning credentials and grant the connector the required permissions. Configure the module inputs (IDs, payloads, query parameters) and map outputs into subsequent steps in your flow.Tip: Use the Custom Request module to call any v2 endpoints not yet provided as first-class modules, or to experiment with new API capabilities before we add dedicated actions.Where to find documentationFull reference and step-by-step instructions are available on Experience League: Workfront Planning modules.Need help or want to give feedback?If you have questions or run into issues, post a comment below, start a thread in the Experience League Community, or contact Adobe Support through the Admin Console Support portal. Your feedback helps prioritize new modules and improvements. 

We want to hear how you work with brand standards, legal requirements, product information, competitor insights, and company policies, especially if you're using AI to bring any of this into your workflow today. Your input will directly influence the early concepts our design teams are building. Who we’re looking for✓AEM users who manage, deploy, or create digital assets✓ AEM users who are familiar with how context is managed at their company - this can include legal context, brand standards, product information, competitor insights, or company policies.✓ To participate in pre-release activities, you must be a member of the Adobe Feedback Program. If you aren’t sure whether your company is a member, no worries - we will check when you sign up! What we ask of users✓ Join us for a 30 minute session where we will discuss how you manage context at your company today, whether or not you are using AI as part of this process. Timeline✓ Interviews will take place this week and next week. How to joinCLICK HERE to sign up for a time to chat with the team. We’ll post below once the interview timeslots are full. Questions?Ask below — the research team will be monitoring this thread throughout the sign-up period. 

Product update: View and compare scenario versionsThis post introduces a new Review changes experience that makes it easy to see exactly what changed between two versions of a scenario so you can confidently restore older versions when needed. OverviewYou can now open a side-by-side comparison of any two versions of the same scenario to view detailed differences before you restore a version. The Review changes view highlights additions, removals, and edits (colored green and red) and groups changes by logical sections (Scenario, Scenario settings, Modules, Flows, Router routes, Error handlers, and Orphan groups). Restoring a version creates a new version, so all restores are reversible.How to compare scenario versionsClick Scenarios in the left panel and open the scenario you want to inspect. Click the More icon at the bottom of the screen, then choose Previous Versions. From the list of previous versions, click View changes for the version you want to compare. The Review changes panel opens and shows a side-by-side comparison: the current scenario on the left and the selected version on the right.Tip: Use the Compare from and Compare to dropdowns near the top of the panel to pick any two versions for comparison.Understand the comparison viewThe Review changes panel visually indicates what would happen if you restored the right-hand version:Red (left): Items present in the left (current) version that would be removed if you restored the right-hand version. Green (right): Items present in the right-hand version that would be added if you restored it. If a value changed between versions, you’ll see the old value in red on the left and the new value in green on the right.Change groupsChanges are grouped into these sections to help you quickly locate relevant differences:Scenario: Name, description, and type. Scenario settings: Schedule and processing options. Modules: Modules added, removed, moved, or reconfigured. Flows: Branches added, removed, or reordered. Router routes: Routes and their contents. Error handlers: Error-handling branches. Orphan groups: Disconnected modules on the canvas.Restore behaviorTo revert to the version shown on the right, click Revert to selected version. Restoring saves the restored scenario as a new version so the change itself can be undone later. If you want to restore the version currently shown on the left, click the ⇄ swap button to put it on the right, then click Revert to selected version.When there are no differencesIf the two selected versions are identical, the Review changes view displays No differences found.More information and supportFor step-by-step guidance, see: View and manage scenario versions on Experience League.If you have questions or feedback, post a comment below or contact Adobe Support via the Admin Console Support portal. 

This post is for informational purposes only. It is not legal advice and does not warrant your compliance. The Adobe Marketo Engage product capabilities described in this help article, configured and operated appropriately, support a compliant implementation. Each user is responsible for determining and complying with its obligations under applicable law.OverviewOn April 14, 2026, France’s data protection authority (CNIL) published a recommendation on the use of open tracking pixels in emails. The guidance clarifies when consent is required and highlights the importance of proper consent practices for email pixel tracking. This policy impacts any entity sending emails to subscribers based in France.CNIL provided a three-month period from the date of the recommendation for companies to inform their email recipients of the presence of the tracking pixels, their purpose, and the recipients’ right to opt-out. During this transition period, Marketo Engage users are expected to notify their recipients about pixel tracking and provide an opt-out if necessary. CNIL is expected to begin enforcement activities after July 14, 2026.As the CNIL and other regulators clarify guidance on tracking pixels and related issues, Adobe will continue to monitor updates and inform you of changing technical capabilities.Marketo Engage offers controls that help you manage open tracking at the email level. Users are responsible for determining their own compliance obligations under applicable CNIL guidance and other laws. What is an email tracking pixelAn email tracking pixel is a small transparent image (just 1x1 pixel in size) embedded in the HTML of an email. When a recipient’s email client loads the email images, the pixel pings a server that records data such as a timestamp, device type, email client, and sometimes an IP address for approximate location. That log is tied to the recipient’s record, allowing marketers to see whether an email is opened.Guidance on consent trackingDetailed steps are outlined for Marketo Engage users in this help article on Experience League.Updates and supportFor the latest updates, bookmark this post. If you have any questions, please post a comment below.

Prior to March 2026, a boolean FALSE value was treated as "no value" during an API merge. This meant that if either of the merged leads had a TRUE value, the result would be TRUE. But in cases when FALSE was an important value, it could cause problems (for example, if a lead's value changed and then merged with an old record, the value could be erroneously reverted back). This behavior was different than other field types.In the March '26 release, Adobe fixed this issue. For API merges, Salesforce merges when they are synced to Marketo, as well as Automerge (if you have it configured); only NULL values in boolean fields are treated as "No Value" when determining which lead to take the value from.The result is that the conflicting field values are now taken from the "winning" record (the resulting lead or contact), unless the winning lead has NULL for that field and the "losing" record (the one disappearing) has a value (TRUE or FALSE). Standard Marketo boolean fields, such as Unsubscribed, will always have a value (TRUE or FALSE), so these will be taken from the winning lead in all cases. 

Hey AJO community! We've just released an updated version of the Image to HTML converter feature, delivering improved accuracy in HTML generation through the use of higher-tier LLM models!This enhancement improves upon the existing feature that enables marketing teams to convert static image-based email designs (JPEG or PNG) into fully modular, editable HTML templates ready for deployment in the Email Designer, without requiring developer involvement. The updated model improves the precision and reliability of the generated HTML output, reducing post-generation corrections and supporting more consistent production workflows.If you're running email through Journey Optimizer and haven't tried this yet, check out the documentation to learn more! Documentation: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/content-templates/image-to-html  

The Project Falco beta program grants you exclusive access to an updated version of Adobe Journey Optimizer B2B Edition that is specifically designed to supercharge your Marketo Engage instance (no purchase required).Program highlights• Agentic Program & Journey Creation: Design and optimize omni-channel lead journeys inseconds leveraging your existing programs, campaigns, and channels inside Marketo Engage.• Agentic Audience Segmentation: Prompt the audience agent to automatically discover andcreate audience segments using Marketo Engage data.• AI-powered Decisioning: Achieve next-gen personalization through AI-powered Next-bestJourney and Journey Path decisioning.• Omni-channel Orchestration: Connect and activate inbound and outbound channels togetherfrom a single journey canvas, expanding to web and paid channels.• Agentic BDR Experience: Allow your BDR teams to automate outbound sequences using theAccount Qualification Agent together with integrated marketing data.What you getEarly accessFirst access to new capabilities: AI agents, audience creation, journey orchestration, conversational AI, and more, before general availability.Direct product line1:1 engagement with the Development, Product Management, Design, and Product Marketing teams through a dedicated private Slack space and regular conference calls.Roadmap influenceReal influence over what we build next. Participate in the development process, submit enhancement requests prior to release, and directly shape the final feature set before it ships.Marketo-native setupAlready on Marketo Engage? Adobe Journey Optimizer B2B Edition Prime is built to integrate seamlessly, no heavy lift to get started.What’s included in your beta access• Audience Creation and Management• Journey Creation, Optimization, and Decisioning• Conversational AI Experiences• Lead Journeys• Brand Concierge• Sales Qualifier• Reporting & Analytics Project Falco video demoWhat we ask of youDurationThe beta program begins in late June and runs through approximately the beginning of August.Your investmentAll we need is your time and honest feedback. There is no purchase required.After the 6 weeksThe conversation doesn’t have to end there. Beta partners can extend their involvement as the product moves toward general availability.How it works1. Apply. Submit your interest. We’re selecting a small cohort of Marketo Engage customers to partner with.2. Onboard. We get you set up. Because you’re already on Marketo Engage, the integration isstraightforward.3. Use and explore. Your team runs Adobe Journey Optimizer B2B Edition Prime in yourenvironment across the 6-week window.4. Feedback sessions. Regular touchpoints with the Adobe product team. Your input directlyinfluences roadmap decisions.5. Extend or transition. At the end of the beta, we discuss continued involvement in thelighthouse program if you are open to it.Ideal for• Existing Marketo Engage customers• Marketing operations practitioners• Teams with a mandate to evaluate AI in their stack• Organizations willing to co-create with us• Practitioners who want influence, not just accessCommon questionsDo we need to buy anything to participate?No. There is no purchase required to join the beta. Your only investment is time and feedback.We’re already on Marketo. How much setup is involved?Adobe Journey Optimizer B2B Edition Prime is designed to integrate with Marketo Engage data, so the lift to get started is minimal. We handle all of the onboarding.What does “design partnership” mean in practice?It means your team’s experience in the product shapes what we build next. You’ll have multipletouchpoints with the Adobe product team during the Beta Program.What happens after the 6 weeks?There’s an opportunity to extend your involvement beyond the beta. We’ll discuss options based on your team’s goals and our roadmap timing.How many companies are you selecting?We’re keeping the cohort intentionally small, so every partner gets meaningful access and attention from the product team. Ready to co-design what’s next?The beta launches in late June. Spots are limited. 

Marketo Engage is in the process of migrating to the Adobe Federated Email Service (FES), a centralized email-sending solution designed to streamline and standardize email delivery across Adobe's various teams and products. Over the next couple of weeks, all Marketo Engage subscriptions will be on FES, making email delivery more reliable, stable, and easier to support at scale.What do you need to do?If you do not have a Branded Return-Path configured during the initial set up of the purchased Dedicated IP, or a Branded Return-Path SKU, no actions are needed. Users who have a Branded Return-PathFor those who had a Branded Return-Path configured during the initial setup of a purchased Dedicated IP, or a Branded Return-Path SKU, you must update the MX record for that specific Branded Return-Path domain.Note: this is not the Branded Domains for your links.Ask your IT team to update the MX record for your branded return path using the values listed below for your pod. If you're unsure which pod your subscription is on, see: identify your data center.The migration has been separated into two cohorts. The first cohort has been completed. June Cohort POD New MX Record SJ  or.mx.mseme.adobe.net  LON or e  gbr.mx.mseme.adobe.net  NLD  irl.mx.mseme.adobe.net  SN  aus.mx.mseme.adobe.net  mlm100x  or.mx.mseme.adobe.net  mlm300x  aus.mx.mseme.adobe.net  mlm400x  irl.mx.mseme.adobe.net  ajob2b100x  or.mx.mseme.adobe.net   July Cohort POD New MX Record AB  va.mx.mseme.adobe.net  mlm200x  va.mx.mseme.adobe.net  ajob2b200x  va.mx.mseme.adobe.net   Expected service impactsThe MX record update is required to ensure Adobe continues to receive and process Asynchronous bounce events on your behalf. No additional service impacts are expected. ScheduleTo receive the full benefits of the FES migration, Branded Return-Path users should make this change by the dates below.June Cohort: Make the change by July 17, 2026.July Cohort: Make the change by July 31, 2026. If you don’t update your records by the date(s) listed:Your subscription won’t be able to process Asynchronous Hard Bounces (which typically amounts to less than 1% of messages sent). Very low chance of Deliverability impacts. When you do update the MX record and we begin to process async bounces again, the applicable recipients will automatically be identified and marked as a Hard Bounce.Updates and supportFor the latest updates, bookmark this post. If you have any questions, contact Adobe Support via the Support portal in the Admin Console or Experience League.

If you've been following Adobe Summit, you'll have seen the announcement of Adobe Data Engineering Agent, a purpose-built Adobe Experience Platform Agent powered by Experience Platform Agent Orchestrator. While the official blog covers the vision well, I want to share more on what it unlocks for your workflows your Adobe stack.  What it's built to doData preparation is high-value but time-intensive, often delaying downstream activation. Adobe's AI & Digital Trends Study found 75% of organizations cite data integration and quality as their top AI implementation challenge. Data Engineering Agent addresses this with an AI-guided, human-in-the-loop approach that automates operational steps across the data lifecycle, so you can focus on higher-value decisions. How it plays out across your stackAdobe Experience Platform: Faster, more confident data onboardingData Engineering Agent extends Experience Platform’s data ingestion strength by making the onboarding process more guided and automated. Instead of manually configuring mappings, schemas, and dataflows, you work conversationally with the agent. It analyzes source data, recommends schema structures aligned to Experience Data Model standards, flags issues early, and builds dataflows after your approval.Notable use cases:Teams managing multi-brand or multi-region implementations that deal with inconsistent naming conventions across business units will find the schema recommendation and validation workflow particularly valuable for maintaining consistency at scale.Adobe Real-Time CDP and Adobe Journey Optimizer: Upstream quality that flows downstreamReal-Time CDP turns unified data into real-time audience activation. Journey Optimizer journeys depend on fresh, accurate profile and event data. By improving data quality upstream through validation, enrichment, and early issue detection, Data Engineering Agent ensures cleaner profiles and faster activation to shorten time-to-live for audiences and journeys.Notable use cases: For organizations using Real-Time CDP with warehouse-native architectures, the agent automates schema creation and dataflow configuration—reducing back-and-forth between data engineering and analytics without compromising governance. For teams building trigger-based journeys from real-time signals, faster validation of streaming datasets accelerates journey activation.Adobe Customer Journey Analytics: Broader access to SQL-powered data prepCustomer Journey Analytics gives analysts the ability to ask cross-channel questions without reprocessing pipelines but SQL-based data preparation has traditionally required platform expertise. Data Engineering Agent brings natural language prompting to that. It can generate optimized, schema-aware SQL with a preview before execution, monitor and troubleshoot SQL jobs, validate dataset readiness before running analysis, and proactively surfaces issues and troubleshoots.Notable use cases: Campaign performance analysts who regularly validate datasets before refreshing Customer Journey Analytics views get a more automated quality check built into their existing workflow.Adobe Experience Platform: Faster implementation and root cause analysis for better data collection Implementation engineers often juggle documentation, forums, internal wikis, and cross-functional meetings to configure complex data collection use cases. Troubleshooting is equally fragmented, requiring manual lineage tracing across components.Data Engineering Agent brings in-context product knowledge directly into the workflow, leveraging Experience League, community forums, and GitHub to explain how components fit together. When issues arise, it surfaces lineage views and dependency maps to quickly identify misconfigurations and root causes.Notable use cases: For teams managing complex, multi-touchpoint data collection setups, the combination of contextual guidance during configuration and semantic lineage visibility during troubleshooting can compress what used to be a multi-day, multi-meeting process into a single working session. What to know before it arrivesData Engineering Agent is coming soon to Experience Platform. A few operational notes:Human-in-the-loop by design. You review and approve recommendations before the agent executes. Built into the existing governance layer. Actions are auditable and operate within Experience Platform's data governance framework. Accessed through AI Assistant. The agent surfaces through the conversational AI Assistant interface already available across Experience Platform applications.----------------------------------------------------------------------------------------------------------------------I’d love to hear from you! Which part of your data engineering workflow, schema mapping, SQL data prep, data collection troubleshooting, or something else, consumes the most time today that Data Engineering Agent can help with? Let me know your thoughts below!

We're excited to announce Unified Review and Approval, a new capability that brings together Adobe Workfront and Adobe Frame.io into a single, deeply connected review experience. This integration is available now for all Workfront customers upon a contract update. What's included Unified Review and Approval natively integrates Frame.io's professional-grade review surface directly into your Workfront workflows. Here's what your teams get:One review surface for every content type — Whether your team is reviewing a 30-second social clip, a 200-page PDF, or a Photoshop comp, the experience is the same. Frame.io supports over 40 file formats with native video playback for formats like ProRes, H.265, and DNxHD — plus visual markup tools for annotating directly on the asset. Frame-accurate commenting for video — Frame.io was purpose-built for creative review, with frame-accurate commenting, advanced watermarking, and support for files up to 500 GB. That capability now lives natively with Workfront. Multi-stage approval workflows — Define clear roles: reviewers provide feedback, approvers make binding decisions (Approve or Needs Work). Approvals reach a conclusion, and everyone has visibility into exactly where things stand. No more download-upload-reupload — Unified Review and Approval is built on Adobe enterprise storage, a common layer connecting Workfront, Frame.io, and Creative Cloud. Assets live in one place and are accessible across tools without manual file transfers. Creatives work in place, and reviewers always see the latest version. Creative work-in-progress workspaces — Teams get their own visual-first workspace for managing rich media with custom metadata, collections, and semantic search that automatically indexes every asset and makes it searchable via natural language. Why it matters Marketing teams are producing more content for more channels than ever, and video has become the dominant format across social, web, retail media, and internal communications. Research shows creatives spend roughly 70% of their time managing files, tracking feedback, and following up rather than doing meaningful creative work. When your review tools aren't connected to your marketing management platform, teams adopt manual workarounds — downloading files, forwarding emails, tracking approvals in spreadsheets. The result is slower time to market, lost feedback, and version confusion. Unified Review and Approval addresses this by closing the gaps between marketing management, creative review, and content delivery. When your marketing management, creative collaboration, and asset delivery systems share a common foundation, every handoff gets faster and every workflow gets simpler. How to get started Unified Review and Approval is available now for Workfront customers upon a contract update. To get started:Work with your Adobe account manager to get on the updated integration Check out the Get Started articleWhether your team is managing a handful of campaigns or operating a global content supply chain, the path forward is the same — one review surface, one approval process, one source of truth. Learn moreRelease Notes Blog announcement Getting startedQuestions or feedback?We'd love to hear from you. How does your team currently manage review and approval across content types? What challenges are you hoping this solves? Drop your questions or thoughts below — our product team is monitoring this thread. 

Japanese version of this announcement at the bottom of the page | このお知らせの日本語版は、このページの下部に掲載されています。To enhance performance, reliability, and scalability, Adobe is performing required network maintenance for Marketo Engage on May 16, 2026, from 16:00 UTC to 18:00 UTC. This will only affect subscriptions hosted in the San Jose data center. (Learn how to locate your data center)During this two-hour maintenance window, all Marketo Engage services will be unavailable. We recommend taking the following steps to mitigate any impact on your business.Avoid creating or updating leads/people or running processes that modify Person records.Do not trigger follow-on processes, as scheduled campaigns will be paused.Temporarily disable any integrations that send/receive data to/from Marketo Engage.Avoid running data imports/exports or major lead/person-generation campaigns.For externally hosted forms, Adobe can support submission caching. To request this, contact Adobe Support with your Munchkin ID and relevant form IDs before May 11.Additional impacts include:CRM integrations and LaunchPoint services will be disabled but should resume automatically afterward. Landing pages, forms, and data collection will be unavailable, and a maintenance message will be displayed instead. If you rely on externally hosted forms, be sure to request caching in advance.For updates, visit the Adobe Status page and consider subscribing to notifications. If you have any questions, contact Adobe Support via the Support portal in Admin Console or via Experience League.  5 月 16 日に予定されているサンノゼデータセンターの計画メンテナンスについて パフォーマンス、信頼性、拡張性の向上のため、2026 年 5 月 16 日の 16:00 から 18:00（協定世界時）までの間、Marketo Engage のネットワークメンテナンスを実施します。このメンテナンスは、サンノゼデータセンターでホストされているサブスクリプションにのみ影響します。（データセンターの確認方法については、次のリンクを参照してください - リンク） この 2 時間のメンテナンス中は、すべての Marketo Engage サービスにアクセスできなくなります。ビジネスへの影響を最小限に抑えるため、以下の事項に従うことをお勧めします。 リード／ユーザーの作成や更新、個人レコードを変更するプロセスの実行は避けてください。スケジュールされているキャンペーンは一時停止されるため、後続のプロセスをトリガーしないでください。Marketo Engage との間でデータの送受信を行う統合処理を一時的に無効*にしてください。データのインポート／エクスポートや、大規模なリード／ユーザー獲得キャンペーンの実行は避けてください。外部でホストされているフォームの場合、送信のキャッシュがサポートされています。このキャッシュを希望する場合は、5 月 11 日までにアドビサポートまでご連絡ください。その際、Munchkin ID と関連フォーム ID を伝えてください。 その他の影響メンテナンス中は CRM 統合と LaunchPoint サービスにアクセスできなくなりますが、メンテナンスが終了すると自動的に再開されます。また、ランディングページ、フォーム、データ収集が停止し、メンテナンスに関するメッセージが表示されます。外部でホストされているフォームを使用する場合は、必ず事前にキャッシュを依頼してください。 最新情報については、Adobe Status ページ を参照してください。通知に登録 することをお勧めします。不明な点については、Admin Console のサポートポータルまたは Experience League からアドビサポートまでお問い合わせください。

We’ve rolled out new Adobe Campaign updates and shared resources to help teams move faster, experiment more easily, and scale customer engagement with confidence. Here’s a quick look at what’s new: Adobe Campaign v8 updatesRecent v8 releases extend key use cases in the web UI while continuing to strengthen flexibility, security, and governance in the client console. Highlights include:Firefly + third-party image generation model integration Campaign inventory timeline view Multilingual deliveries Transactional message profile enrichment Adobe Experience Manager live copies + language copies Content experiments (A/B testing) Continuous delivery enhancements Campaign approval management SMS connector Security improvements 🔗 View full release notes:Adobe Campaign v8 Web UI release notes Adobe Campaign v8 client console release notes Support note: Adobe Campaign Standard and Campaign Classic remain supported. Roadmap investments are focused on Adobe Campaign v8, prioritizing long-term stability, security, and modern campaign orchestration capabilities. Adobe Campaign v8 product description updateWe’ve updated the Adobe Campaign Managed Cloud Services (v8) product description by removing the license metric for generative actions related to AI Assistant content generation in Adobe Campaign Managed Cloud Services v8.While responsible use guardrails remain in place, we will not meter usage of these generative actions - making it easier to experiment with and scale AI-assisted content workflows. Join us at Adobe SummitAdobe Summit (20-22 April in Las Vegas) is a great opportunity to connect with Adobe experts and peers, see what’s coming next across Customer Engagement applications, and get practical guidance you can bring back to your team.Register for Tips & Tricks to Accelerate Adobe Campaign v8 Adoption (Session S525) Campaign VIP Customer Breakfast at Adobe Summit where you can meet other customers and and members of the Adobe Campaign product team. Reach out to your account team for more information on how to register. Resources to help you adopt fasterAdobe Campaign v8 self-guided product tour AI Assistant preview for content generation (Adobe Experience League login required) Webinar: How Southwest unlocked speed and stability with with Adobe Campaign v8 Ultimate Success Webinar: How customers are modernizing campaign execution with Adobe Campaign and Adobe Journey Optimizer Customer success story: General Motors: Pioneering new approaches to zero-friction customer experiences 

What’s New in 2026.02.0The 2026.02.0 AEM release brings important enhancements across Generation, Activation, and Agentic AI capabilities. Below is a quick summary to help you understand what’s included and where to focus.AEM GenerationContent Fragment Management and Launches, OpenAPI side-port to 6.5 LTS SP2: Improved compatibility and extensibility with OpenAPI side-port support, helping teams working across Cloud Service and 6.5 LTS SP2 environments streamline integrations and content workflows.AEM ActivationQuiet Hours & Update-Free Periods – Now GA: Greater operational control with generally available support for defining quiet hours and update-free windows. This helps teams manage deployments and content activation with reduced disruption. AEM Content Advisor in Adobe Express: Content guidance capabilities are now integrated into Adobe Express, enabling smarter content refinement and optimization directly within creative workflows.AEM Agentic AIPipeline Troubleshooting | Code Quality Step: Enhanced troubleshooting within the pipeline experience, specifically targeting the code quality step to help teams identify and resolve issues faster.🎥 Release Overview Video (6 minutes)Watch here: https://video.tv.adobe.com/v/3480399/Seed Q&APlease use this thread to ask questions related to this release.See all the Previous Releases here and the Current Release Notes here.

February' 26 release notes Check out what's new and improved in the latest Adobe Journey Optimizer product release update: Release Notes New capabilitiesJourney arbitration: You can now use ranking formulas to automatically boost journey priority scores based on customer profile attributes and contextual factors, ensuring customers enter the most relevant journeys. This capability is only available for a set of organizations (Limited Availability). To gain access, contact your Adobe representative. Action activity in journeys: Journey Optimizer supports a new generic Action activity that enables you to configure both single actions and multi-action inbound action groups, allowing for streamlined action configuration within the journey canvas. In particular, this new feature allows for: A simplified native action configuration within the journey canvas. The capacity to create multi-action inbound action groups. The ability to add optimization to any built-in channel action. The ability to add both experimentation and multilingual options to any action. Wave sending of outbound messages: You can now schedule messages from Journey Optimizer campaigns or journeys to be delivered in controlled batches over time. Wave sending offers the following benefits: Better deliverability – Spread sends over time to help maintain a strong sender reputation and reduce the risk of being flagged as spam. Load control – Avoid overwhelming downstream systems (e.g. call centers, landing pages) by limiting how many messages go out at once. High-volume and time-sensitive use cases – Suited to large audiences or when you need to control timing (e.g. call center capacity, ramp-up, or time-bound offers). Migrate subdomains to custom delegation: You can now migrate subdomains using the CNAME delegation mode to custom delegation directly from the interface, so you can meet stricter security policies in line with your company's guidelines without re-creating channel configurations. This capability is only available for a set of organizations (Limited Availability). To gain access, contact your Adobe representative. Web push notifications channel: Adobe Journey Optimizer now supports Web push notifications, expanding the push channel beyond mobile. You can seamlessly deliver notifications to both mobile and desktop browsers, enabling you to reach customers directly on their devices without requiring an app. This enhancement allows you to engage users with timely, personalized messages in real time, leveraging the same authoring workflows and targeting capabilities already available for mobile push. Content decision activity: A new Content decision activity is now available in the journey canvas for integrating personalized offers directly into your customer journeys. This activity enables you to deliver decision-based content and reference those offers throughout your journey—in conditions for creating eligibility-based branching, in custom actions for passing offer data to external systems, and in other activities for building fully personalized customer experiences. Self-service migration tooling APIs:  Migration tooling APIs are now available to programmatically migrate Decision management entities to Decisioning, featuring: Flexible migration scopes (sandbox, offer, or decision level) Automated dependency analysis and validation Rollback support for completed migrations Detailed migration reports with object mappings Custom action monitoring: Gain deeper insight into the health and performance of your custom action endpoints with a new monitoring dashboard and enriched journey step event data. Track successful calls, errors, throughput, response times, and queue wait times to quickly understand when, where, and why anomalies occur. Decisioning support in SMS channel: You can now personalize and optimize the content of your SMS messages with Decisioning. Use Priority Scores, Formulas, or AI Models to display the best content to your customers. Please find the detailed information around the new capabilities and improvements here: Latest ReleaseFeel free to reach out in case you have any questions and/or feedback through the below comment section.

February' 26 release notes Check out what’s new in the latest Adobe Experience Platform release update: Release Notes New capabilities Alerts Slack integration for customer-facing alerts: You can now deliver customer-facing alerts to Slack. Follow the step-by-step tutorial to set up the Slack integration and receive alert notifications directly in your Slack workspace. Destinations Snowflake Batch generally available: The Snowflake Batch destination is now generally available. Real-Time CDP customers worldwide can now use this connector to activate data into their Snowflake accounts without needing to physically copy the data. All limitations from the limited release have been lifted (availability for US-only customers, support for audiences belonging to the default merge policy only). Segmentation Service Editable API audiences: You can now edit audiences created using either the Segmentation Service API or the Audience Agent in Segment Builder. Note: Audiences that contain time-series data cannot be edited using Segment Builder at this time. External audience data expiration refresh: You can use the Segmentation Service API to extend the data expiration of your external audiences.  Sources Unity Catalog support in Databricks source connector: The Databricks source connector now supports Unity Catalog. Experience Data Model (XDM) Restricted Editing for Schemas with Datasets: Editing operations that result in breaking changes are now restricted once a dataset exists for a schema. When a dataset is associated, you can no longer rename or delete fields, change field data types or formats, modify identity descriptors, manage related fields to remove existing fields, or change the assigned class; additive changes and field deprecation remain supported. Please find the detailed information around the new capabilities and updates here: Latest ReleaseFeel free to reach out in case you have any questions and/or feedback through the below comment section.

Content Advisor (evolution of Asset Selector) brings AI-powered content discovery directly into your content supply chain. With AI search and context aware recommendations based on canvas content and campaign briefs, native access to channel ready Dynamic Media renditions, customers can now discover relevant assets faster, work more creatively, and reuse content — all without switching tools. What This Means for customers Design and marketing teams can now discover and leverage approved brand assets instantly without manual searching. Creatives and non-creatives alike benefit from AI recommendations that inspire new content ideas and accelerate execution.  Enterprise content supply chains become more efficient as teams remain in a single workflow from discovery to creation.  Content Advisor capabilities at a glance: AI Search for smarter asset discovery Smart suggestions based on Express canvas context Campaign briefs to discover relevant assets Native access to all your Dynamic Media renditions Access asset metadata and filters consistent with Assets view Recent and saved searches Search across and within collections  See it in action Experience League documentation RegardsApoorvaDirector Product, AEM Assets and Dynamic Media

January' 26 release notes Check out what’s new in the latest Adobe Experience Platform release update: Release NotesNew capabilities Agent Orchestrator Adobe Experience Platform Agents usage-bound trial: Select customers now have a complimentary trial access to Adobe Experience Platform Agents. You can use the trial to explore and interact with Agents through the AI Assistant interface powered by Adobe Experience Platform Agent Orchestrator. The trial offers hands-on experience with AI Agents that operate within the context of customers’ existing Experience Cloud products and environments, allowing teams to evaluate value before committing to a full purchase. Destinations Kevel destination connector now available: The Kevel streaming destination for Adobe Experience Platform enables customers to activate Adobe audiences directly into Kevel’s UserDB and Segment Management APIs to support real-time targeting at ad decision time. Kevel provides the AI-enabled technology and expert guidance that help innovative commerce leaders launch, scale, and succeed in retail media. Kevel’s Retail Media Cloud powers targeted, attributable, customizable ad formats for on-site and off-site advertising. Index Exchange destination connector now available: Use this destination connector to export audience segments from Adobe Experience Platform directly to Index Exchange’s programmatic advertising platform. Index is a global advertising supply-side platform that helps media owners maximize the value of their content across every screen. With over 20 years of industry leadership, Index connects the world’s largest brands with premium experience makers to deliver high-quality consumer experiences. Real-Time Customer Profile Monitor profile ingestion job status: You can now monitor the job-level progress percentage for batch Profile ingestion dataflow runs. This feature provides real-time visibility into the current progress of batch ingestion jobs, including critical checkpoints that indicate whether the ingestion is ready for customer segmentation and Adobe Journey Optimizer lookups. For large ingestions that may take several hours to process, this progress transparency helps you understand whether the job is progressing normally or encountering issues, reducing uncertainty during data processing. Segmentation Service Audience validation: Experience Platform now provides built-in validations to ensure your audiences are accurate, stable, and scalable. These checks are automatically run in real-time while you’re creating your audience definitions.  Sources Oracle Eloqua V2 source: A new Oracle Eloqua source connector is now available, replacing the deprecated connector. This updated connector provides enhanced functionality and improved reliability for ingesting data from Oracle Eloqua into Experience Platform. Customers using the existing connector should migrate to the new implementation, as existing connections will no longer function. The new connector supports all setup and configuration steps needed to connect to Oracle Eloqua and ingest marketing automation data. Salesforce Marketing Cloud V2 source: A new Salesforce Marketing Cloud source connector is now available, replacing the deprecated connector. This updated connector provides improved performance and additional capabilities for ingesting data from Salesforce Marketing Cloud into Experience Platform. Customers using the existing connector should transition to the new implementation. The new connector includes comprehensive setup instructions for connecting to Salesforce Marketing Cloud and ingesting marketing automation data. Please find the detailed information around the new capabilities and updates here: Latest ReleaseFeel free to reach out in case you have any questions and/or feedback through the below comment section.

Real-Time CDP Collaboration Release Real-Time CDP Collaboration now supports CSV file upload as a new method for sourcing audiences, as well as new mobile match keys (IDFA and GAID) for enhanced audience matching and measurement.New featuresCSV upload for Audience Sourcing: Upload CSV files to source audiences into Collaboration directly from the UI. Ideal for onboarding first-party data for short-term collaboration projects.  Mobile Match Key Support: Collaboration now supports mobile match keys, including IDFA and GAID, for audience matching and measurement. These match keys are selected during account setup and can then be used when configuring connection settings for new connections and in downstream collaboration workflows.Please find the detailed information around the new functionalities here: Latest ReleaseFeel free to reach out in case you have any questions and/or feedback through the below comment section.

January' 26 release notesCheck out what's new and improved in the latest Adobe Journey Optimizer product release update: Release NotesNew capabilitiesDecisioning support in Push channel: You can now personalize and optimize the content of your Push notifications with Decisioning. Use Priority Scores, Formulas, or AI Models to display the best content to your customers. Direct mail channel in journeys: Previously limited to Campaigns, Direct Mail channel is now available on the journey canvas, enabling you to incorporate Direct Mail into your journeys. Direct Mail can now be used in both batch and 1:1 journey scenarios, with support for file extraction configuration and time-based frequency settings. Quiet hours (time-based exclusions): Quiet hours let you define time-based exclusions for Email, SMS, Push, and WhatsApp channels. They ensure that no messages are sent during specific periods of time, helping you respect customer preferences and compliance requirements. You can apply quiet hours through rule sets, which can be assigned to individual actions in campaigns or journeys for precise control. Message export: A new Message Export capability is now available for email and SMS channels. This feature allows you to automatically export sent message content to a dedicated Experience Platform dataset, enabling you to: Meet regulatory compliance requirements (such as HIPAA) Archive messages for legal claims and customer care inquiries Retain copies of personalized content sent to individuals Direct mail channel in orchestrated campaigns: Direct mail channel is now available in orchestrated campaigns. The Direct mail activity facilitates direct mail sending within your Orchestrated campaign, for both one-time and recurring messages. It serves to automate the process of generating the extraction file required by direct mail providers. You can combine channel activities into the Orchestrated campaign canvas to create cross-channel campaigns that can trigger actions based on customer behavior and data. Journey Agent - Create a Journey: Journey Agent now offers creation capabilities, enabling Journey Optimizer users to build and configure marketing journeys through a natural language interface. With these new skills, practitioners can quickly create journeys by simply describing their requirements in conversational prompts. This innovation streamlines the journey creation process, allowing marketers to concentrate on strategy rather than technical configuration. Action campaign retrieval API: A new Journey Optimizer API is now available, enabling you to programmatically retrieve and inspect campaign-related data such as details, versions, and configurations. Email Designer themes: You can now quickly apply pre-approved themes to ensure brand consistency across all emails, speed up your campaign creation process, and independently produce high-quality emails while reducing dependency on design teams. Please find the detailed information around the new capabilities and improvements here: Latest ReleaseFeel free to reach out in case you have any questions and/or feedback through the below comment section.

Please note: This article was originally published on 1/6/26, but was accidentally removed during the Community transition.On Tuesday, March 31, 2026, Marketo Engage will deprecate the Search Engine Optimization feature (SEO).  Why deprecate SEO? When we deprecate older features that have low usage, we can reallocate their resources to newly released and upcoming features, as well as to the overall maintenance of Marketo Engage. This in turn creates an improvement in performance for users across the board.What do I need to do? If you don’t actively use SEO, nothing.  If you have used SEO in the past few months and you want to export your data, it must be done on or before March 31, 2026. All SEO-related data will be removed from the system and the SEO tile will no longer be available as of April 1, 2026.  How to export:  Issues   Keyword Results  Keyword Trends  Competitor Keyword Trends  I still want to use SEO. What tool can I use instead? We recommend Semrush, which offers a comprehensive set of SEO capabilities, including keyword research, competitor analysis, backlink tracking, reporting, and more.  If you have any additional questions, please reach out to our Support Team. 

DetailsThe features in this release focus on Experience Manager Sites, Forms, Assets, and Cloud Foundation innovations and include the following: AEM SITES: Edge Delivery Updates AEM FORMS: Interactive Communications Associate UI AEM ASSETS: AI Search (Multilingual, Semantic) CLOUD FOUNDATION: MCP Server Release Overview Video: https://video.tv.adobe.com/v/3479789/ Seed Q&APlease use this thread to ask questions related to this release.See all the Previous Releases here and the Current Release Notes here.

We’re excited to share that all Prime and Ultimate customers now have access to the Lead Activity and User Audit Marketo Engage Data Streams. Whether you need to sync lead data into your CDP, keep a close eye on asset changes, or are looking to reduce your API load, Data Streams can help you do more with your data with less effort.What are Data Streams?Data Streams let you stream real-time events from Marketo Engage to any system. They send event data directly to your systems as they time, so you don't have to wait for scheduled syncs or manually query for changes.Current streams available:Lead Activity: Send lead-level engagement and activity events (e.g., form fills, list adds) directly from Marketo Engage to other platforms and services. User Audit Events: Stream changes made by users, such as updates to assets, programs, or tokens, to improve compliance across all marketing operations.If you are looking to integrate Marketo with downstream tools such as Snowflake or a homegrown CDP, Data Streams are your perfect solution.Early examples of how customers are using Data Streams:Dual Mastering: Keep a copy of person/lead data in your internal systems (like data lakes and CDPs) that’s always up to date. Webhook Monitoring: Keep an eye on whether actions triggered by webhooks were carried out correctly. Campaign Orchestration: Use real-time engagement data to trigger downstream processes, such as sales alerts.. Compliance & Governance: Get notified when programs or tokens change, and monitor user actions to ensure governance and rollback policies are followed.Access and AvailabilityData Streams have been provisioned for all Prime, Ultimate, and Performance tier customers as of December 2025. If you're on a different package, please reach out to your Adobe Account Team to explore upgrade options.How to Set Up & Start Using Data StreamsOnce your organization has been provisioned with access, here’s how to get up and running:Go to Adobe I/O Events: All setup is done using Adobe I/O Events. Choose your delivery method: Webhooks: Pushes events in near real-time to your endpoint (great for reactive workflows) Adobe Runtime: Serverless event handling with logic inline Amazon EventBridge: Native AWS integration Journaling (on by default): Collects a rolling 7-day event history (ideal for recovery or auditing) Start routing event data to your systems: Follow the setup guides and use the sample code provided in our documentation. More detailed instructions:Marketo Data Streams Documentation Adobe I/O Events Overview Setting up Marketo Lead Activity Data Streams Setting up Marketo User Audit Data StreamsStill need help? Please contact Adobe support for additional assistance. What’s next?We’re continuing to invest in expanding Data Streams and making setup even easier, and we are excited to help you get started with Lead Activity and User Audit today.Have a cool use case? Post it here. We’d love to feature your story and share best practices with others!

We’re excited to introduce the AJO Mobile Learning Hub, a centralized learning destination designed to help you configure, design, launch, and optimize mobile experiences using Adobe Journey Optimizer.Whether you’re just getting started with mobile channels or looking to refine advanced use cases, the hub brings together practical guidance and best practices in one place.Access the AJO Mobile Learning Hubhttps://experienceleague.adobe.com/en/docs/journey-optimizer-learn/mobile-learning-hub/overviewYou can also find it on Experience League under:Learn → Tutorials → Journey Optimizer → Mobile Learning HubWhat you’ll find in the hub Overview and Getting Started Learn about the value of AJO Mobile, review customer examples, and understand how mobile fits into your Journey Optimizer strategy. Configure and Launch (Developers) Step-by-step guidance for enabling mobile channels, including SDK setup, event triggers, and Adobe Experience Platform integration. Design and Deliver (Marketers) Mobile-specific best practices, message design examples, and guidance for building effective mobile use cases. Measure and Optimize (Marketers and Analysts) Tutorials focused on mobile reporting, performance measurement, and optimization workflows. What’s nextWe’ll continue enhancing the Mobile Learning Hub with end-to-end mobile use case walkthroughs, expanded analytics and optimization guidance, and content aligned to newly released and upcoming AJO Mobile capabilities.We’d love your feedback as you explore the hub. Let us know what topics, use cases, or deep dives would be most helpful for you.