---
title: Markin + Adobe: prioritising the opportunity before personalisation
url: https://markin.ai/compare/markin-and-adobe
kind: stack
description: Adobe Real-Time CDP and Journey Optimizer unify profiles and personalise in the moment. Markin decides which opportunity deserves that moment.
updated: 2026-09-03
---

# Markin + Adobe: prioritising the opportunity before personalisation

> Adobe Experience Platform unifies profiles in Real-Time CDP and orchestrates personalised experiences through Journey Optimizer. Markin sits before the moment of personalisation and decides which commercial opportunity deserves it for each customer, and what it is worth. Adobe still owns the profile, the journey and the experience.

## In short

- Adobe Experience Platform: How do we deliver a personalised experience to this profile, in this moment? Output: Personalised experiences, journey state, audience activation and reporting.
- Markin, the decision + execution layer: Which opportunity is worth this customer's attention, and what is it worth to the business? Output: A ranked, sized decision per customer, returned as the input to the experience.
- A better-personalised version of the wrong offer is still the wrong offer.
- It decides which opportunity deserves one, then hands that decision to Adobe so the journey and personalisation machinery does what it is good at.

## What each layer is

**Adobe Experience Platform**, An enterprise experience stack: Real-Time CDP for unified profiles and audiences, and Journey Optimizer for orchestrating and personalising journeys and in-the-moment experiences across channels.

Answers: How do we deliver a personalised experience to this profile, in this moment?

**Markin, the decision + execution layer**, A layer that ranks commercial opportunities per customer, sizes the revenue at stake, chooses the treatment expected to move it, and holds when nothing has positive expected value.

Answers: Which opportunity is worth this customer's attention, and what is it worth to the business?

## Side by side

|  | Adobe Experience Platform | Markin, the decision + execution layer |
| --- | --- | --- |
| Question it answers | How do we deliver a personalised experience to this profile, in this moment? | Which opportunity is worth this customer's attention, and what is it worth to the business? |
| Primary input | Ingested events and records, unified profiles, audiences, journey and offer configuration. | Unified context, outcome history, margin, contact cost, constraints, experiment results. |
| Primary output | Personalised experiences, journey state, audience activation and reporting. | A ranked, sized decision per customer, returned as the input to the experience. |
| Usual owner | Marketing operations and experience teams. | Growth, data science and revenue leadership. |
| How it's measured | Engagement, journey performance, personalisation lift within the experience. | Incremental revenue and ARPU against a holdout. |

## What a full Adobe estate still leaves open

Personalisation answers how an experience should be tailored once you have decided to deliver it. The prior question,  of everything we could put in front of this customer, which one is commercially worth the moment, is usually settled by audience rules and a campaign calendar.

- A better-personalised version of the wrong offer is still the wrong offer.
- Audience qualification is rule-based; concurrent qualification is resolved by suppression and priority ordering, not by expected value.
- Experience-level lift is measured within the channel, rarely as incremental revenue across everything the customer received.
- The rate of new commercial hypotheses is bounded by the operations backlog, not by the data.

## How the two run together

1. **Context in.** Markin reads unified customer context,  Real-Time CDP profiles alongside warehouse, product and billing data, plus the outcome history required to learn from past treatments.
2. **Decision.** Opportunities are generated, sized and ranked per customer. A treatment is chosen, a control group assigned and an expected value attached before anything is delivered.
3. **Activation back into Adobe.** The decision returns as a profile attribute or event, so Journey Optimizer selects and personalises the experience. Content, channel and experience design stay with Adobe.

## Adobe's own decisioning layer

Products: Journey Optimizer AI Decisioning, Offer Decisioning, Real-Time CDP, Adobe AI Assistant

Adobe has the most complete decisioning product of the group: real-time ranking, journey arbitration, frequency capping, experimentation and global control groups. It is also the only vendor here that publishes the hard limits of that engine, and those limits describe an offer-catalogue architecture rather than an opportunity-generation one.

**What it optimises**

- AJO AI decisioning combines a real-time decision engine, AI ranking of options by likelihood of engagement, eligibility constraints, frequency capping and AI model insights reporting conversion or revenue lift. [Vendor page: Adobe, Journey Optimizer AI decisioning](https://business.adobe.com/products/journey-optimizer/ai-decisioning.html)
- Adobe ships experimentation with global control groups,  an automatically held-out subset used to measure true impact, plus send-time optimisation, with AI journey path, channel and arbitration optimisation flagged as coming soon. [Vendor page: Adobe, Journey Optimizer AI decisioning](https://business.adobe.com/products/journey-optimizer/ai-decisioning.html)

**Documented constraints**

- Adobe publishes decisioning guardrails: a maximum of 10,000 decision items, item size capped at 1KB with 30 attributes, 500 items per collection and 30 decision items returned per policy. [Vendor docs: Adobe Experience League, Decisioning guardrails](https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/decisioning-guardrails)
- Further documented ceilings: a maximum of 5 AI ranking models, 1,000 placements, 10 decision policies per email, and 1,500 to 5,000 decision requests per code-based experience API call depending on Edge segmentation. [Vendor docs: Adobe Experience League, Decisioning guardrails](https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/decisioning-guardrails)
- Full value depends on Adobe Experience Platform and Real-Time CDP being the customer data foundation underneath Journey Optimizer. [Vendor page: Adobe, Journey Optimizer AI decisioning](https://business.adobe.com/products/journey-optimizer/ai-decisioning.html)

**Evidence**

- Adobe was named a Leader in the 2026 Gartner® Magic Quadrant™ for Personalization Engines (published 3 February 2026), a genuine independent report, though the promotional framing is Adobe's selection from it. [Analyst report: Gartner® Magic Quadrant™ for Personalization Engines (2026)](https://business.adobe.com/resources/reports/gartner-mq-personalization-engines-2026.html)
- Adobe's AI model insights surface conversion and revenue lift for your own programmes, but no aggregate customer uplift benchmark is published. [Vendor page: Adobe, Journey Optimizer AI decisioning](https://business.adobe.com/products/journey-optimizer/ai-decisioning.html)

**Where Markin differs**

- **Opportunities are generated, not catalogued.** Adobe ranks items from a decision catalogue someone has to author and maintain within published limits. Markin generates and sizes the opportunity from customer context, so the space of things worth doing is not capped by a catalogue.
- **Above the platform, not inside it.** Markin runs on the warehouse alongside AEP rather than requiring the full Experience Platform footprint before decisions can be made, and writes decisions back into AJO for delivery.
- **Ranked on money, not engagement likelihood.** AI ranking orders options by likelihood of engagement. Markin orders them by expected incremental revenue net of cost, which is why not contacting can win.

## What Markin does not replace

To be explicit about scope, because procurement will ask:

- Markin does not deliver experiences, emails or on-site personalisation.
- Markin does not replace Real-Time CDP profiles or the identity graph.
- Markin does not manage consent, data governance or brand controls.
- Markin does not replace Journey Optimizer; it supplies the decision that starts the right journey.

## Where Markin fits

Markin does not build experiences. It decides which opportunity deserves one, then hands that decision to Adobe so the journey and personalisation machinery does what it is good at. The enterprise governance you have already implemented does not move.

- **The decision precedes the experience.** Journey entry becomes a ranked opportunity with an expected value rather than an audience rule, so personalisation is applied to the offer worth making.
- **Governance stays in place.** Profiles, consent, data governance and brand controls remain Adobe's. Markin reads context in place and writes decisions back.
- **Revenue-level proof.** Each decision carries a holdout, so the number reported to the business is incremental revenue rather than in-channel lift.

Next: [Next-Best Action](https://markin.ai/solutions/next-best-action)

## When Markin is not the right answer

- Your priority is improving creative and experience quality rather than choosing between commercial opportunities.
- You lack the outcome history required to size opportunities or evaluate treatments.
- You want to consolidate vendors. This layer adds a decision capability; it does not remove an experience platform.

## FAQ

**Adobe Journey Optimizer already has AI decisioning. Why add a layer?**

Adobe's decisioning is the most complete in the category: real-time ranking, eligibility rules, frequency capping, experimentation with global control groups, and a 2026 Gartner Magic Quadrant Leader placement for Personalization Engines. It is also catalogue-based, and Adobe publishes the ceilings, 10,000 decision items, 30 items returned per policy, 5 AI ranking models, 1,000 placements. Markin generates and sizes opportunities from customer context instead of ranking a maintained catalogue, then writes the chosen decision into AJO.

**Do we have to replace Adobe?**

No. Adobe remains the profile and experience layer. Markin decides which opportunity deserves the moment and returns that decision so Journey Optimizer can execute and personalise it.

**Real-Time CDP already has audiences and offers. Why add a decision layer?**

Audiences describe who qualifies and offer management describes what can be shown. Neither estimates the incremental revenue of acting, ranks competing opportunities by expected value, or enforces a holdout by default.

**How does the decision reach Journey Optimizer?**

As a profile attribute or event that journeys can key off, so the experience team works with the interfaces they already use.

**Does this create a governance problem?**

It should not. Consent and eligibility rules are treated as hard constraints on what Markin may decide, and every decision is auditable with the reason and expected value attached.

**How is Markin different from the decisioning or AI already inside Adobe?**

A decisioning engine ranks actions a human already defined, inside the campaign surface it was given. Markin forms the hypotheses itself,  marketing, product, pricing or a technical anomaly holding growth back, sizes them, executes them inside Adobe and your product surfaces, and reads each one against a randomised holdout. It behaves like a data science and growth team, not like an optimiser.

**Does Markin only test messages and offers?**

No. Anything a human growth scientist would investigate is in scope: onboarding friction, feature adoption, pricing and packaging, dunning, and technical health issues such as a checkout error rate or a broken deeplink quietly killing conversion. Marketing is one of four hypothesis domains, not the boundary.

**What is the business case for adding Markin on top of Adobe?**

On the assumptions preloaded above, 8.0M customers at 32 a month, a small move in ARPU is a large number in absolute terms, because it applies to the whole installed base every month rather than to a campaign. Across Markin deployments the verified range on treated cohorts is +17% to +35% ARPU against a randomised holdout. The point is not more messages: it is finding the highest-value action per customer, launching it, and proving it against control before it scales.

**How long before it pays for itself?**

First sized opportunities are in test within six weeks and the first holdout-verified result lands inside 90 days. Payback depends on your base, margin and programme cost, the calculator on this page computes it from your own numbers, after applying the 20% to 40% haircut BCG finds when next-best-action programmes are incrementality-tested.

Source: https://markin.ai/compare/markin-and-adobe