Typically, a project manager has authority over resource allocation and resource planning, but must defer to the stakeholders for everything else (most importantly, for actual design/implementation decisions). A product manager has authority over the complete lifecycle of his product, including design, implementation and resource allocation.
One would have to articulate a lot to make a point about a project manager being directly associated with sales/revenue etc. -- the top line. "Oh yeah, the project manager can increase customer satisfaction and then contribute to upselling, especially in companies focused on farming and not much on hunting customers!" -- I agree, but it's rare now.
- Reads Jira (or whatever) and moves things around (yes, they may also add things sometimes, but I'm drawing a general distinction).
- Gantt charts.
- Tracks project status, communicates it upward.
- May also do some communicating expectations downward.
- Translates blunt assessments of the project's progress into managerese.
- May have some responsibility for keeping development processes going, especially ones that involve lots of communication (think: Agile shit, or just project status meetings generally)
- Helps unblock process-related shit.
Product manager:
- Writes to Jira a lot.
- Does market research, or works closely with those who do.
- Guides the direction of the product (e.g. which feature do we tackle next, do we pivot).
- Works closely with key stakeholders (clients, product owners, domain experts) to determine that direction.
- Sells that direction to management and such.
- May have some significant sway on final decisions for e.g. design.
- May do quite a bit of business-model analysis.
But PM/PMM roles can vary a fair bit.