To use the feature, the ${candidates.pipelineTag.heading} key must appear in the candidate table header row. The header row will be repeated for each change in pipeline status.
If you use the new key in a report, you must run the report from the ‘Group by:Pipeline tags’ view, or you will get strange results.
Attached is a sample template and an example of how this sample looks with data. Let me know if you have any questions.