The meeting becomes tense the moment somebody asks which number is right. The media platform shows conversions. The ATS shows fewer applicants from the source. Recruiters say the candidates they reviewed were not viable. Each group has evidence. None has the whole story.

This is one of the most common forms of the Outcome Accountability Gap. The person responsible for explaining the result is handed three partial records and expected to produce one clean conclusion.

Begin by asking what each system can actually observe

A media platform can observe impressions, clicks, redirects, landing-page events, and any conversion event that was correctly instrumented. It may not know whether the ATS created a durable candidate record, whether the person completed every required field, whether the recruiter reviewed the application, or whether a hiring manager changed the requirements after launch.

An ATS can store candidate records, source fields, stages, dispositions, and hires. It may not know the full path that led the candidate there. Source values can reflect a last detectable touch, a self-reported answer, an imported value, a mapping rule, or a default. Those are not interchangeable forms of evidence.

Recruiters see response, eligibility, fit, duplicate records, candidate confusion, and hiring-manager behavior. Their judgment is essential, but it is also shaped by workload, workflow design, disposition discipline, and the clarity of the intake.

Three reports can be internally accurate and still produce one misleading performance story.

Use a reconciliation table before choosing a winner

For the campaign or role in question, place the following information side by side:

  • The exact event the media platform called a conversion.
  • The identifier passed at that event.
  • The ATS event that created or updated the candidate record.
  • The source logic applied by the ATS.
  • The recruiter disposition and when it was entered.
  • The hiring-manager decision and any requirement changes.
  • The final outcome that matters for the business.

The purpose is not to make the totals match at any cost. It is to understand why they differ. A 20 percent mismatch caused by cookie loss requires a different decision than a 20 percent mismatch caused by imported leads being labeled as applicants.

Separate observed facts from attribution rules

Observed facts include an ad click, a form submission, an ATS record, a recruiter disposition, an interview, or a hire. Attribution rules assign credit for those facts. The rule can be useful without being causal truth.

When leaders collapse the two, a source field becomes proof that one channel created the hire. A more defensible statement may be that the source was the last recorded acquisition touch, while other interactions were not consistently available.

What to change before the next report

  1. Define the apply and conversion events in writing.
  2. Preserve a campaign, job, and candidate identifier across the handoff where appropriate.
  3. Test the path before launch with real records.
  4. Require consistent recruiter dispositions and document what each disposition means.
  5. Label modeled, inferred, and observed results separately.
  6. Return interview and hire outcomes to the systems and partners shaping acquisition.

This work does not create perfect attribution. It creates a performance story that can survive reasonable questions.

Continue with The Evidence Chain: from candidate touch to retained hire and What a $10,000 recruitment campaign must be able to prove.

What this looks like in a real operating week

On Monday, the media team sees application volume pacing above plan. On Tuesday, recruiters flag that many records are missing a required credential. By Wednesday, the ATS report shows fewer sourced applicants than the media report. On Thursday, the client asks which partner should lose budget. The team is already debating a funding decision before anyone has confirmed whether the records represent the same event.

A useful pause at that point is not bureaucracy. It is decision protection. Pull a sample of records and follow them. Did the media conversion create an ATS record? Did the ATS preserve the campaign identifier? Did the recruiter apply the same eligibility rule used in planning? Did the hiring manager change the requirement? A sample of twenty or thirty records can reveal more about the mechanism than another aggregate dashboard.

Choose an authority for each fact

The organization may not have one source of truth for the entire hiring outcome. It can still define an authoritative source for each fact. The ad platform may be authoritative for spend and delivery. The web analytics tool may be authoritative for site behavior. The ATS may be authoritative for stage movement. The HRIS may be authoritative for starts and employment status. Recruiter notes may be the strongest available record of viability, provided the dispositions are defined and used consistently.

This approach reduces a common failure: asking one system to prove facts it was never designed to hold.

Watch for the human causes of data conflict

Not every discrepancy is technical. Recruiters sometimes delay dispositions because the workflow is cumbersome. Hiring managers may reject candidates in email or chat without updating the ATS. Campaign naming conventions can change midflight. Teams may duplicate requisitions or move candidates between jobs. Those behaviors are part of the operating system and should be included in the reconciliation.

The final conclusion should be specific enough to change a decision. “The data is messy” is not a conclusion. “The ATS lost the campaign identifier after the mobile apply handoff, so we can prove delivery and apply starts but cannot attribute 18 percent of completed records by source” is a conclusion that supports action.