CJM-124288 - Further changes for loyalty challenge state change event field group#2093
Merged
waykar-prashant merged 10 commits intoadobe:masterfrom Mar 4, 2026
Merged
Conversation
…s. In particular add a few more fields that would be useful for auditing/reporting
… and fix all the examples.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Polish provided challenge information in loyalty challenge state change event field group.
1. Reward definition and milestones (Loyalty Challenge State)
loyalty.challenge.state.schema.jsonReward definition — The existing
rewardobject is extended with arewardDefinitionsub-object:xdm:denomination(string) — e.g. reward currency/unit (e.g. “Stars”).xdm:enabled(boolean) — whether the reward is enabled.Milestones — A new
xdm:milestonesobject on the challenge:xdm:contiguous(boolean) — whether milestones must be completed in contiguous order.xdm:interval(string) — interval type (e.g. task).xdm:completions(array) — list of milestone completion states; each item hasstate,count, and optionalreward(rewardValue,source).Example updates are reflected in
loyalty.challenge.state.example.1.json.2. Task description tweaks (Loyalty Challenge Task)
loyalty.challenge.task.schema.jsondescriptionand/or field-level descriptions for the task have been updated for clarity and alignment with product (e.g. state, dates, variables, schedule, completion tracking).Deprecated (retained for backward compatibility):
xdm:multiDay— Multi-day visit requirements for task completion (object withcontiguous,days). Replaced by schedule/streak semantics.xdm:currentProgress— Current progress toward task completion (object with quantity, spend, days, qualifiedEvents). Replaced bytaskCompletionsand the new task completion accumulators.Example updates are reflected in
loyalty.challenge.task.example.1.json.3. completionDate on task completions (Loyalty Challenge Task Completion)
loyalty.challenge.taskCompletion.schema.jsonxdm:completionDatefield (string,date-timeformat) indicating when the task was completed.xdm:qtyandxdm:spendfor accumulated quantity and spend (replaces the deprecated top-level fields below).Deprecated (retained for backward compatibility):
xdm:quantity— Total quantity accumulated. Useaccumulators.qtyinstead.xdm:spend— Total spend accumulated. Useaccumulators.spendinstead.xdm:days— Number of qualified days accumulated for this task completion.xdm:qualifiedEvents— List of events that provided progress toward task completion.Example updates are reflected in
loyalty.challenge.taskCompletion.example.1.json.