Question for AJO Client Side vs. Server Side Personalization
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
I ran both samples in the Client-Side Personalization and Server-Side Personalization. It seems that the Client Side (Web SDK) is sending in the Proposition Action Type, as well as the Array of Tokens that are clicked or displayed. The Server-Side (configured with the AEP Edge Client) doesn't seem to do this. It only sends back the ID, Scope, and Scope Details.
Is that intentional? Do the disposition events (click and display) have different formats depending on the Channel they are coming through?
Thanks,
Billy
Contributor guide
Research direction
Compare the Client-Side Personalization and Server-Side Personalization samples, starting with how each returns proposition data through the Web SDK and AEP Edge Client. Determine whether action types and clicked or displayed token arrays intentionally differ by channel, then document the confirmed disposition-event formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100