Track employee referrals and attribute sourced candidates in an ATS
domain: recruiting-general · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a unique referral link per employee that appends a source parameter (e.g., ?referrer_id={employee_id}) to your careers page or job posting URL
On application submission, capture the referrer_id parameter from the URL and include it as a custom field or source attribution in the ATS API request
In Greenhouse, set the source field to 'Referral' and add the referrer as a prospect_owner or use the Harvest API to add an attribution note linking the referring employee's email
Build a reporting query that counts referred candidates by stage (applied, interviewed, hired) grouped by referrer for calculating referral bonus eligibility
On hire of a referred candidate, trigger a notification to HR or payroll to process the referral bonus according to your program rules
Known gotchas
URL parameters are stripped by many link shorteners and some email clients; test referral link tracking end-to-end before launching the program to confirm attribution is captured
Candidates who apply through multiple channels (e.g., referred link and then directly) may create duplicate attribution; define a clear 'first touch' vs 'last touch' attribution rule in your system
Referral bonuses for candidates who are hired but leave within a probationary period often need to be clawed back; ensure your tracking captures both hire date and a post-hire status update
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?