Markin + Intercom
In-app conversations as a decision surface.
In-app messaging is cheap to send and expensive in attention. Arbitration keeps the surface useful instead of exhausting it.
Triggered eventAttribute write-back
What Markin reads
- Conversation history and resolution outcomes
- User attributes
What Markin writes back
- Attributes and events that trigger targeted conversations
How the connection works
| Pattern | What it means here |
|---|---|
| Triggered event | Markin emits an event that starts or advances a journey. Near-immediate, and the channel keeps its own governance. |
| 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. |
Intercom questions
- How does Markin connect to Intercom?
- Triggered event, Attribute write-back. Markin emits an event that starts or advances a journey. Near-immediate, and the channel keeps its own governance.
- What does Markin read from Intercom?
- Conversation history and resolution outcomes; User attributes.
- What does Markin write back into Intercom?
- Attributes and events that trigger targeted conversations
- 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.