> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pressmaster.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Track growth and reach across every channel

> See impressions, engagement, and follower growth across every connected channel, benchmarked against creators your size.

![Growth tab showing impressions, engagement, audience journey, and follower growth across connected channels](https://mintcdn.com/pressmaster/VUgATWkXe0iANkbN/images/performance-growth.png?fit=max\&auto=format\&n=VUgATWkXe0iANkbN\&q=85\&s=fbf4cd5054a89b88b0c7420d7267ec4a)

The Growth tab shows how your audience and reach are trending across every connected channel, and how that compares to similar-size creators.

## Growth benchmark

At the top of the tab, Pressmaster shows the percentage of similar-size creators you're outgrowing, for example, "You grew faster than 86% of creators your size", along with the specific metrics driving that score, reach, followers, engagement, and website visits.

## Core metrics

* **Impressions**, total times your content was seen
* **Likes**, total likes across all connected channels
* **Comments**, total comments across all channels
* **Engagement Rate**, percentage of viewers who interacted with your content

Each metric shows the percentage change from the previous period, plotted over time.

## Audience Journey

A funnel showing how your audience moves from awareness to action, impressions, reached, engaged, and website visits. Use it to see where you lose the most people between seeing your content and acting on it.

## Channel Performance

A per-channel breakdown of likes, comments, reposts, impressions, and reach, so you can see which platform is doing the most work.

## Followers

Track total follower count, or switch to Follows and Unfollows to see gross change per channel.

> [!TIP]
>
> If growth stalls on one channel, check Channel Performance first, a drop in impressions on a single platform is usually a sync or posting-frequency issue, not a content problem.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.