Agree an explicit mapping (yes/y/true/1 → true; no/n/false/0 → false) and treat anything else as an error to investigate, not as false. Apply it during ingestion, and log how many rows fell outside the mapping. For consent, prefer the dedicated consent field groups over a home-made boolean.

Error Library / AEP

XDM error: boolean field got "yes", "Y" or "1"

What you seeField 'authenticated' expected type 'boolean' but got 'yes'

XDM boolean fields take true or false. Values like "yes", "Y", "TRUE" (as text) or "1" come from spreadsheets and CRMs and need converting.

Why it happens

CSV has no real boolean type, so every exporter picks its own words.
Consent and authentication flags are the usual offenders, and they matter: a consent flag read wrongly is a compliance problem, not just a failed row.

How to fix it

Agree an explicit mapping (yes/y/true/1 → true; no/n/false/0 → false) and treat anything else as an error to investigate, not as false.
Apply it during ingestion, and log how many rows fell outside the mapping.
For consent, prefer the dedicated consent field groups over a home-made boolean.

Before and after

Fails

{ "authenticated": "yes" }

Works

{ "authenticated": true }

Common questions

Is an empty value false?

No. Empty means unknown; leave the field out rather than guessing false.

Practise the fix

Build the Customer Profile

Reproduce this error in your own AEP practice workspace, fix it, and earn a verifiable credential for the skills involved: XDM schema design, Identity descriptors, Real-Time Customer Profile enablement, Dataset configuration.

See the Lab plan

Related errors

XDM error: number field received text (currency symbols, commas)

Batch ingestion: columns missing from the dataset after upload

AdsBot is an independent training provider, not affiliated with Adobe. Behaviour can differ between ingestion methods and product versions; always test with a small batch first.