Offline conversion tracking

Recruitee + Meta Ads Integration

LeadTrackr sends Recruitee candidates to Meta Ads through the Conversions API (CAPI), matching each qualifying stage and hire to its fbclid so Advantage+ delivery and lookalikes learn from people you actually hire.

5-min setup · cancel anytime

How the pieces fit

From a Recruitee candidate to a Meta 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.

business.facebook.com/adsmanager
Campaigns Optimized on hires
CampaignSpendForm fillsQualifiedhires
Lookalike 1%€3,6001802711
Retargeting — IG€2,200124187
Prospecting€1,90015683
Broad€1,40024031

Illustrative figures.

Sent to Meta Ads
+22 hires
Illustrative

LeadTrackr pushes the hired-candidate outcome to Meta Ads via Conversions API (CAPI).

Recruitee + Meta Ads

How Recruitee candidates become Meta Ads conversions

In plain English: when a Recruitee candidate reaches interview or gets hired, LeadTrackr tells Meta server-side — so Advantage+ and lookalikes learn from people you hire, not everyone who taps apply.

How it works in one picture

Ad click
Someone clicks your vacancy ad
Application
fbclid captured on submit
Candidate hired
Marked Hired in Recruitee
LT
LeadTrackr
Matches the candidate to the fbclid
Smarter delivery
Advantage+ optimizes on hires

The full story

LeadTrackr sends Recruitee outcomes to Meta Ads through the Conversions API (CAPI), server-side. It captures the fbclid on the original application submission and stores it against the Recruitee candidate, along with the hashed email and phone they entered on your form, so qualification and Hired events arrive even when the browser Pixel is blocked by ad blockers, iOS restrictions, or cookie consent.

Application forms carry unusually strong identifiers — candidates give a real email and phone because they want to be contacted — which pushes Event Match Quality toward the Great range. And because LeadTrackr only sends candidates who reached a qualifying stage or were marked Hired, your Lookalike Audiences are seeded from people who passed your process, giving Advantage+ delivery the downstream signal it needs to target the profile you hire instead of the profile that clicks.

What LeadTrackr reads

Pipeline stage

A candidate reaching your interview stage fires a server-side CAPI event with full match parameters.

Hired/disqualified status

The Hired status seeds Custom and Lookalike Audiences from people who actually accepted an offer.

How it works, step by step

fbclid captured
Stored against the candidate with hashed email & phone
Candidate progresses or is hired
Reaches a mapped stage or is marked Hired
CAPI event sent
Server-side to Meta in near real time

You might be wondering

Q.How do you send Recruitee candidates to Meta Ads?

LeadTrackr reads the Recruitee pipeline stage and hired/disqualified status, then sends each qualifying outcome to Meta through the Conversions API (CAPI) server-side. It ties the fbclid from the application to the candidate and adds hashed email and phone, so a hire lifts Event Match Quality and lets Advantage+ delivery and Lookalike Audiences optimize toward people who resemble your real hires. The events carry no value — a candidate has no amount — so this optimizes on cost per hire, not ROAS.

Conversions are sent to your ad platforms
Qualified-lead and closed-deal events, via official server-side APIs.
Google AdsMeta AdsGoogle Analytics 4Webhook

The connection at a glance

How Recruitee + Meta Ads works

Click ID capturedfbclid
Recruitee signal readPipeline stage + hired/disqualified status (e.g. Interview, Hired)
Destination APIConversions API (CAPI)
Recruitee connectionPersonal API token on the Recruitee API
Conversion valueNone — a candidate carries no amount; events are sent without a value
Setup time~5 minutes
Attribution parametersIP address, user agent, hashed email & phone

Why connect them

What Recruitee + Meta Ads unlocks

Server-side CAPI, no Pixel gaps

LeadTrackr sends Recruitee outcomes straight to Meta through the Conversions API server-side, so qualification and Hired events arrive even when the browser Pixel is blocked by ad blockers, iOS restrictions, or cookie consent.

High Event Match Quality

Each event carries the fbclid plus the hashed email and phone the candidate entered on your application form, pushing Event Match Quality toward the "Great" range so Meta can attribute more of your hires accurately.

Lookalikes seeded from real hires

Because LeadTrackr only sends candidates who reached a qualifying stage or were marked Hired, your Meta Custom and Lookalike Audiences are seeded from people who passed your process — not from everyone who ever clicked apply on a vacancy.

Advantage+ optimized on filled vacancies

Feeding hired Recruitee candidates into CAPI gives Advantage+ campaigns the downstream signal they need, so Meta delivery shifts spend toward audiences whose applications survive the first screen, rather than audiences that produce cheap volume and no hires.

Advertisers pushing hired Recruitee candidates into Meta via CAPI typically lift Event Match Quality into the "Great" range, giving Advantage+ a cleaner hire signal to optimize against.

How it works

Set up once, runs automatically

01

Recruitee candidate qualifies

A candidate reaches a mapped stage such as Interview, or is marked Hired in Recruitee — the signals you chose to treat as conversions.

02

LeadTrackr assembles the CAPI event

LeadTrackr pulls the fbclid stored against the Recruitee candidate and hashes their email and phone with SHA-256, assembling a server-side event with full match parameters.

03

Event sent to Meta via CAPI

LeadTrackr delivers the event to Meta through the Conversions API in near real time, attributed to the original click. Advantage+ delivery and your lookalike modeling update to favor people who resemble your hires rather than every applicant.

FAQ

Recruitee + Meta Ads questions

LeadTrackr uses the modern Conversions API (CAPI), Meta's recommended method for server-side events, not the deprecated Offline Conversions API. Each Recruitee outcome is delivered as a CAPI event with fbclid plus hashed email and phone, which gives better matching, real-time delivery, and higher data reliability than the legacy offline upload. This keeps your Recruitee hires eligible for Advantage+ and other automated Meta products.
Event Match Quality rises with the number of strong identifiers per event. LeadTrackr sends the fbclid captured at application together with the hashed email, hashed phone, IP, and user agent from the Recruitee candidate. Application forms are unusually rich here — candidates give a real email and phone number because they want to be contacted — so this combination typically lands in Meta's "Great" band, which means more of your hires are attributed to the right campaigns.
Yes, and for recruitment this is usually the single biggest win. Once qualifying Recruitee outcomes flow into Meta via CAPI, you can build a Custom Audience of candidates marked Hired and then create a Lookalike Audience from it. Because the seed is people who actually passed your interviews and accepted an offer, the resulting lookalike targets the profile you hire rather than the profile that clicks — which usually cuts the volume of unqualified applications your recruiters have to screen.

Get started free

Start pushing Recruitee conversions to Meta Ads

Set up the connection in minutes — no developer needed.

Start Free

5-min setup · cancel anytime