Skip to content

CJM-141473: Add isBot boolean field to messageInteraction schema#2182

Open
deepansh90 wants to merge 1 commit into
adobe:masterfrom
deepansh90:CJM-141473-isbot-boolean-field
Open

CJM-141473: Add isBot boolean field to messageInteraction schema#2182
deepansh90 wants to merge 1 commit into
adobe:masterfrom
deepansh90:CJM-141473-isbot-boolean-field

Conversation

@deepansh90
Copy link
Copy Markdown

@deepansh90 deepansh90 commented May 26, 2026

Additive boolean field for bot detection. Does not change the interactionType enum — click/open values are preserved unchanged.

Summary

Adds an additive isBot boolean field to message-interaction under
extensions/adobe/experience/customerJourneyManagement/. Marks a recipient
interaction (click/open) as identified by bot detection. Field is absent
when false; no backfill required for historical events. The interactionType
enum is preserved unchanged.

This is the schema layer for CJM-141473 (replacement design for the
destructive bot_click/bot_open enum approach that caused PLATIR-63838 /
PLATIR-64150 on May 8–12). Paired with:

  • cjm/tracker#605 — Tracker stops emitting BOT_CLICK / BOT_OPEN; sets messageInteraction.isBot = true on bot-detected clicks
  • AresSolutionConfig/ares_ajo_config#181sm_ajo_outboundBotClicks backed by composite derived field (isBot=true ∧ interactionType=click ∧ entityType=message)

Explicitly out of scope

Field design

Field Type Required Semantics
isBot boolean no true ⇒ this interaction was identified as automated/non-human. Absent or false ⇒ human (or unknown).

Additive boolean field for bot detection. Does not change the
interactionType enum — click/open values are preserved unchanged.
Absent field is equivalent to false; no historical backfill needed.
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.

2 participants