How does Markin connect to Segment?

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 Segment?

Unified profiles and identity graph; Track and identify events; Consent state.

What does Markin write back into Segment?

Computed traits carrying the chosen action and its reason Decision events for downstream destinations

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.

Markin + Segment

Identity and consent stay yours; decisions flow through.

Segment resolves who the customer is. Markin decides what should happen to them. Writing the decision back as a trait means every destination you already configured inherits it without new plumbing.

Attribute write-backTriggered event

What Markin reads

Unified profiles and identity graph
Track and identify events
Consent state

What Markin writes back

Computed traits carrying the chosen action and its reason
Decision events for downstream destinations

How the connection works

Activation patterns used with Segment
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

Segment questions

How does Markin connect to Segment?: 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 Segment?: Unified profiles and identity graph; Track and identify events; Consent state.
What does Markin write back into Segment?: Computed traits carrying the chosen action and its reason Decision events for downstream destinations
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.