Do you ignore churn feedback when it goes against your core product vision?

Collecting cancellation reasons from users is super easy but deciding what to actually fix is a constant headache. We once had a bunch of users leaving because they wanted a specific PDF export format even though our tool was built entirely around web-first dashboards. If we listened to every single complaint, we would have ended up building a completely different software.

How do you draw the line between giving users what they ask for versus sticking to your original product direction?