Integrations
One growth team. Your entire stack.
Markin reads signal where it already lives, decides what deserves to happen for each customer, and writes that decision back into the systems that execute today. Nothing is migrated, nothing is replaced, and switching it off returns every journey to exactly how it behaved before.
Type
36 connections
Warehouses and lakes
Where the customer history lives. Markin reads in place, on your compute, and never copies the base out.
Snowflake
Turn warehouse history into decisions without copying a single row out.
Attribute write-back · Read only
BigQuery
Turn GA4 and transaction data in BigQuery into proven revenue actions.
Attribute write-back · Read only
Databricks
Extend the data science team you already have instead of duplicating it.
Attribute write-back · Read only
Amazon Redshift
Start decisioning on Redshift with a read role and one new schema.
Attribute write-back · Read only
CDPs and activation pipelines
Identity, consent and the pipes that already move rows into channels. Markin produces the rows; your pipeline keeps moving them.
Segment
Give every Segment destination one decided action instead of a raw audience.
Attribute write-back · Triggered event
Hightouch
Feed your existing syncs decisions instead of hand-written audiences.
Attribute write-back
Tealium
Decide which action deserves the contact before Tealium routes it.
Attribute write-back · Triggered event
Census
Ship decisions to every tool through the syncs you already run.
Attribute write-back
RudderStack
Add decisions to a warehouse-native event pipeline.
Attribute write-back · Triggered event
Engagement and CRM
Where lifecycle programmes run. Markin decides what deserves to exist and writes it into the journeys you already operate.
Braze
Decide what deserves to be sent; let Braze send it.
Attribute write-back · Triggered event
Salesforce Marketing Cloud
Put a decided action into a data extension your journeys already read.
Attribute write-back · Triggered event
Adobe Journey Optimizer
Decide which offer should exist, then let Adobe deliver it.
Attribute write-back · Triggered event
HubSpot
Drive existing HubSpot workflows from a decided action.
Attribute write-back · Triggered event
Klaviyo
Decide the moment and the offer; Klaviyo runs the flow.
Attribute write-back · Triggered event
Iterable
Feed Iterable journeys a decision instead of a segment.
Attribute write-back · Triggered event
Optimove
Widen the action set Optimove has to choose from.
Attribute write-back · Triggered event
MoEngage
Decide the action; MoEngage keeps the mobile channel.
Attribute write-back · Triggered event
Airship
Send fewer, better push messages by deciding first.
Attribute write-back · Triggered event · Decision API
Customer.io
Trigger Customer.io campaigns from a decision, not a rule.
Attribute write-back · Triggered event
Twilio
Only send the paid message when the decision justifies its cost.
Decision API · Triggered event
Product analytics and events
Behavioural signal at session granularity, plus the surfaces where an in-session decision is worth the latency.
Amplitude
Turn product analytics findings into actions with a measured verdict.
Read only · Attribute write-back
Mixpanel
Use Mixpanel behaviour as the evidence behind each decision.
Read only
Web and mobile SDK
Decide in-session, at render time, with a fallback that always renders.
Decision API · Direct surface
Google Analytics 4
Use GA4 acquisition and conversion data as decision signal.
Read only
Commerce, billing and subscriptions
The revenue ground truth. Orders, plans, dunning and churn events are what every hypothesis is finally read against.
Stripe
Recover failed payments and protect subscriptions before they lapse.
Read only · Triggered event
Shopify
Decide the next offer per shopper from real order history.
Read only · Triggered event
PrestaShop
Turn PrestaShop commerce data into the next profitable customer action.
Read only · Triggered event · Decision API
Recurly
Choose retry, pause or downgrade before a subscription lapses.
Read only · Triggered event
SAP and ERP systems
Anchor every revenue claim to the system finance already trusts.
Read only
Support and contact centre
Service is a revenue surface. Markin can put the next best action on the agent's screen with the reason attached.
Zendesk
Prioritise the support queue by revenue at risk.
Decision API · Read only
Salesforce Service Cloud
Give the agent one recommended action, with the reason attached.
Decision API · Read only
Intercom
Message in-product only when the decision earns the interruption.
Triggered event · Attribute write-back
Paid media and audiences
Suppression and expansion audiences, sized by expected value rather than by list membership.
Experimentation and feature flags
Where product-side hypotheses get executed. Markin proposes, sizes and reads them like any other action.
Four ways a decision reaches the customer.
The pattern is chosen per surface, not per estate. Latency, cost and who owns the veto are what decide it.
| Pattern | How it works |
|---|---|
| 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. |
| Decision API | The surface asks Markin for a decision at render time and receives one action plus its reason, with a defined fallback. |
| Direct surface | Markin populates a slot in the product or message body directly, for placements where round-tripping through a channel adds nothing. |
Common questions
- 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.
- How reversible is a Markin integration?
- Fully. Decisions arrive as attributes, events or API responses in systems you already own. Switch Markin off and every journey, campaign and surface behaves exactly as it did before, because none of them were rewritten to accommodate it.
- Who enforces frequency caps and consent?
- The systems that already enforce them. Markin supplies intent; the channel keeps its veto over consent, quiet hours, frequency and brand review. That boundary is deliberate, and it is what makes the layer safe to switch on one surface at a time.
Not sure which surface to connect first?
Deployment starts with one surface that already has an outcome signal, and expands once the first holdout has read positive.