User story · Persona: Program team. The program team needs visibility into how often notifications actually drive the desired action, so that reminder strategy effectiveness can be measured and tuned over time. 

Link every relevant downstream action with any notification that preceded it within a configurable window, and expose an endpoint that turns that link into measurable effectiveness numbers. 

• Attribution linkage: When a downstream action occurs (ASHA claim submission, ASHA resubmission, Verify ASHA-Month at Supervisor, CHO, or ANM stage, Reject ASHA-Month at Supervisor, CHO, or ANM stage), the audit log entry for that action must record whether a relevant notification was dispatched to the same actor within a configurable attribution window before the action. Recommended default: 7 days. Event-type to action mapping defines "relevant" (ASHA Submission Reminder to ASHA claim submission; Supervisor Verification Reminder to Supervisor Verify or Reject; CHO and ANM Verification Reminders to CHO or ANM Verify or Reject; ASHA Claim Rejected to ASHA resubmission). Attribution window configurable per event type via the configuration surface from Ticket P3.1. 

• Reporting endpoint: Backend query or report endpoint returning, for a given date range, notifications dispatched, viewed, tapped, dismissed, and cleared; number followed by the expected action within the attribution window; effectiveness ratio per event type and recipient role. Output as JSON for an analytics backend or CSV for spreadsheet review. 

• Affected modules: Notification service (attribution writer). Notification log datastore (attribution fields). Audit log datastore (linkage to notification log). Reporting backend (new endpoint).