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.
32
documented connections
4
activation patterns
0
systems replaced or migrated
Type
32 connections
Warehouses and lakes
Where the customer history lives. Markin reads in place, on your compute, and never copies the base out.
Snowflake
Scores every customer against the ARPU model on your own warehouse compute, nightly.
Attribute write-back · Read only
BigQuery
Builds the opportunity feed from event and revenue tables without exporting a single row.
Attribute write-back · Read only
Databricks
Runs propensity and uplift models next to the feature tables your team already maintains.
Attribute write-back · Read only
Amazon Redshift
Reads order and subscription history in place to size each hypothesis.
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
Turns a decision into a computed trait your existing destinations already read.
Attribute write-back · Triggered event
Hightouch
Ships the decision table to every downstream tool your syncs already cover.
Attribute write-back
Tealium
Writes the next best action as an audience attribute inside your existing badge logic.
Attribute write-back · Triggered event
Census
Syncs Markin's decision table to the channels without new pipeline work.
Attribute write-back
RudderStack
Emits the decision as an event your existing routing already fans out.
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
Decides which of forty possible messages a customer deserves this week, then hands Braze the one that wins.
Attribute write-back · Triggered event
Salesforce Marketing Cloud
Fills the journey entry attribute so your existing programmes select the right customers.
Attribute write-back · Triggered event
Adobe Journey Optimizer
Supplies the offer and the reason; AJO keeps the orchestration and the consent veto.
Attribute write-back · Triggered event
HubSpot
Puts the expansion play and its expected value on the record the rep is already looking at.
Attribute write-back · Triggered event
Klaviyo
Replaces send-to-everyone flows with a per-customer decision and a live holdout.
Attribute write-back · Triggered event
Iterable
Chooses the action per customer; Iterable keeps frequency caps and quiet hours.
Attribute write-back · Triggered event
Customer.io
Triggers the journey only for customers where the model says it pays.
Attribute write-back · Triggered event
Twilio
Reserves the expensive channel for the cases where the expected value covers the 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
Turns a behavioural anomaly into a sized, testable hypothesis within the day.
Read only · Attribute write-back
Mixpanel
Detects the funnel step where revenue is leaking and proposes what to change.
Read only
Web and mobile SDK
Answers the in-session decision call in milliseconds, with a defined fallback.
Decision API · Direct surface
Google Analytics 4
Cross-checks the site-side read against the warehouse before a result is trusted.
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
Reads payment and dunning ground truth so every read is against revenue, not clicks.
Read only · Triggered event
Shopify
Decides the cross-sell that does not cannibalise the order the customer would have placed anyway.
Read only · Triggered event
Recurly
Times the plan-change offer against real renewal and churn dates.
Read only · Triggered event
SAP and ERP systems
Grounds every hypothesis in billed revenue rather than in tracked events.
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
Puts the next best action, and its reason, on the agent's screen mid-ticket.
Decision API · Read only
Salesforce Service Cloud
Turns a service contact into a sized retention or expansion moment.
Decision API · Read only
Intercom
Chooses whether a conversation deserves an offer, a fix or nothing at all.
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.