---
title: Markin + Customer.io
url: https://markin.ai/integrations/customer-io
category: Engagement and CRM
description: Connect Markin to Customer.io: write decision attributes and trigger events into the campaigns you already run.
---

# Markin + Customer.io

> Attributes and events into existing campaigns.

**Job:** Trigger Customer.io campaigns from a decision, not a rule.

A Markin and Customer.io setup writes the decided action into person attributes or emits an event, so the campaigns already built in Customer.io run on a decision with a reason and an expiry attached.

The fastest path from decision to revenue is usually a campaign that already exists and only needs a better audience and a better reason to fire.

## What can you ask Markin to do in Customer.io?

- How do I trigger Customer.io campaigns from a model?
- Can I add next best action to Customer.io?
- How do I stop overlapping Customer.io campaigns?
- How do I test lifecycle messaging against a holdout?

## What Markin does in Customer.io

- Read person attributes, segments and delivery history.
- Read events already tracked into Customer.io.
- Write the chosen action, reason and expiry as attributes.
- Emit events that start the matching campaign.
- Arbitrate so a person receives one action per window.
- Suppress the randomised holdout from every campaign.
- Read conversions back keyed to the decision ID.
- Report incremental revenue per campaign.

## The growth work behind Customer.io

### Read the estate

- Map every customer, account, subscription and plan in the systems you already run.
- Rebuild the revenue baseline from orders, payments, refunds and credits.

### Find where revenue is leaking

- Size every finding in revenue, not in percentage points.
- Watch ARPU by cohort, plan, market, channel and tenure for drift that clears noise.

### Explain why

- Run the investigation automatically and return the drivers with their evidence.
- Separate mix effects from real behaviour change.

### Write hypotheses worth funding

- Attach the expected revenue effect and the population it applies to.
- Attach the evidence and the assumption each one depends on.

### Decide per customer

- Pick the channel, timing and incentive level, not only the message.
- Cap discount and margin exposure at the level finance agreed.

### Execute in the tools you already run

- Route offers, retention plays and save flows to the right surface.
- Open the work as a draft for approval where a human should sign off.

### Prove it caused the revenue

- Read uplift in revenue per customer against that control.
- Report retention, ARPU, margin and contact pressure side by side.

### Retire, govern and hand over

- Hand the team a portfolio they can read, question and overrule.
- Retire programmes automatically when they stop beating control.

Full catalogue: [Everything a growth team does, running every day.](https://markin.ai/growth-work)

## Activation patterns

- **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.

## What Markin reads from Customer.io

- Person attributes and segment membership
- Delivery and conversion metrics

## What Markin writes back

- Person attributes with the action and expiry
- Trigger events

## Used together with

- [segment](https://markin.ai/integrations/segment)
- [stripe](https://markin.ai/integrations/stripe)
- [snowflake](https://markin.ai/integrations/snowflake)
- [amplitude](https://markin.ai/integrations/amplitude)
- [rudderstack](https://markin.ai/integrations/rudderstack)
- [intercom](https://markin.ai/integrations/intercom)

## Related

- [Solution: lifecycle-automation](https://markin.ai/solutions/lifecycle-automation)

## FAQ

**How does Markin connect to Customer.io?**

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 Customer.io?**

Person attributes and segment membership; Delivery and conversion metrics.

**What does Markin write back into Customer.io?**

Person attributes with the action and expiry Trigger events

**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.

Source: https://markin.ai/integrations/customer-io