Markin + Adobe Journey Optimizer
Profile attributes and events into the Adobe estate.
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.
Attribute write-backTriggered event
What Markin reads
- Experience Platform profile attributes
- Journey step events
What Markin writes back
- Profile attributes with the committed action
- Journey trigger events
How the connection works
| Pattern | What it means here |
|---|---|
| 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. |
Where this shows up
Adobe Journey Optimizer questions
- 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.