How-to guideDataAvailable
Output Targets
Attach transformation outputs to user, event, session, or account properties in the Data Catalog.
Last reviewed July 13, 2026
Every transformation can attach its output to a specific property in the Data Catalog. Output targets define where computed values appear so downstream tools — reports, segments, destinations, and the Agent — can use them.
Target types
| Target | Where it appears | Example |
|---|---|---|
| User property | User Properties in the Data Catalog | predicted_ltv, churn_risk_score |
| Event property | Event Properties in the Data Catalog | attributed_channel, sentiment_label |
| Session property | Session-level attributes | session_value_tier |
| Account property | Account- or organization-level attributes | account_health_score |
Select the target type when creating or editing a transformation.
Rule-based vs precomputed
Both execution modes write to the same catalog properties:
| Mode | When values are computed | Best for |
|---|---|---|
| Rule-based | At query time (SQL CASE) | Simple logic, always current |
| Precomputed | On a schedule or after source sync | Heavy aggregations, ML scores |
From the user’s perspective, both appear as properties in the Data Catalog. The difference is internal execution timing.
Using outputs downstream
Once attached to a catalog property, transformation outputs are available to:
- Segments — build audiences from computed properties
- Destinations — sync properties to external tools
- Insights — include in cross-channel reporting
- Agent — query and analyze in conversation
- MCP tools — access programmatically from external AI tools
Related
- Transformations
- Customer 360 — built-in calculated property templates
- Data Catalog — browse all properties
Last updated on