Markin + LaunchDarkly
Feature flags as an execution channel for growth hypotheses.
Some of the largest ARPU changes are product changes, not messages. Treating a flag as a channel puts them in the same queue and under the same measurement discipline.
Decision API
What Markin reads
- Flag definitions and exposure logs
What Markin writes back
- Per-user targeting decisions with holdouts preserved
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. |
LaunchDarkly questions
- How does Markin connect to LaunchDarkly?
- Decision API. 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 LaunchDarkly?
- Flag definitions and exposure logs.
- What does Markin write back into LaunchDarkly?
- Per-user targeting decisions with holdouts preserved
- 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.