A heatmap answers one question well: where's it dense, and where's it empty, across two categorical axes at once. Plot hour of day against day of week and you can spot exactly when a gym fills up (Monday at 6pm, Wednesday at 6am) in one glance that a bar chart would need fifty-six separate bars to match. Or plot signup cohort against month and you get a retention grid that shows churn patterns a line chart would blur into a tangle of overlapping series.
PlotSet currently ships one heatmap template, built around a straightforward category-by-category matrix: a row category, a column category, and a numeric value in each cell. That single template covers most real use cases, from attendance patterns to correlation matrices to survey score grids, because the data shape is flexible even though the chart type itself isn't. What actually changes from case to case is the color scale, not the chart: sequential for a plain count that only goes up from zero, diverging when values can fall above or below a baseline.
Color choice matters more here than in most chart types, because color is the entire encoding. Get it wrong and the chart misleads. Perceptually uniform scales, where equal steps in the data produce equal-looking steps in color, are the safer default; rainbow scales exaggerate some ranges and flatten others, which is why most modern data-viz style guides have moved away from them. Around 8% of men have some form of red-green color blindness, so a red-to-green diverging scale is a real accessibility problem, not a nitpick.