Offline conversion tracking

Recruitee + ChatGPT Ads Integration

LeadTrackr sends Recruitee pipeline stages and hired/disqualified outcomes to ChatGPT Ads through OpenAI’s Conversions API, matching each hire back to its oppref click identifier so conversion-optimised bidding trains on filled vacancies.

5-min setup · cancel anytime

How the pieces fit

From a Recruitee candidate to a ChatGPT Ads conversion

recruitee.com
Recruitee · Candidates
Applied2
EdEmma
Monteur
DVDaan
Planner
Interview1
NHNoor
Monteur
Offer1
SvSophie
Werkvoorbereider
Hired1
LBLiam
Monteur
Every status → pushed automatically

Recruitee qualifies your leads — your team just works candidates as usual.

ads.google.com/aw/campaigns
Campaigns Optimized on hires
CampaignSpendForm fillsQualifiedhires
Kitchen — Sponsored€1,80074198
Bathroom — Sponsored€1,20052115
Broad — Home Reno€9009652
Brand€3003831

Illustrative figures.

Sent to ChatGPT Ads
+16 hires
Illustrative

LeadTrackr pushes the hired-candidate outcome to ChatGPT Ads via ChatGPT Ads Conversions API.

How do you send Recruitee hires to ChatGPT Ads?

LeadTrackr reads the Recruitee pipeline stage and the hired or disqualified status of each candidate, then posts the matching outcome to the ChatGPT Ads Conversions API server-side. It captures the oppref click identifier when a candidate arrives from a sponsored ChatGPT placement, stores it against the Recruitee candidate with hashed email and phone for advanced matching, and fires the conversion when the candidate reaches Interview or Hired.

The connection at a glance

How Recruitee + ChatGPT Ads works

Click ID capturedoppref (__oppref cookie, 30 days)
Recruitee signal readPipeline stage + hired/disqualified status (e.g. Interview, Hired)
Destination APIChatGPT Ads Conversions API (server-side)
Recruitee connectionPersonal API token on the Recruitee API
Conversion valueNone — a candidate carries no amount; events are sent without a value
DeduplicationShared event ID with the OAIQ pixel
Setup time~5 minutes

Why connect them

What Recruitee + ChatGPT Ads unlocks

Server-side, built for hiring timelines

A hire that lands six weeks after the application is beyond any browser pixel. LeadTrackr posts the outcome to the Conversions API when the Recruitee stage actually changes, which is what OpenAI built the server-side layer for.

Conversion bidding on quality, not volume

Send only the candidates that reached Interview or Hired and the oCPC auction learns which sponsored placements produce placeable people, instead of chasing whichever placement generates the most applications.

oppref held on the candidate

The __oppref cookie lasts 30 days, which is shorter than most hiring processes. LeadTrackr copies the identifier onto the Recruitee candidate at application, so a hire long after that window still resolves to the click.

Hashed matching, no raw candidate data

Where oppref is missing, advanced matching runs on the SHA-256 hashed email and phone from the candidate record. Hashing happens inside LeadTrackr, so no raw applicant data reaches OpenAI.

Recruiters connecting ChatGPT Ads early train conversion bidding on interviews and hires from the first week, rather than on the application volume every competing employer is optimizing toward.

How it works

Set up once, runs automatically

01

Recruitee candidate reaches a mapped stage

A candidate advances to Interview or is marked Hired — the Recruitee pipeline moments you chose as conversions, not the application form that started them.

02

LeadTrackr builds the server-side event

LeadTrackr reads the oppref value from the candidate record, adds the hashed email and phone for advanced matching and stamps a stable event ID for deduplication. No value is attached — a candidate carries no amount.

03

Posted to the Conversions API

The event reaches your ChatGPT Ads Pixel ID over the server-side endpoint, attributed to the placement that earned the click, and conversion bidding steers toward the placements that produce hires.

FAQ

Recruitee + ChatGPT Ads questions

Usually Interview rather than Hired. Conversion-optimised bidding needs enough events to build a model, and hires are too rare in most pipelines to provide that on their own. Interview fires sooner and far more often while still representing a genuine quality judgement by a recruiter. LeadTrackr maps each stage to its own event, so you can bid on Interview while still sending Hired for reporting.
No. A Recruitee candidate carries no monetary amount, so LeadTrackr sends the conversion without a value rather than fabricating one. ChatGPT Ads conversion events do accept a value, so if you want to weight vacancies differently you can configure a fixed value per vacancy in LeadTrackr and have that sent instead — but the default is an honest valueless event.
If you are spending on the channel, yes — the auction optimizes on whatever events reach it regardless. Sending applications teaches it to find people who apply, which in recruitment is a notoriously poor proxy for people worth hiring. Sending Interview and Hired events costs the same to configure and produces bidding trained on candidate quality from the start, before the channel’s costs settle at mature levels.

Get started free

Start pushing Recruitee conversions to ChatGPT Ads

Set up the connection in minutes — no developer needed.

Start Free

5-min setup · cancel anytime