Try Free
Background ScreeningGreenhouse IntegrationRecruitment Tech

Data Facts Background Check Integration for ATS: API Setup, Compliance, and ROI

Titus Juenemann May 22, 2024

TL;DR

Integrating Data Facts with Greenhouse embeds background checks into the ATS workflow to automate orders, surface status updates, and attach final reports to candidate profiles. The integration is well-suited for enterprises, regulated industries, and high-volume hiring operations in North America; it offers SOC 2 controls, PBSA accreditation, no offshoring, and specialty services like education verification and OIG exclusion screening. Implementation involves API configuration, consent workflows, and a pilot phase; teams should track time-to-clearance, recruiter time saved, and compliance metrics to measure ROI. Combined with AI pre-screening (for example, ZYTHR) this setup can reduce unnecessary screening volume and accelerate hiring while preserving auditability and data controls.

Data Facts’ integration with Greenhouse embeds background screening into the candidate workflow so teams can request, receive, and record screening results without switching systems. The integration leverages Greenhouse APIs and partner hooks to push candidate details to Data Facts, track status updates in real time, and attach final reports directly to the candidate profile. This setup reduces manual steps, centralizes hiring documentation, and preserves an audit trail for compliance. Its design aims at organizations that need fast, auditable screening — from high-volume hourly hiring to regulated professional roles — while maintaining security controls such as SOC 2 compliance and data residency (no offshoring).

What the Data Facts integration does — at a glance

  • Automates screening requests Triggers background checks from Greenhouse when a candidate reaches a defined workflow stage (e.g., after offer or after interview).
  • Streams status updates Displays screening progress in Greenhouse (ordered, in-progress, cleared, adverse) so recruiters and hiring managers see live status.
  • Attaches final reports Final background check reports and verifications are stored on the candidate record for audit and hiring decisions.
  • Supports specialty services Includes education verification, medCheck (OIG exclusion searches), and other specialty screens accessible through the same flow.
  • Preserves data controls Operates with SOC 2 controls and PBSA accreditation while keeping data processing in North America (no offshoring).

Typical technical flow: Greenhouse sends a screening request via API or partner integration when a configured candidate stage is reached. Data Facts ingests candidate PII, normalizes fields (name, DOB, SSN when required), and queues standardized searches. Results and document attachments are posted back to Greenhouse using candidate identifiers so the two systems remain synchronized and auditable.

ZYTHR for Greenhouse – Featured Section
ZYTHR - Your Screening Assistant

AI resume screener for Greenhouse

ZYTHR scores every applicant automatically and surfaces the strongest candidates based on your criteria.

  • Automatically screens every inbound applicant.
  • See clear scores and reasons for each candidate.
  • Supports recruiter judgment instead of replacing it.
  • Creates a shortlist so teams spend time where it matters.
ZYTHR - AI resume screener for Greenhouse ATS
Name Score Stage
Oliver Elderberry
9
Recruiter Screen
Isabella Honeydew
8
Recruiter Screen
Cher Cherry
7
Recruiter Screen
Sophia Date
4
Not a fit
Emma Banana
3
Not a fit
Liam Plum
2
Not a fit

Feature comparison: Data Facts integration vs generic background checks

Capability Data Facts + Greenhouse
Turnaround time Optimized workflows and platform automation for faster results; enterprise SLAs available
Compliance & certification PBSA accreditation, SOC 2; no offshoring of data
Specialty searches Education verification, medCheck (OIG/Affiliate exclusion) and vendor list screening
ATS integration Native Greenhouse integration with status updates and report attachments
Customer support Dedicated US-based account teams and client portals for case management

Who should evaluate this integration

  • Enterprise and scaling mid-market teams Organizations (100–10,000+ employees) that need integrated screening across many roles and locations in North America.
  • Healthcare and regulated industries Employers that require OIG exclusion checks, provider screening, and auditable verification for compliance.
  • High-volume hiring operations Retail, hospitality, logistics, and staffing firms that need fast turnaround to fill many hourly roles.
  • Teams prioritizing security and data locality Companies that need SOC 2 controls and no offshoring for sensitive candidate information.

Compliance considerations: Data Facts holds PBSA accreditation and SOC 2 certification which assist organizations in meeting industry standards and audit expectations. The integration keeps PII handling within defined data residency boundaries and integrates with Greenhouse’s consent and disclosure workflows so employers can capture candidate authorization and maintain a clear chain-of-custody for screening decisions.

Key benefits for hiring teams

  • Faster time-to-hire Automated order placement and electronic verifications reduce manual follow-up and speed clearance for offer acceptance.
  • Reduced recruiter workload Status updates and attached reports eliminate manual uploads and follow-ups with screening vendors.
  • Better recordkeeping Reports stored on candidate profiles provide a single source for audit and compliance reviews.
  • More consistent screening Standardized packages (criminal, education, OIG checks) ensure consistent criteria across roles and locations.
  • No hidden implementation fees Integration details list no partner implementation fee, reducing initial project cost for many customers.

Common implementation questions

Q: How do I start connecting Data Facts to Greenhouse?

A: Request the integration through Data Facts or Greenhouse’s partner portal; Data Facts will provide API keys, configuration steps, and a checklist to map candidate fields and screening packages.

Q: Is candidate consent handled?

A: Yes — the typical integration leverages Greenhouse disclosure and authorization workflows so consent is captured before candidate data is transmitted.

Q: What if I need custom screening packages?

A: Data Facts supports custom package configuration for role-based needs (e.g., medCheck for healthcare). Discuss requirements with your Data Facts implementation specialist.

Implementation checklist for IT and HR: confirm Greenhouse admin access and API credentials, define screening packages and workflow triggers, document consent steps for disclosure, test ordering and result posting in a sandbox environment, and align SLAs and escalation paths with Data Facts’ support team. Plan a short pilot with a controlled set of roles to validate status mapping, report attachments, and candidate communications.

Sample timeline and SLA expectations

Phase Typical duration / expectation
Setup & API configuration 1–2 weeks: credential exchange, field mapping, and sandbox tests
Pilot (small cohort) 2–4 weeks: verify workflows, consent capture, and report handling
Full rollout 1–4 weeks after pilot: scale packages and monitor SLAs
Turnaround for common screens 24–72 hours for criminal searches; education and OIG checks may vary depending on source

Measuring ROI: metrics to track

  • Time-to-clearance Average hours/days from order to final report — compare before vs after integration to quantify speed improvements.
  • Recruiter time saved Hours per week previously spent on manual follow-ups and uploads; automation converts that into capacity for higher-value work.
  • Offer acceptance rate Track whether faster screening correlates with fewer declined offers due to delays.
  • Compliance incident rate Monitor audit findings or remediations related to screening documentation and consent capture.

Troubleshooting & support

Q: If a report doesn’t attach to the candidate, what should I check?

A: Verify the candidate identifier mapping (candidate ID or external ID), ensure API keys are active, and check Data Facts’ portal for processing status or exception notes.

Q: Who handles disputes or candidate disputes of results?

A: Data Facts maintains a dispute resolution process; the employer should coordinate with Data Facts to initiate rechecks, corrections, or supplemental verifications per PBSA guidance.

Q: What support channels are available?

A: Data Facts offers client portals, dedicated account teams, and support contacts; escalate integration or SLA issues through the designated account manager.

Best practices: start with role-based screening packages to limit unnecessary searches, include consent steps early in the Greenhouse workflow, monitor initial pilot metrics, and maintain a single source of truth by keeping all reports attached to the candidate profile. Regularly review package configurations and SLAs with Data Facts to align with changing compliance needs or hiring volume shifts.

Pair Greenhouse + Data Facts with ZYTHR to speed hiring

Use ZYTHR’s AI resume screening to surface the best candidates before sending orders to Data Facts, reducing the number of background checks you need to run and improving reviewer accuracy. ZYTHR saves recruiter time and increases resume review precision — combine it with Greenhouse + Data Facts for a faster, more reliable hiring pipeline.