Skip to main content
Recruitee → CriteoIntegration guide

Connecting Recruitee to Criteo

Recruitee leans on collaborative hiring and employer branding, which means much of its value shows up as candidate quality rather than as application volume. Criteo is a retargeting and commerce media network built on product-level data, which means its feed matters as much as its conversion events. The join between them succeeds or fails on one thing: whether the Criteo user identifier and product IDs reaches the Recruitee candidate before the conversion happens, because Criteo can only match a conversion it can tie back to a click it recognizes.

Free30 minutesNo obligation

Specific to this pair

Recruitee and Criteo: wrong tool for hiring, count sources instead

There is no Recruitee-to-Criteo setup worth building: a hiring funnel has no product catalog or transactions. Use a tagged link per board or campaign, Recruitee's source field filled at application, and quarterly screening pass rate and hires by source. Build any retargeting audience from careers pages you control, never from candidate lists, after checking employment-ad rules.

Criteo's retargeting depends on a product catalog and transaction events, and a hiring funnel has neither. A job opening is not a product, an application is not a transaction, and a hire is certainly not something to retarget. There is no Recruitee-to-Criteo setup worth building, and a feed of open roles would only produce ads following candidates around the web after they applied.

If the underlying request is to retarget people who looked at your jobs, that is an audience on a social or display platform, and in the US it runs into employment-ad rules on several platforms; check the specific platform's policy before targeting anyone. Any retargeting audience should be built from careers-page visits on pages you control, never from Recruitee candidate lists, and certainly not from rejected applicants.

The sane minimal setup for paid recruiting is a tagged link per board or campaign, Recruitee's source field filled at application, and a quarterly report of screening pass rate and hires by source. That answers where to spend without sending any candidate signal to an ad network. If a vendor insists Criteo can optimize toward hires, ask what event it would receive and how often; the answer will be a handful a quarter.

Recruitee → Criteo · what breaks

Why this join usually fails — Recruitee → Criteo

  1. 01

    The Criteo user identifier and product IDs never reaches Recruitee

    Careers pages may be hosted by Recruitee on their subdomain, and applications arrive from several boards.

  2. 02

    Application volume reported instead of candidate quality

    A board producing three hundred applications of which none pass screening is worse than one producing twenty of which five do. Volume reporting rates them the opposite way round.

  3. 03

    Product IDs that do not match the feed

    Criteo resolves conversions against your catalogue. If the IDs in your purchase events differ from the IDs in your feed — a common outcome when the feed is generated by a different system — the conversion resolves poorly and the reported value is wrong.

  4. 04

    Nothing reconciles afterwards

    Criteo reports conversions on its own attribution windows, which include view-through. Reconcile against your own order records and be explicit that view-through credit is included — otherwise the comparison will never balance.

Recruitee → Criteo · the fix

What working looks like — Recruitee → Criteo

  • The Criteo user identifier and product IDs on every application

  • Conversions arriving in Criteo

    Conversions appear in Criteo's reporting attributed to its own view- and click-through windows, which are worth understanding before comparing anything.

  • Reconciled against the source

Recruitee → Criteo · architecture

How Recruitee and Criteo actually connect

  1. 1

    Recruitee holds the truth

    Two sources producing identical application volumes can differ completely in how far those candidates progress. Stage rate by source is the useful signal and it is rarely reported.

  2. 2

    Criteo needs a click to match

    Criteo needs the transaction with its product IDs, quantities and values, matched to your catalogue feed. Identity resolution is Criteo's side of the problem; feed consistency is yours.

  3. 3

    The identifier is the bridge

    The Criteo user identifier and product IDs, captured at the visit and carried into the Recruitee candidate.

  4. 4

    The event source decides reliability

    Send hires as counts by source, with stage progression rates reported alongside. No candidate detail.

  5. 5

    Deduplication at the destination

    Criteo deduplicates on the transaction identifier. Sending the same order from both a tag and a server integration without a shared ID counts it twice, and on a retargeting network that inflates the metric the whole channel is judged on.

Recruitee → Criteo · normal or broken

Working vs. broken, side by side — Recruitee → Criteo

Normal, not a fault

  • The Criteo user identifier and product IDs present on the application

  • Sent from the Recruitee hire record

  • Deduplicated correctly

    Criteo deduplicates on the transaction identifier. Sending the same order from both a tag and a server integration without a shared ID counts it twice, and on a retargeting network that inflates the metric the whole channel is judged on.

  • Reconciles with the source

Actually broken

  • The Criteo user identifier and product IDs missing on most records

    Careers pages may be hosted by Recruitee on their subdomain, and applications arrive from several boards.

  • Sent from the browser

    A board producing three hundred applications of which none pass screening is worse than one producing twenty of which five do. Volume reporting rates them the opposite way round.

  • Counted twice, or not at all

    Criteo resolves conversions against your catalogue. If the IDs in your purchase events differ from the IDs in your feed — a common outcome when the feed is generated by a different system — the conversion resolves poorly and the reported value is wrong.

  • Nobody has reconciled it

Recruitee → Criteo · diagnose

Diagnostic order — Recruitee → Criteo

  1. 01

    Count applications carrying the Criteo user identifier and product IDs

  2. 02

    Follow one real conversion end to end

  3. 03

    Report screening pass rate by source

    It is available in the ATS and almost never reaches whoever is deciding where to advertise.

  4. 04

    Compare product IDs in a real conversion against the catalogue feed

    They must match exactly. This single check explains most Criteo value discrepancies.

  5. 05

    Read the match rate, not the success message

    Criteo reports conversions on its own attribution windows, which include view-through. Reconcile against your own order records and be explicit that view-through credit is included — otherwise the comparison will never balance.

Recruitee → Criteo · prove

How it gets proven — Recruitee → Criteo

Source of truth

Hires by date and source, with stage progression tracked per source.

  • The Criteo user identifier and product IDs confirmed present on a live application.
  • Product IDs in a live conversion confirmed to match the catalogue feed exactly.
  • Hires reconciled as counts by source, with stage rates reported and no candidate data sent.

Recruitee → Criteo · free audit

What we check in the free audit

  • Count applications carrying the Criteo user identifier and product IDs
  • Follow one real conversion end to end
  • Report screening pass rate by source
  • Compare product IDs in a real conversion against the catalogue feed
  • Read the match rate, not the success message

Checked against

Hires by date and source, with stage progression tracked per source.

Get my free conversion tracking audit

Free30 minutesNo obligation

Recruitee → Criteo · when not to buy

When you don't need this — Recruitee → Criteo

  • Measure identifier coverage yourself first — pull your last hundred applications and count how many carry the Criteo user identifier and product IDs.
  • If every source produces similar quality, volume is an adequate proxy and the extra reporting is unnecessary.
  • If you do not sell products with a catalogue, Criteo's model does not fit and the effort is misdirected.

Recruitee → Criteo · what we deliver

What gets built — Recruitee → Criteo

  • Identifier capture into Recruitee

    Capture where you control the careers page and record source at application.

  • Event source: the Recruitee hire record

    Send hires as counts by source, with stage progression rates reported alongside. No candidate detail.

  • Dispatch to Criteo

    Server-side transaction events with product IDs matching the catalogue feed, plus the feed itself kept in sync.

  • Reversals where they exist

    Declined offers reverse.

Written guarantee

95%+ tracking accuracy

Measured against Hires by date and source, with stage progression tracked per source.. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Recruitee → Criteo questions, answered

It isn't built for that, and you shouldn't upload candidate data to an ad network. Retarget careers-page visitors on a platform whose employment-ad rules you've checked, if at all.

Free · 30 min

Get Recruitee and Criteo joined properly

Free30 minutesNo obligation