---
title: Markin + Salesforce Marketing Cloud
url: https://markin.ai/integrations/salesforce-marketing-cloud
category: Engagement and CRM
description: Connect Markin to Salesforce Marketing Cloud: decisions land in data extensions and existing journeys read them as entry criteria.
---

# Markin + Salesforce Marketing Cloud

> Data extensions receive the decision; journeys stay untouched.

**Job:** Put a decided action into a data extension your journeys already read.

A Markin and Salesforce Marketing Cloud setup lands decisions in a dedicated data extension. Existing journeys read it as entry criteria, so the decision layer arrives without a single journey being rewritten.

Rebuilding an SFMC estate is a multi-year project nobody wants. Writing into a data extension means the decision layer arrives without any journey being rewritten.

## What can you ask Markin to do in Salesforce Marketing Cloud?

- How do I add next best action to Salesforce Marketing Cloud?
- Can I trigger an SFMC journey from a model decision?
- How do I modernise SFMC without a replatform?
- How do I measure incrementality of SFMC journeys?

## What Markin does in Salesforce Marketing Cloud

- Read journey exposure and send logs.
- Read contact and subscriber attributes.
- Write rows into a dedicated data extension.
- Send API events that trigger a journey with a reason attached.
- Apply arbitration so two journeys never target the same contact.
- Maintain a randomised holdout as a suppression list.
- Read conversions back keyed to the decision ID.
- Report incremental revenue per journey.

## The growth work behind Salesforce Marketing Cloud

### 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

- Refuse to call a result that has not cleared the evidence standard.
- Publish the readout in the same place for every experiment.

### 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 Salesforce Marketing Cloud

- Journey exposure and send logs
- Contact and subscriber attributes

## What Markin writes back

- Rows in a dedicated data extension
- API events that trigger journeys

## Used together with

- [salesforce-service-cloud](https://markin.ai/integrations/salesforce-service-cloud)
- [snowflake](https://markin.ai/integrations/snowflake)
- [hightouch](https://markin.ai/integrations/hightouch)
- [stripe](https://markin.ai/integrations/stripe)
- [segment](https://markin.ai/integrations/segment)
- [amplitude](https://markin.ai/integrations/amplitude)

## Related

- [Solution: lifecycle-automation](https://markin.ai/solutions/lifecycle-automation)
- [Comparison](https://markin.ai/compare/markin-and-salesforce)

## FAQ

**How does Markin connect to Salesforce Marketing Cloud?**

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 Salesforce Marketing Cloud?**

Journey exposure and send logs; Contact and subscriber attributes.

**What does Markin write back into Salesforce Marketing Cloud?**

Rows in a dedicated data extension API events that trigger journeys

**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/salesforce-marketing-cloud