Reintroduce Loyalty changes (CJM-115123) #2054
Open
+340
−1
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.
This PR includes 2 sets of changes needed for storing customers' loyalty data in AEP:
The data will typically come from the customer's Loyalty Management System, 3rd party or otherwise.
Profile Loyalty Field Group Changes
We are adding the following fields:
Experience Event Loyalty Field Group
This field group is for tracking loyalty transactions, which are usually tied to an end user's commercial transaction. Loyalty transactions are typically dependent on the commercial transaction's details, so Loyalty Management Systems conversely receive them from the customer and use them as input when resolving the loyalty program's business logic.
For example, the end user is trying to use a 10% off coupon while buying a $500 power tool. The Loyalty management system will need both the coupon code and the shopping cart to figure out:
This field group would therefore be typically used together with a commercial transaction tracking field group, for example the Commerce Details field group, to capture the full transaction details.
Fields