Skip to content

Add Decisioning Content data type for ExD Offer Content Personalization#2120

Open
kmmraju wants to merge 1 commit intoadobe:masterfrom
kmmraju:CJM-135243-support-decisioning-content-datatype
Open

Add Decisioning Content data type for ExD Offer Content Personalization#2120
kmmraju wants to merge 1 commit intoadobe:masterfrom
kmmraju:CJM-135243-support-decisioning-content-datatype

Conversation

@kmmraju
Copy link
Copy Markdown
Contributor

@kmmraju kmmraju commented Mar 26, 2026

https://jira.corp.adobe.com/browse/CJM-135243

Summary

  • Introduces a new XDM data type decisioning-content under extensions/adobe/experience/decisioning/ to support expression-based content personalization in decisioning offers.
  • The schema defines a content field with:
    • contentType — an enum (text, json, html) indicating how the expression should be interpreted
    • expression — a string containing the dynamic content expression
  • Includes two example files validating text and HTML content types.

Motivation

As part of the ExD Offer Content Personalization initiative (Techspec), decisioning offers need a standardized way to define dynamic content fields with expression-based personalization. This data type enables offers to carry content expressions in multiple formats (plain text, HTML, JSON), allowing the decisioning engine to render personalized content at delivery time.

Files Changed

File Description
decisioning-content.schema.json New XDM data type schema with contentType enum and expression string
decisioning-content.example.1.json Example: text content type
decisioning-content.example.2.json Example: HTML content type

Test Plan

  • npm test — all 2131 mocha tests pass (schema loads and validates against meta-schema)
  • ajv validate — both examples validate against the schema
  • Invalid content (missing required fields) correctly rejected by schema validation

Introduces a new XDM data type `decisioning-content` to support expression-based
content personalization in decisioning offers. The schema defines a content field
with a contentType enum (text, json, html) and an expression string, enabling
dynamic content rendering across different media formats.

Techspec: https://wiki.corp.adobe.com/spaces/CJM/pages/3757303279/ExD+Offer+Content+Personalization+Techspec
Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant