Problem
The Paid Media class (https://ns.adobe.com/xdm/classes/paid-media) does not appear in the AEP Schema Editor class picker ("Other classes" browse list), even though it is present in the Schema Registry global container and schemas built on it work when created via the Schema Registry API.
Root cause
components/classes/paid-media.schema.json is missing meta:tags. Every XDM class that surfaces in the UI class picker carries an industry vertical tag:
"meta:tags": { "industry": ["all"] }Comparing all 30 classes in the repo: profile, experienceevent, and summarymetrics (all browsable) each carry meta:tags.industry. The classes that lack meta:tags are the internal/system classes (campaign, consentpolicy, segmentdefinition, graphs, weather, …) — plus paid-media. The Schema Editor groups/filters available global classes by industry vertical, so an untagged global class has no bucket to render under: reachable by $id via API, absent from the UI browse list. This matches the observed symptom exactly.
Proposed fix (additive, non-breaking)
Add an industry tag to the class so it is offered in the class picker:
"meta:tags": { "industry": ["all"] }
components/classes/paid-media.schema.json
Metadata-only, additive — no properties, types, or enum values change; no example updates required.
If tagging alone does not surface the class after registry ingest, the Schema Editor class list may have an additional curation/allowlist gate owned by the Schema Registry / Schema Editor UI team, which would be followed up separately.
Problem
The
Paid Mediaclass (https://ns.adobe.com/xdm/classes/paid-media) does not appear in the AEP Schema Editor class picker ("Other classes" browse list), even though it is present in the Schema Registry global container and schemas built on it work when created via the Schema Registry API.Root cause
components/classes/paid-media.schema.jsonis missingmeta:tags. Every XDM class that surfaces in the UI class picker carries an industry vertical tag:Comparing all 30 classes in the repo:
profile,experienceevent, andsummarymetrics(all browsable) each carrymeta:tags.industry. The classes that lackmeta:tagsare the internal/system classes (campaign,consentpolicy,segmentdefinition,graphs,weather, …) — pluspaid-media. The Schema Editor groups/filters available global classes by industry vertical, so an untagged global class has no bucket to render under: reachable by$idvia API, absent from the UI browse list. This matches the observed symptom exactly.Proposed fix (additive, non-breaking)
Add an industry tag to the class so it is offered in the class picker:
components/classes/paid-media.schema.jsonMetadata-only, additive — no properties, types, or enum values change; no example updates required.
If tagging alone does not surface the class after registry ingest, the Schema Editor class list may have an additional curation/allowlist gate owned by the Schema Registry / Schema Editor UI team, which would be followed up separately.