---
title: Markin + Adobe Journey Optimizer
url: https://markin.ai/integrations/adobe-journey-optimizer
category: Engagement and CRM
description: Connect Markin to Adobe Journey Optimizer: write decisions into Experience Platform profiles and trigger journeys with a reason attached.
---

# Markin + Adobe Journey Optimizer

> Profile attributes and events into the Adobe estate.

**Job:** Decide which offer should exist, then let Adobe deliver it.

A Markin and Adobe Journey Optimizer setup writes committed decisions into Experience Platform profiles and triggers journeys with the reason attached. Adobe ranks offers you configured; Markin decides whether an offer should exist and proves it against a holdout.

Adobe's own decisioning ranks offers you have configured. Markin decides whether an offer should exist at all, and proves the answer against a holdout before it scales.

## What can you ask Markin to do in Adobe Journey Optimizer?

- How does Adobe Journey Optimizer decisioning compare to a decision layer?
- Can I write a next best action into Adobe Experience Platform profiles?
- How do I prove incremental revenue from AJO journeys?
- How do I generate new offer ideas rather than ranking existing ones?

## What Markin does in Adobe Journey Optimizer

- Read Experience Platform profile attributes.
- Read journey step and delivery events.
- Propose new candidate actions, not only rankings of configured offers.
- Write the committed action onto the profile with its reason.
- Emit journey trigger events.
- Maintain randomised holdouts inside the profile store.
- Read outcomes back keyed to the decision ID.
- Report incremental revenue per journey and per offer.

## The growth work behind Adobe Journey Optimizer

### Read the estate

- Reconcile the same customer across billing, CRM, product and support identities.
- Read consent, subscription and channel eligibility state before anything else.

### Find where revenue is leaking

- Detect involuntary churn from failed payments, card expiry and retry behaviour.
- Spot onboarding steps where activation falls off and revenue never starts.

### Explain why

- Keep the query trail so an analyst can reproduce every number.
- Run the investigation automatically and return the drivers with their evidence.

### Write hypotheses worth funding

- Write hypotheses continuously across marketing, product, pricing and technical health.
- Attach the expected revenue effect and the population it applies to.

### Decide per customer

- Suppress an action rather than send a weak one, and log why.
- Choose the next best action for each customer, for each moment.

### Execute in the tools you already run

- Roll a decision batch back cleanly when something looks wrong.
- Leave the estate exactly as it was if Markin stops writing.

### Prove it caused the revenue

- Stop an experiment early when the evidence is conclusive either way.
- Refuse to call a result that has not cleared the evidence standard.

### Retire, govern and hand over

- Show the whole decision trail when legal, finance or an auditor asks.
- Hand the team a portfolio they can read, question and overrule.

Full catalogue: [Everything a growth team does, running every day.](https://markin.ai/growth-work)

## Activation patterns

- **Attribute write-back.** Markin writes the decision onto the customer profile; your existing journeys read it as an entry condition. Latency is the platform's sync interval.
- **Triggered event.** Markin emits an event that starts or advances a journey. Near-immediate, and the channel keeps its own governance.

## What Markin reads from Adobe Journey Optimizer

- Experience Platform profile attributes
- Journey step events

## What Markin writes back

- Profile attributes with the committed action
- Journey trigger events

## Used together with

- [snowflake](https://markin.ai/integrations/snowflake)
- [segment](https://markin.ai/integrations/segment)
- [amplitude](https://markin.ai/integrations/amplitude)
- [stripe](https://markin.ai/integrations/stripe)
- [google-ads](https://markin.ai/integrations/google-ads)
- [optimizely](https://markin.ai/integrations/optimizely)

## Related

- [Solution: next-best-action](https://markin.ai/solutions/next-best-action)
- [Comparison](https://markin.ai/compare/markin-and-adobe)

## FAQ

**How does Markin connect to Adobe Journey Optimizer?**

Attribute write-back, Triggered event. Markin writes the decision onto the customer profile; your existing journeys read it as an entry condition. Latency is the platform's sync interval.

**What does Markin read from Adobe Journey Optimizer?**

Experience Platform profile attributes; Journey step events.

**What does Markin write back into Adobe Journey Optimizer?**

Profile attributes with the committed action Journey trigger events

**Do we have to move our data to Markin?**

No. Markin reads from your warehouse, product events and operational systems in place, on your compute, under the access rules your data team already set. Nothing is copied into a separate customer base and there is no vendor-side profile store to migrate off later.

**Does Markin replace our engagement platform or CDP?**

No, and it should not. Your engagement platform keeps the channel, the templates, the deliverability and the governance. Your CDP keeps identity and consent. Markin adds the layer neither has: deciding which action deserves to exist for each customer, and proving it against a holdout.

**What if the system we use is not listed?**

The four activation patterns cover almost everything: attribute write-back, triggered event, decision API and direct surface rendering. Any system that exposes an API, accepts a table, or can read a warehouse column can receive decisions. New connectors are built during deployment, typically in days.

Source: https://markin.ai/integrations/adobe-journey-optimizer