# Customer and member 360 with reverse ETL

> A customer or member 360 on DataNature unifies core systems, digital channels and CRM into one governed profile. AI360 Studio adds segments, propensity and churn scores and next-best actions, then pushes them to CRM and marketing tools with reverse ETL, without a second copy of customer data.

Source: https://datanature.ai/solutions/customer-360-reverse-etl
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-05

One profile, scored and pushed to the tools your teams use

## Components

- **Connect**: Core, digital and CRM data
- **AI360 Studio**: Identity, segments, scores and next-best actions
- **DataNature AI**: Feature store and model serving
- **Reverse ETL**: Sync to CRM and engagement tools

## Steps

1. **Unify**: Land and match customer records across systems.
2. **Model**: Build features, segments and scores.
3. **Activate**: Sync audiences and scores to CRM and campaigns.
4. **Measure**: Track outcomes back in the lakehouse.

## Documentation

- [Machine learning](https://docs.datanature.ai/docs/developers/ai-and-analytics/machine-learning)

## How is this different from a SaaS CDP?

The profile lives in your governed lakehouse, in your jurisdiction. There is no second copy in a third-party tool.

## What can teams do with it?

Cross-sell, retention, collections prioritization, member profitability and service briefings.

## Do marketers need SQL?

No. Audiences are built and synced in AI360 Studio.

## Common questions

### What is reverse ETL?

Sending modelled data from the lakehouse back into CRM, marketing and service tools.

### What is a customer 360?

One governed profile of each customer built from every channel. See [member 360 for credit unions](/blog/member-profitability-and-customer-360-for-credit-unions).

## Is this a customer data platform?

Yes. Customer 360 with reverse ETL is the composable customer data platform pattern: collect, resolve identities, build one profile, score and segment, then activate in the tools teams already use. AI360 Studio adds consent-aware activation and real-time profiles through StreamHouse and Lakebase, and the whole CDP can run in your jurisdiction. Read [the AI360 CDP architecture, step by step](/blog/customer-data-platform-architecture-ai360-lakehouse).

## Implementation details

1. **Ingest customer sources** (core systems, CRM, digital channels) into Bronze; use StreamHouse for interactions that must be fresh in seconds.
2. **Resolve identity** in Silver: match records across systems into one customer key, and keep the match rules in dbt.
3. **Build the profile** in Gold: attributes, product holdings, behavioural aggregates.
4. **Score** churn, propensity and lifetime value with models tracked in the DataNature AI registry; store scores in Gold with the model version.
5. **Segment and decide** in AI360 Studio.
6. **Push back** to operational tools with reverse ETL, and serve low-latency lookups from Lakebase for apps and agents.
7. **Mask PII** for analysts with hash masks so profiles stay joinable without exposing identity.
