---
title: Markin + Census
url: https://markin.ai/integrations/census
category: CDPs and activation pipelines
description: Connect Markin to Census: Markin writes decisions to the warehouse and your existing Census syncs activate them downstream.
---

# Markin + Census

> Decision tables synced by the pipeline you already trust.

**Job:** Ship decisions to every tool through the syncs you already run.

A Markin and Census setup uses a table as the integration surface. Markin writes decisions to the warehouse; Census syncs them to the tools that need them. Turning the sync off returns the estate to exactly its previous state.

The integration surface is a table, not an API contract. That keeps the connection reversible: turn the sync off and the estate is exactly as it was.

## What can you ask Markin to do in Census?

- How do I activate model output through Census?
- Can Census sync a next best action to Salesforce and Braze?
- How do I keep an AI decision layer reversible?
- What table shape should a decision sync use?

## What Markin does in Census

- Read sync definitions and field mappings.
- Write decision tables in the shape the syncs already read.
- Attach a reason and an expiry to every decided action.
- Keep holdout membership beside the decision to prevent leakage.
- Recompute idempotently so re-syncs never duplicate sends.
- Version each write so a bad batch can be rolled back.
- Leave delivery, retries and alerting with Census.
- Remove the table and nothing downstream changes shape.

## The growth work behind Census

### Read the estate

- Derive behavioural features from event history without a new pipeline.
- Reconcile the same customer across billing, CRM, product and support identities.

### Find where revenue is leaking

- Detect churn risk building in a segment before it shows in the monthly number.
- Detect involuntary churn from failed payments, card expiry and retry behaviour.

### Explain why

- Show the counter-evidence, not only the supporting cut.
- Keep the query trail so an analyst can reproduce every number.

### Write hypotheses worth funding

- Keep the full portfolio visible, including what was deliberately not funded.
- Write hypotheses continuously across marketing, product, pricing and technical health.

### Decide per customer

- Attach a plain-language reason and an expiry to every decision.
- Suppress an action rather than send a weak one, and log why.

### Execute in the tools you already run

- Recompute idempotently so a replay never double-sends.
- Roll a decision batch back cleanly when something looks wrong.

### Prove it caused the revenue

- Report retention, ARPU, margin and contact pressure side by side.
- Detect and discount cannibalisation between competing actions.

### Retire, govern and hand over

- Keep personal data in your systems and act on it in place.
- Show the whole decision trail when legal, finance or an auditor asks.

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.

## What Markin reads from Census

- Sync definitions and field mappings

## What Markin writes back

- Warehouse decision tables consumed by existing syncs

## Used together with

- [snowflake](https://markin.ai/integrations/snowflake)
- [bigquery](https://markin.ai/integrations/bigquery)
- [braze](https://markin.ai/integrations/braze)
- [hubspot](https://markin.ai/integrations/hubspot)
- [klaviyo](https://markin.ai/integrations/klaviyo)
- [salesforce-marketing-cloud](https://markin.ai/integrations/salesforce-marketing-cloud)

## Related

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

## FAQ

**How does Markin connect to Census?**

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.

**What does Markin read from Census?**

Sync definitions and field mappings.

**What does Markin write back into Census?**

Warehouse decision tables consumed by existing syncs

**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/census