Quick Verdict
Adobe Sensei should no longer be presented as a standalone purchasable AI product. It is the legacy umbrella Adobe introduced in 2016 for machine-learning capabilities across its portfolio. Those capabilities have not all disappeared; they have moved behind clearer product brands and licenses. As of July 20, 2026, buyers should evaluate Adobe Firefly for generative creative workflows; Adobe Experience Platform (AEP), AI Assistant, Experience Platform Agents, and Agent Orchestrator for customer data and marketing agents; Adobe Target for experimentation and personalization; Journey Optimizer for journey decisions; and Acrobat AI Assistant for document interaction. Older references to Sensei or Sensei GenAI remain useful history but are not a current SKU, unified feature list, or pricing plan. This page is therefore a migration guide. The directory should eventually demote or remove the standalone card and route discovery to current Adobe products.
Best For
- Enterprises mapping older Adobe architecture, contracts, or documentation to current products.
- Existing Experience Cloud customers evaluating AI in AEP, Target, or Journey Optimizer.
- Creative Cloud customers evaluating Firefly and enterprise creative governance.
- Global marketing technology teams that need shared data labels, sandboxes, approvals, and audits.
- Not appropriate for a new buyer seeking an independent “Adobe Sensei account” or inexpensive AI app.
Key Features
- Creative AI moved to Firefly: Generative image, video, audio, design, Generative Fill, and enterprise custom-model questions should be assessed against Firefly and Creative Cloud entitlements. Generative credits, model policies, training terms, brand customization, and indemnity depend on the plan.
- Experience intelligence moved to AEP: AEP AI Assistant supports product knowledge and data insight, while Experience Platform Agents and Agent Orchestrator address multi-step audience, journey, experimentation, content, and site-optimization work. Agent, region, and release availability must be checked for the customer’s tenant.
- Testing remains in Adobe Target: Target includes A/B testing, Auto-Allocate, Auto-Target, Automated Personalization, and recommendations. Fixed randomization is suited to causal questions; automated allocation and model-based personalization optimize live decisions but do not produce an identical estimate.
- Prediction is embedded in Experience Cloud: Propensity, audience, journey, and next-best-experience capabilities are licensed through specific products. A Sensei label in an old interface or document does not imply a shared Sensei console.
- Governance is product-specific: Adobe products provide roles, sandboxes, data-use labels, policies, auditability, Content Credentials, and enterprise controls. Customers still configure consent, sensitive data, use limitations, human approval, and deletion.
- Attribution and data quality: AEP, Analytics, Target, and Journey Optimizer can share identities and events. Teams must align exposure, randomization units, attribution windows, and identity stitching rather than merging attribution, propensity scores, and experiment effects.
Use Cases
A marketing team can organize lawfully collected customer data in AEP, orchestrate journeys in Journey Optimizer, and run a randomized holdout in Target for a page or recommendation policy. An Experimentation Agent or AI Assistant may help investigate data and propose work, but an experiment owner should approve the hypothesis, audience, outcomes, and stopping rule. A creative team can generate or edit assets with Firefly, then pass them through brand rules, Content Credentials, rights review, and human publishing approval.
Cross-product attribution requires documented event sources, identity resolution, deduplication, and observation windows. A propensity score is not an observed intention. Automated personalization should not use sensitive traits or proxy variables without a lawful basis, meaningful notice, fairness review, and a fallback experience. Marketing attribution should not be reported as randomized incremental lift.
Pricing
Adobe Sensei has no standalone price, free edition, or universal trial. Licensing follows the actual product. Experience Cloud products are commonly sales-quoted; public Creative Cloud, Firefly, and Acrobat plans vary by region, generative credits, seats, and enterprise terms.
| Current purchasing entry | Capabilities inherited or replaced | Confirm in procurement |
|---|---|---|
| Adobe Firefly / Creative Cloud | Generative creation, editing, content supply chain | Credits, models, training policy, custom brand models, and indemnity |
| Adobe Experience Platform | Customer data, AI Assistant, agents, and governance | Licenses, data volume, sandboxes, queries, agents, and regions |
| Adobe Target | A/B, automated allocation, personalization, recommendations | Visits, activities, models, metrics, implementation, and services |
| Journey Optimizer | Cross-channel journeys, decisions, and messaging | Message volume, channels, decisions, consent, and frequency caps |
| Acrobat AI Assistant | Document questions and summaries | Seats, document handling, enterprise controls, and availability |
Do not accept “Sensei included” as a sufficient order description. Ask the vendor to name each application, AI entitlement, usage meter, data region, implementation service, preview feature, support level, and renewal term.
Pros
- Legacy Sensei capabilities were largely productized rather than simply switched off.
- Firefly integrates deeply with Adobe’s creative production applications.
- AEP, Target, and Journey Optimizer can share customer-experience data and governance context.
- Target supports randomized tests, automated allocation, personalization, and recommendations.
- Enterprise products provide foundations for roles, sandboxes, policies, audits, and human approval.
- Buyers can choose the Adobe product aligned to a concrete workflow instead of a vague AI layer.
Cons
- The Sensei name no longer identifies a product that can be evaluated or purchased coherently.
- Capabilities are distributed across several expensive products with complex licensing and implementation.
- Agents, AI Assistant features, and Firefly capabilities can roll out by tenant, region, and release stage.
- Cross-product data design across AEP, Target, Analytics, and journeys requires specialist teams.
- Personalization, propensity scores, and generated content create bias, privacy, and intellectual-property risks.
- Keeping a standalone Sensei directory card can mislead new buyers and dilute current Adobe product pages.
Alternatives
| Tool | Better fit | Main difference |
|---|---|---|
| Adobe Firefly | Generative creative and Creative Cloud workflows | A current, purchasable Adobe AI product entry |
| Optimizely | Independent experimentation, flags, and marketing agents | Clearer current product boundaries than the legacy Sensei umbrella |
| Dynamic Yield | Retail recommendations and omnichannel personalization | Experience OS and Mastercard Element focus on commerce decisions |
| Monetate | Enterprise testing, recommendations, and secure deployment | Symphony, Maestro, and Forte map directly to procurement |
| Salesforce Einstein | Salesforce CRM data and agent workflows | Tighter coupling to Salesforce objects and permissions |
FAQ
Was Adobe Sensei discontinued?
“Discontinued” is too simple. As an independent market and procurement entry, it has been superseded by specific product brands. Many machine-learning capabilities continue inside Adobe applications. Check Target, AEP, Firefly, or another product rather than searching for a Sensei plan.
Can a customer still buy Adobe Sensei?
Not as one standalone SKU. First determine whether the need is creative generation, customer data, experimentation, personalization, journey orchestration, or document AI, then price the corresponding Adobe product.
Is Firefly the new name for Sensei?
No. Firefly is Adobe’s current generative creative AI brand. Sensei covered a much wider range of machine learning. Many Experience Cloud capabilities are not part of a Firefly purchase.
Is Adobe Target automated personalization the same as A/B testing?
No. A/B testing uses predefined random allocation to estimate a variant effect. Automated personalization selects experiences using features and models. They can complement each other but need different statistical interpretation and control designs.
Does Adobe AI guarantee marketing lift?
No. Models and automation execute or support decisions. Incremental effects require an appropriate randomized experiment, uncertainty estimates, and business guardrails. Case studies and attribution dashboards are not an ROI guarantee.
Should this directory delete the Adobe Sensei entry?
After preserving a migration explanation, yes: demote or remove the standalone card, or permanently label it historical. Search and recommendations should favor Adobe Firefly and specific Experience Cloud products to avoid misleading buyers.
Bottom Line
Adobe Sensei’s accurate status is “legacy AI umbrella whose capabilities migrated into products,” not “standalone Adobe AI platform still for sale.” Use this page only to map the old name to Firefly, AEP, Target, Journey Optimizer, and Acrobat AI Assistant. Neither legacy Sensei nor current Adobe AI, experimentation, and personalization capabilities guarantee conversion, growth, or ROI; results still require appropriate randomized controls, uncertainty estimates, attribution rules, and business guardrails. Evaluate each product’s data, region, governance, release status, and contract separately. Marketing, data, creative, and finance owners remain responsible for permissions, consent, publishing approval, platform and media budgets, and final content or business decisions. The directory should subsequently clean up or demote this standalone card.