Home/
How CJA Data View component settings reshape a raw schema field at report time — a visual overview plus an interactive inspector for all eight setting types.
Settings live in the Data View, not the schema — applied at report time, retroactively.
Raw column from AEP
Becomes a component
Shape how it behaves
Reports at run time
Retroactive & non-destructive
Settings never alter underlying data. They reinterpret it at query time, so changes apply backward across all existing history.
Admins only
Product admins create, edit, and delete data views. Regular users cannot edit or view data views — only consume the components inside them.
One field, many components
Drag the same column in twice with different settings — e.g. a Revenue field can become both an Orders metric and a Revenue metric simultaneously.
Settings matrix
Dimension only
Persistence
allocation, expiration & binding
No value options
rename, hide, treat as value
Value bucketing
group numerics into ranges
Substring
left/right, delimiter, URL parse, trim, regex
Lower case
behavior setting
Metric only
Format
decimal, time, percent, currency, trend color
Attribution
model, container & lookback window
Metric deduplication
scope, dedup ID, value to keep
Count values vs instances
behavior setting
Both
Include / exclude values
filter values at query time
Core header
type, name, ID, tags, context labels
Hide component in reporting
Workspace override behaviour
Can override in Workspace
Locked to data view