eventual consistency versus strong consistency. when do you pick which one?

Hey everyone, I've been wrestling with a design decision and wanted to get your input. We're building a new feature and need to decide on our consistency model. Some data, like financial transactions, *really* needs to be in sync immediately. But other data, user profile updates for example, could tolerate a slight delay. How do you all handle this? Do you have a go-to rule for when eventual consistency is 'good enough' versus when you absolutely need strong consistency? And what patterns do you use to manage this trade-off?