Background / Issue
Users see a list of supportive services on the application confirmation page, tailored to their predicted risk level (“At risk” or “Not at risk”). However, we’re currently not capturing any data on which links are actually clicked. This limits our insight into which resources are helpful or engaging, and which ones may need to be revisited or replaced.
Technical Context
This would involve implementing logging for when a user clicks a resource link. Data should include the risk classification group, the name of the resource, and which specific URL was visited. This will help inform future iterations of the resource set and ensure we’re driving users toward the most effective support.
Acceptance Criteria
QA Notes
- Confirm that clicking any resource link from the confirmation page triggers a logged event.
- Test with both “At risk” and “Not at risk” flows.
- Validate that events include meaningful metadata.
Background / Issue
Users see a list of supportive services on the application confirmation page, tailored to their predicted risk level (“At risk” or “Not at risk”). However, we’re currently not capturing any data on which links are actually clicked. This limits our insight into which resources are helpful or engaging, and which ones may need to be revisited or replaced.
Technical Context
This would involve implementing logging for when a user clicks a resource link. Data should include the risk classification group, the name of the resource, and which specific URL was visited. This will help inform future iterations of the resource set and ensure we’re driving users toward the most effective support.
Acceptance Criteria
QA Notes