Improved
Cloud Connect V2 data models — Activated Fields and permission-aware Field Mappings
7 days ago
The V2 data model config form now brings back Activated Fields from V1, letting you declare them directly when you build a Cloud Connect audience, and it adapts the Field Mappings section to your permissions so the form is clearer about what you can edit.
What's new
- Activated Fields — back from V1, this lets you pick the source columns you want Lytics to activate, and Lytics automatically creates the matching schema fields populated by this data model. Options are drawn straight from the columns your SQL query returns, so you only choose from fields that actually exist in your results.
- Permission-aware Field Mappings — if your role doesn't include schema management, the Field Mappings section now stays visible but read-only, with a clear note that schema management permissions are required to edit it. Activated Fields and the rest of the configuration remain fully editable, so you can still build and save the model.
See Creating Cloud Connect Audiences for the full data model configuration walkthrough.