Hiring Report: Get More Accurate Reports by Connecting Greenhouses’ Offers Endpoint

Why should we connect our Offers Endpoint to our Datapeople integration?

At Datapeople, we want to make sure you have access to accurate and timely analytics for your hiring processes. 

If you aren't currently sharing your Greenhouse offers endpoint with Datapeople, we use the candidate’s last_activity_at date to populate the Hiring Report. However, we’ve found that in Greenhouse, the last_activity_at date updates with any activity such as:

• surveys being sent to candidate after offer is accepted
• any candidate data being updated (new address, etc.)
• employee (former candidate) being added as a Greenhouse user (becoming an interviewer)

So, the last_activity_at date does not always align with the candidate’s hire date and will shift the data each time the user has an update to their account, sometimes to months after their hire date.

Within the offers endpoint, the offer_resolved_at date captures the date that the recruiter marked the candidate as resolved (hired, declined, etc). It is a static date that captures the single action that the Hiring Report focuses on.

Greenhouse uses the offer_resolved_at date for their Offers Accepted metric, so using the offer endpoint for our reporting will allow your ATS data to line up with what you’re seeing in Greenhouse, as well.

Here is an example of how using the offer endpoint will provide clearer and more accurate reporting:

In Q1 you hired 28 candidates. Since then, 8 of those candidates have had updates to their Greenhouse user profile.

• Using the offer endpoint, our Hiring Report would include all 28 candidates in a report or Q1
• Without the offer endpoint, we use the next best thing, the last_activity_at date, which would only show 20 hires, because the other 8 have a newer last_activity_at date. 
• Since 8 of the candidates have had activity on their profile since they were hired, they would not be included in the Q1 Hiring Report.

This shifts hiring metrics slightly:

These don’t seem like large differences, but what happens to the 8 candidates whose last_updated_at dates are later on?

These 8 candidates had updates to their profile in Q3, so let’s see how this affects Q3 data:

• In Q3, without the offer endpoint, we’d see a higher number of hires than there actually were.
• Without the offer endpoint, the 8 candidates who applied (and were hired) months ago also exacerbate the average time to hire.

Adding the offer endpoint to a Datapeople integration is easy! And will give a much more accurate experience with our Hiring Report!

How do I add the Offer Endpoint to our Datapeople integration?

In order to enable the use of your offer data in Datapeople’s Hiring Report, your Datapeople integration needs access to the Offers endpoint. This can be done by anyone with Developer Permissions in Greenhouse. View a How-To video here.

Navigate to the Datapeople Harvest API Key

Click the Configure icon on your navigation bar, then click Dev Center on the left.

Navigate to API Credential Management

Click on the pencil icon so you can edit for your Datapeople integration

Permissions

Add the following permissions for the Datapeople integration:

Offers

• Get: List Application's Offers
• Get: Retrieve Application's Current Offer
• Get: Retrieve Offer
• Get: List Offers

Here’s what it should look like when you’re done:

When you’ve saved your edits, please reach out to your Datapeople account representative so we can validate that we have the right access.