adobe / adobe/target-nodejs-sdk
visitorState properties
- Dominant language
- JavaScript
- Stars
- 26
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I am not sure if this is the best place to ask this, hope someone can help me:
The `visitorState` returned by the node SDK does not contain the 'AppMeasurement:1' property under `supplementalDataIDCurrentConsumed`, this is set with a value of true once consumed in the front-end, but because the API does not provide this property at all or its default value, then it stays as true for the remaining of the session, we then need to manually set it on our end to false or delete the property on every SDK getOffers request for new sdid's to be consumed.
I was wondering if this was intended behaviour, as the scenarios I can think of, the current state in the client is usually merged with the response of the server
Contributor guide
Research direction
Start with the node SDK's visitorState returned by getOffers, focusing on supplementalDataIDCurrentConsumed and the missing AppMeasurement:1 property. Reproduce whether the property is omitted for new SDIDs and determine the expected default or merge behavior; done when the SDK behavior is defined and the client no longer needs to reset it manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100