Step by step: create and enable a dataset
- Create the dataset from an existing schema.
- Decide whether it should feed Profile. Enable the schema first, then the dataset.
- Ingest a small test batch or stream and check batch status and failed records.
- Confirm profiles and identities appear as expected before loading full history.
- Apply data usage labels for governance and set retention where available.
Common use cases
- CRM profile attributes (Profile-enabled record dataset).
- Web and app events collected with Web SDK (Profile-enabled event dataset).
- Historical or analytical data used only in Query Service or CJA (not Profile-enabled).
Troubleshooting checklist
- Batch failed: check the error preview for type mismatches and missing required fields.
- Data in the dataset but not in profiles: confirm both schema and dataset are enabled for Profile and that records carry a valid primary identity.
- Dataset missing in CJA: confirm it is added to a CJA connection with the correct person ID.
- Unexpected volumes: review duplicate ingestion from multiple sources.
Who this guide is for
This guide is written for beginners, students and career switchers who want a clear mental model, and for developers, data engineers, implementation specialists, consultants, architects, marketers, agencies and enterprise teams who need practical, step-by-step detail they can apply on real projects.
Frequently asked questions
Should every dataset be enabled for Profile?
No. Enable only data that is needed for real-time profiles, segmentation or personalisation. Analytical or archival data can stay in the data lake.
Last updated: