Markin + Web and mobile SDK
In-session decisions rendered into your own surfaces.
Some surfaces cannot wait for a sync interval. A paywall or home screen slot asks at render time and gets one answer, and the surface always renders even when Markin does not answer.
Decision APIDirect surface
What Markin reads
- Session context passed at request time
What Markin writes back
- One action plus its reason, per request, with a fallback default
How the connection works
| Pattern | What it means here |
|---|---|
| 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. |
Where this shows up
Web and mobile SDK questions
- How does Markin connect to Web and mobile SDK?
- Decision API, Direct surface. The surface asks Markin for a decision at render time and receives one action plus its reason, with a defined fallback.
- What does Markin read from Web and mobile SDK?
- Session context passed at request time.
- What does Markin write back into Web and mobile SDK?
- One action plus its reason, per request, with a fallback default
- 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.