[abhinavdahiya060918]

Summary

Closes #2266

Adds five optional string fields to the Customer Journey Management Message Interaction field group (_experience.customerJourneyManagement.messageInteraction), so AJO open/click tracking events can record the recipient's device type, operating system and browser:

• deviceType: device category; known values documented via meta:enum: mobile, tablet, desktop, other (a recognised device of another kind, e.g. TV, games console, eReader), unknown (device lookup ran but couldn't identify it)
• operatingSystem: OS name (e.g. iOS, Android, Windows, macOS), or unknown
• operatingSystemVersion: OS version (e.g. 17.4), or unknown
• browserName: browser or app name (e.g. Chrome, Safari), or unknown
• browserVersion: browser or app version (e.g. 124.0), or unknown

Non-breaking: additive only; no existing fields changed or removed. deviceType is a soft enum (meta:enum only, no JSON Schema enum), so no values are rejected.

Supersedes #2255 (original commit cherry-picked with authorship preserved, plus review fixes).

Motivation

AJO customers need native device-, OS- and browser-level data (mobile vs desktop, iOS vs Android, Chrome vs Safari, …) for email opens and clicks in AJO and CJA reports. AJO's Tracker service builds the open/click Experience Events itself and writes them under messageInteraction. Until these fields exist in the field group, AEP drops them at ingestion.

The fields sit alongside the existing messageInteraction.isBot (#2192), which follows the same flat pattern and producer:

• Producer: Adobe-CJM/tracker (open/click tracking), gated per org behind a feature flag. Device, OS and browser come from Experience Edge Device Lookup.
• Values:
  • deviceType is normalized to mobile / tablet / desktop; any other recognised device type becomes other.
  • unknown means the lookup ran but couldn't determine the value (unrecognised user agent, partial result, failure or timeout).
  • A field is left out entirely when the lookup didn't run for that org.
• Browser fields are captured now; surfacing them in AJO reporting is a later step.

Changes

• extensions/adobe/experience/customerJourneyManagement/message-interaction.schema.json: add deviceType (string + meta:enum), operatingSystem, operatingSystemVersion, browserName, browserVersion (strings) under messageInteraction.
• extensions/adobe/experience/customerJourneyManagement/message-interaction.example.4.json: add the five fields to the example that already covers isBot.
• docs/reference/adobe/experience/customerJourneyManagement/message-interaction.schema.json: same five fields, kept identical to the extensions copy (following CJM-141473: Add isBot boolean field in messageInteraction schema #2192).

Validation

• npm test: 2455 passing, 1 pending
• npm run lint: clean
• npm run validate: no failures in the changed schema (pre-existing failures elsewhere unchanged vs master)
• npm run incompatibility-check: clean

Breaking changes

None. Additive-only, so no CHANGELOG.md entry is needed.

Related

• Jira: CJM-146679 / CJM-51156
• Producer: Adobe-CJM/tracker#717 (writes the fields); Experience Edge Konductor forwards the Device Lookup values
• Precedent: CJM-141473: Add isBot boolean field in messageInteraction schema #2192 (messageInteraction.isBot)