Updated event type from personalization.request to decisioning.propositionFetch#159
Merged
akhiljain1907 merged 3 commits intoJun 25, 2026
Conversation
mohdashraf010897
added a commit
to adobe/griffon-toolkit
that referenced
this pull request
Jun 18, 2026
…quests Mobile SDKs are migrating the XDM eventType used to fetch propositions from the deprecated `personalization.request` to `decisioning.propositionFetch`, aligning Mobile with the XDM spec already used by Web SDK. Both SDK PRs are open: - Optimize: adobe/aepsdk-optimize-ios#159 - Messaging: adobe/aepsdk-messaging-ios#491 (in-app, content cards, CBE) Assurance must match events from both old and new SDK builds, so the affected matchers now accept either eventType (additive — no break for existing sessions). Changes: - New personalizationFetchEventTypes.ts: exports LEGACY_EDGE_EVENT_TYPE, PROPOSITION_FETCH_EDGE_EVENT_TYPE, and edgeEventTypeMatcher (combineAny of both values). Single source of truth for all three matchers. - optimizeMessagesRequest.ts, personalizationEdgeRequest.ts, iamMessagesRequest.ts: replace the hardcoded personalization.request JMESPath clause with edgeEventTypeMatcher; export the new constants. - personalizationEdgeRequest.json schema: widen const -> enum [both]. optimize + iam schemas inherit this via allOf, so all three are covered. - index.ts: re-exports personalizationFetchEventTypes. - Version bump: 0.13.0 -> 0.14.0 (additive, no breaking changes). All three matchers (optimize, edge, IAM) covered now — Messaging SDK #491 is open, so accepting the new type in the IAM matcher is forward-ready and safe (legacy type still matches today). Tests: 11/11 pass (2 existing sharedStateConfig + 9 new across all three matchers + constants). MOB-25095 / MOB-24547 / PLATIR-51299
4 tasks
sagar-sharma-adobe
approved these changes
Jun 25, 2026
ishwetansh
approved these changes
Jun 25, 2026
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
3 participants
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.
MOB-24547
PLATIR-51299
Description
Desktop and Mobile SDKs are using "personalization.request" to fetch decisions. This is deprecated and should be replaced with "decisioning.propositionFetch".
Table of valid event types:
https://experienceleague.adobe.com/en/docs/experience-platform/xdm/classes/experienceevent
Related Issue
Motivation and Context
How Has This Been Tested?
Tested AEPOptimize SDK with personalization requests being sent with event type as decisioning.propositionFetch instead of personalization.request. Passed decision scope for both Target and Offer Decisioning and retrieved offers for both. Also compared the Tracking payload sent for Display and Click for corresponding offers.
Assurance session - https://experience.adobe.com/#/@aemonacpprodcampaign/data-collection/assurance/session/b22ec762-9a8b-4094-bc0e-20fe819c0651/view/event-list
Screenshots (if appropriate):
Types of changes
Checklist: