> For the complete documentation index, see [llms.txt](https://help.join.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.join.com/post-and-promote-jobs/postings-status.md).

# Postings status

Check where each job is posted, what each posting status means, and how many applications and clicks every job board has brought in for that job.

The `Postings` tab shows you every channel your job is distributed to, its current status, and how many applications and clicks it has brought in, organic and paid, in one place.

To open the `Postings` tab:

1. Click `Jobs` > `Active` in the sidebar menu and select the job you want to review
2. Click the `Postings` sub-tab within the job page

{% hint style="info" %}
Looking for the `Channel Performance` chart? It has moved to the job's `Reports` tab as the `Applications` chart, alongside reports on your sources and pipeline. See [Reports & analytics](/create-and-manage-jobs/job-reports.md).
{% endhint %}

***

## Postings table

The postings table lists every channel your job is distributed to.

The table always includes a row for your JOIN career page and job widget. It reads `Online` while the job is online and shows applications and clicks like the other channels.

<figure><img src="https://1825767176-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEdFjOFlkC1DEfDv3nGRh%2Fuploads%2FcgkC1QCvErBptMcf7JAF%2Fchannel-list.png?alt=media&amp;token=6d0b4384-6464-450e-be32-f575f0c26572" alt=""><figcaption></figcaption></figure>

Each row shows:

* **Channel**: The name of the job board/channel, logo, and product type (e.g. `Organic`, `Single Posting`, `LinkedIn Ultimate`)
* **Status**: The current publication status of that posting (see [Posting statuses](#posting-statuses) below to understand the different types of status)
* **Applications**: The number of applications received from that channel. Hover over the count to see the quality breakdown (see [Application quality](#application-quality) below). Rows with no applications show `–`
* **Clicks**: The number of clicks your job ad received on that channel, where the board supports this data. Rows where click data is not available show `–`
* **External link icon**: For postings with an `Online` status, where the board has returned the ad's URL, click the link icon to open the live job ad directly on the partner platform. Use this to check how your ad looks or to share it with a hiring manager

***

## Posting statuses

Each row in the table shows a status tag reflecting the real-time state of that posting on the partner platform. Hover over any status tag to see additional context, such as when a posting went live, when it expires, or details about a failure.

Not all statuses apply to every type of posting. Some are specific to organic (free) postings, others to paid postings, and some can appear on both.

<table data-card-size="large" data-view="cards" data-search="true"><thead><tr><th>Status</th><th>What it means</th><th>Applies to</th><th>Details</th></tr></thead><tbody><tr><td><code>Online</code></td><td>The job is live and visible on the job board.</td><td>Organic and Paid postings</td><td><ul><li>JOIN received a direct confirmation from the board. Most boards also return the URL of the live job post, but some don't, or not straight away: a free Indeed posting, for example, gets a link only once a candidate applies through Indeed Apply.</li><li>For paid postings, the hover tooltip shows: <code>Active since [date] · Expires [date]</code>.</li><li>For organic postings, the hover tooltip shows: <code>Posted organically</code>.</li><li>When a posting is Online and the board has returned its URL, a link icon appears in the row. Click it to open the live ad on the partner platform.</li></ul></td></tr><tr><td><code>Sent</code></td><td>The job has been successfully sent to the job board, but the board has not sent a confirmation back to JOIN.</td><td>Organic postings only</td><td><ul><li>This happens with job boards that receive postings via an XML feed rather than a direct API connection.</li><li>This is normal behaviour for feed-based boards and does not mean anything went wrong.</li><li>JOIN cannot display a link to the job post or verify the exact moment it went live.</li><li>Your job has been sent successfully. To confirm it is live, visit the job board directly.</li><li>Application and click counts are not available.</li><li>You can still receive applications from these boards.</li></ul></td></tr><tr><td><code>Processing</code></td><td>JOIN has submitted the job to the board and is waiting for a response.</td><td>Organic and Paid postings</td><td><ul><li>This is a temporary state that usually resolves within a few minutes to up to 72 hours, depending on the board. The hover tooltip shows the usual time for that board.</li><li>Application and click data are not yet available while a posting is in this state.</li></ul></td></tr><tr><td><code>Expired</code></td><td>The paid posting duration has ended and the job is no longer live on this board.</td><td>Paid posting only</td><td><ul><li>The hover tooltip shows: <code>Live between [date] and [date].</code></li><li>You can repurchase the posting directly from the three-dot menu if no active order exists for that board.</li></ul></td></tr><tr><td><code>Failed</code></td><td>The posting could not be published. Hover over the status tag for more detail.</td><td>Organic and Paid postings</td><td><ul><li>Hover over the Failed tag to see the reason and who is responsible for resolving it.</li><li>Error on your side: The tooltip shows the specific issue. Resolve it, and if the posting still shows <code>Failed</code>, contact us at contact@join.com.</li><li>Error on our side: An internal error occurred. JOIN's team has been notified and is working on it. No action is needed from you.</li><li>Error on the channel board's side: A technical error occurred on the job board's side. JOIN's team has been notified.</li><li>If a Failed posting has not resolved after 24 hours, contact us at contact@join.com.</li></ul></td></tr><tr><td><code>Configure</code></td><td>The job board needs your company's details before JOIN can post your job there.</td><td>Organic posting only</td><td><ul><li>The hover tooltip shows: <code>Set up posting on [Board Name]</code>.</li><li>Click <code>Manage</code> on the row to open the board's profile in a new tab and add your company's details. You need permission to edit integrations.</li><li>Until the details are saved, the board shows as <code>Configure</code> and JOIN doesn't post your job there.</li></ul></td></tr><tr><td><code>Inactive</code></td><td>The organic posting is inactive because the job is not online, or because a paid or contract posting is currently active for the same job board.</td><td>Organic posting only</td><td><ul><li>When a paid posting is running, the organic version steps back to avoid duplication.</li><li>The hover tooltip confirms this: <code>Inactive because a paid order is active on [Board Name]</code> or <code>Inactive because a contract posting is active on [Board Name]</code>.</li><li>If the job itself is not online, the hover tooltip shows: <code>To resume, set the job status to Online</code>.</li><li>Once the paid posting ends, the organic posting will resume.</li></ul></td></tr><tr><td><code>Closed</code></td><td>The posting was closed before its scheduled end date.</td><td>Paid posting only</td><td><ul><li>The hover tooltip shows the dates it stayed live: <code>Live between [date] and [date].</code></li><li>You can repurchase the posting directly from the three-dot menu if no active order exists for that board.</li></ul></td></tr></tbody></table>

<figure><img src="https://1825767176-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEdFjOFlkC1DEfDv3nGRh%2Fuploads%2Fjfn10nclhIZbUxjWtckz%2Fchannel-status.png?alt=media&amp;token=c8ef7213-2380-4cfb-a39b-877b4ea53839" alt=""><figcaption></figcaption></figure>

{% hint style="warning" icon="lightbulb-on" %}
The key difference between `Sent` and `Online` status is whether the board sends JOIN a confirmation:

**Online**: The board confirmed the posting is live. Where it returned a URL, JOIN can show you the link directly.

**Sent**: The board received the job and is expected to publish it, but does not send a confirmation back. JOIN cannot display a link or verify the exact moment it went live.\
Your job has been sent successfully. To confirm it is live, visit the job board directly.

Application and click counts are not available for Sent postings. You will still receive applications from these boards, and they will appear in your pipeline as normal.
{% endhint %}

If you are unsure about a failed posting or it has not resolved after 24 hours, contact us at <contact@join.com>.

***

## Application quality

Hovering over the application count on any posting opens a breakdown of how candidates from that channel have progressed through your pipeline:

* **Qualification rate**: The share of applications from that channel that were qualified.
* **Unreviewed**: Candidates still in the `Application Review` stage with no recruiter action yet
* **Unqualified**: Candidates who were reviewed and not advanced
* **Qualified**: Candidates who moved past `Application Review` (e.g. to an interview stage, `Offer`, or `Hired`)

The qualification rate is only shown when there is at least one qualified candidate. If all applications are unreviewed or unqualified, no percentage is displayed.

{% hint style="info" icon="lightbulb-on" %}
Use this breakdown to compare which boards are sending candidates worth reviewing, rather than just the highest volume. To compare all of a job's sources side by side, including sourced candidates, use the `Sources` report in the job's `Reports` tab. See [Reports & analytics](/create-and-manage-jobs/job-reports.md).
{% endhint %}

***

## FAQs

<details>

<summary>Why does a posting show a status of Sent instead of Online?</summary>

Some job boards, such as Adzuna, do not send confirmation back to JOIN when a job goes live. In these cases, JOIN marks the posting as `Sent` to indicate the job has been successfully transmitted to the board. This does not mean the job failed. It means confirmation is not available for that board.

</details>

<details>

<summary>Why does a posting show dashes instead of application or click counts?</summary>

Dashes appear when data is not yet available. This happens when a posting is in `Processing` or `Sent` status, or when the job board does not share click or view data with JOIN. You will still receive applications from these job boards.

</details>

<details>

<summary>How is the qualification rate calculated?</summary>

The qualification rate is the share of applications from that channel that were qualified.

The percentage is rounded to the nearest whole number.

</details>

<details>

<summary>Why can I not see a link icon on some postings?</summary>

The external link icon only appears on postings with an `Online` status. Postings that are `Processing`, `Sent`, `Expired`, `Failed`, or `Closed` do not have a live URL to link to.

For `Sent` postings specifically, this is because the job board does not return a URL to JOIN. The job has been sent successfully, so you can check the board directly to find the live ad.

</details>

<details>

<summary>Where has the Channel Performance chart gone?</summary>

It has moved to the job's `Reports` tab, where it's now called `Applications` and also includes sourced and contract applications. The `Postings` tab now focuses on the status of each posting. See [Reports & analytics](/create-and-manage-jobs/job-reports.md).

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.join.com/post-and-promote-jobs/postings-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.