While there is a lot of debate on skills PMs should have, ranging from stakeholder management to the ability to not bang your head against a wall, one thing that I have found common across all companies, countries and roles - is the ability to analyse data.
While some companies have analysts to help PMs, lot of places expect PMs to get their hands dirty writing SQL to get their own data. And while many do learn the language and skill to get data, I often find in my discussions, that they miss understanding how the data got there in the first place.
If, like me, you thought that all websites and products have analytics magically built into them, you are just one escalation and bad product review away from getting your bubble burst. I have sat over the years with analysts and engineers in different roles to understand the data pipeline. And after all that - I have finally found an article which explains how it is done in most firms, so that you can avoid that awkward ‘I have no clue what this is’ talk.
This doesnt really help you in achieving any product metric honestly, but given that you work with data day in and day out, it is a good to have knowledge. I will share two articles - the first is how analytics are set up, second is slightly more detailed and technical (though still explained in layman terms) on what is the best practices. I hope you have more authority with your analyst now when they throw words like event, server side, machine learning and other imaginary things.