You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add new dimension to MBD and potentially DiamondHands endpoints to help partners identify if low score is due to poor quality transactions or lack of transactions
#3130
Open
lebraat opened this issue
Dec 11, 2024
· 0 comments
As a partner
I want to better understand if a low score coming from MBD or DiamondHands is due to low transaction volume or poor transactions
So that I can adjust how I treat the user.
Acceptance Criteria
GIVEN a request to the MBD or DiamondHands API (tbd)
WHEN a user scores low
THEN a secondary field can help me understand if this is due to low transaction volume or poor transactions
Add a new '-1' response that indicates no or insufficient data to score
Add new dimension to MBD and potentially DiamondHands endpoints to help partners identify if low score is due to poor quality transactions or lack of transactions
The text was updated successfully, but these errors were encountered:
User Story:
As a partner
I want to better understand if a low score coming from MBD or DiamondHands is due to low transaction volume or poor transactions
So that I can adjust how I treat the user.
Acceptance Criteria
GIVEN a request to the MBD or DiamondHands API (tbd)
WHEN a user scores low
THEN a secondary field can help me understand if this is due to low transaction volume or poor transactions
Add a new '-1' response that indicates no or insufficient data to score
Add new dimension to MBD and potentially DiamondHands endpoints to help partners identify if low score is due to poor quality transactions or lack of transactions
The text was updated successfully, but these errors were encountered: