Create schema field groups
Last update: February 14, 2025
- Topics:
- Schemas
CREATED FOR:
- Beginner
- Developer
This video shows how to create schema field groups in Adobe Experience Platform. Schema field groups are reusable components that define most fields in Experience Data Model (XDM) schemas. For more information, please visit the schemas documentation.
Transcript
In this video, I’ll show you how to build your own schema field groups in Adobe Experience Platform. Schema field groups are groups of fields used to build Experience Platform data models and are usually organized around a theme. For example, you could have a field group for loyalty data, paid search marketing details, or dining reservation details. Platform comes with many field groups out of the box, reflecting common industry data model best practices. Sometimes though, you may have your own specific modeling requirements which aren’t met by the out-of-the box field groups. In these circumstances, you can easily create your own field groups to meet your needs. I’ll show you how to create a field group in the Platform interface, although you can also create these via the API as well. I’ll log into the Platform interface and select Schemas in the left navigation. I can click the Field groups tab to see all of the field groups in my account, and can use the filter to see the ones that I’ve created. Field groups are created in the schema editor. So, I can either start the process to build the new schema or open an existing schema. While designing the data model for Luma, our retail demo brand, we realized we needed a custom class for our brick and mortar store details. We created a class containing our StoreId field, and we’ll now create a field group for the store contact details. I’ll create a new schema using my custom store class. Next, I’m prompted to add a field group. Field groups are almost always tied to a specific class. So, while there are field groups that contain address information, they won’t be compatible with my new Store class. There are a few standard groups that we make available to all classes, which is what we see here. I want to create a new field group, so I click Create new field group and give it a name and description. Now, I can start adding fields wherever I’d like to in this schema. I’ll add a field at the root level. Note that custom fields are always namespaced under my organization’s tenant ID to prevent collisions with standard fields. Now, although I can’t use other standard field groups for my class, I can access any of the standard data types. I can quickly add my postal address details by adding the Postal address data type which contains a number of relevant fields. I can quickly do the same for phone number. Note that the field names should all be one word and you need to assign a display name, which should be a friendly name so that downstream users, like marketers, can easily find the relevant fields when doing things like building segments off of them. For my Store Name field. I’ll use a more generic data type string. When I save my schema, the new field group will be saved and it will be reusable in any other schema sharing the same base class. So, that’s how to create field groups in Adobe Experience Platform, good luck. -
Previous pageCreate classes
Next pageCreate data types
Experience Platform
- Platform Tutorials
- Introduction to Platform
- A customer experience powered by Experience Platform
- Behind the scenes: A customer experience powered by Experience Platform
- Experience Platform overview
- Key capabilities
- Platform-based applications
- Integrations with Experience Cloud applications
- Key use cases
- Basic architecture
- User interface
- Roles and project phases
- Introduction to Real-Time CDP
- Getting started: Data Architects and Data Engineers
- Authenticate to Experience Platform APIs
- Import sample data to Experience Platform
- Administration
- AI Assistant
- Audiences and Segmentation
- Introduction to Audience Portal and Composition
- Upload audiences
- Overview of Federated Audience Composition
- Connect and configure Federated Audience Composition
- Create a Federated Audience Composition
- Audience rule builder overview
- Create audiences
- Use time constraints
- Create content-based audiences
- Create conversion audiences
- Create audiences from existing audiences
- Create sequential audiences
- Create dynamic audiences
- Create multi-entity audiences
- Create and activate account audiences (B2B)
- Demo of streaming segmentation
- Evaluate batch audiences on demand
- Evaluate an audience rule
- Create a dataset to export data
- Segment Match connection setup
- Segment Match data governance
- Segment Match configuration flow
- Segment Match pre-share insights
- Segment Match receiving data
- Audit logs
- Data Collection
- Collaboration
- Dashboards
- Data Governance
- Data Hygiene
- Data Ingestion
- Overview
- Batch ingestion overview
- Create and populate a dataset
- Delete datasets and batches
- Map a CSV file to XDM
- Sources overview
- Ingest data from Adobe Analytics
- Ingest data from Audience Manager
- Ingest data from cloud storage
- Ingest data from CRM
- Ingest data from databases
- Streaming ingestion overview
- Stream data with HTTP API
- Stream data using Source Connectors
- Web SDK tutorials
- Mobile SDK tutorials
- Data Lifecycle
- Destinations
- Destinations overview
- Connect to destinations
- Create destinations and activate data
- Activate profiles and audiences to a destination
- Export datasets using a cloud storage destination
- Integrate with Google Customer Match
- Configure the Azure Blob destination
- Configure the Marketo destination
- Configure file-based cloud storage or email marketing destinations
- Configure a social destination
- Activate through LiveRamp destinations
- Adobe Target and Custom Personalization
- Activate data to non-Adobe applications webinar
- Identities
- Intelligent Services
- Monitoring
- Partner data support
- Profiles
- Understanding Real-Time Customer Profile
- Profile overview diagram
- Bring data into Profile
- Customize profile view details
- View account profiles
- Create merge policies
- Union schemas overview
- Create a computed attribute
- Pseudonymous profile expirations (TTL)
- Delete profiles
- Update a specific attribute using upsert
- Privacy and Security
- Introduction to Privacy Service
- Identity data in Privacy requests
- Privacy JavaScript library
- Privacy labels in Adobe Analytics
- Getting started with the Privacy Service API
- Privacy Service UI
- Privacy Service API
- Subscribe to Privacy Events
- Set up customer-managed keys
- 10 considerations for Responsible Customer Data Management
- Elevating the Marketer’s Role as a Data Steward
- Queries and Data Distiller
- Overview
- Query Service UI
- Query Service API
- Explore Data
- Prepare Data
- Adobe Defined Functions
- Data usage patterns
- Run queries
- Generate datasets from query results
- Tableau
- Analyze and visualize data
- Build dashboards using BI tools
- Recharge your customer data
- Connect clients to Query Service
- Validate data in the datalake
- Schemas
- Overview
- Building blocks
- Plan your data model
- Convert your data model to XDM
- Create schemas
- Create schemas for B2B data
- Create classes
- Create field groups
- Create data types
- Configure relationships between schemas
- Use enumerated fields and suggested values
- Copy schemas between sandboxes
- Update schemas
- Create an ad hoc schema
- Sources
- Use Case Playbooks
- Experience Cloud Integrations
- Industry Trends