Skip to main content
Meta · IT staffingMeta × IT staffing

Meta Ads conversion tracking for IT staffing firms

IT staffing runs two acquisition problems with opposite economics and one shared ads account. What Meta Ads adds on top of that is a mechanical requirement: fbclid and _fbc have to reach the record that holds the money, because Meta can only credit a conversion it can tie back to a click it recognizes. This page covers both halves — what a conversion is in IT staffing firms, and what Meta specifically needs to accept it.

Free30 minutesNo obligation

Specific to Meta × IT staffing

Meta for IT staffing: Employment category rules and SubmitApplication

On Meta, send candidate applications as SubmitApplication and client enquiries as Lead through the Conversions API, matched on fbc, fbp and hashed email, then send filled roles from the ATS as a separate event carrying placement value. Job ads run under Meta's Employment special ad category, which limits targeting, so the conversion signal carries more of the weight.

Meta is a candidate channel far more than a client channel for IT staffing. Engineers scroll Instagram and Facebook; CIOs rarely pick a staffing vendor from the feed. Any campaign advertising jobs must be declared under Meta's Employment special ad category, which removes age, gender and ZIP targeting and limits audience options, so you cannot narrow your way to senior cloud engineers. What you can do is feed the algorithm a better event: optimize toward candidates submitted to a client rather than raw applications, if you produce enough of them each week.

Ads offering staffing services to employers are not job ads, but keep them in separate campaigns and confirm the category on each, since a mixed campaign forces the restriction onto both audiences. Meta's 7-day click window fits candidate submittals reasonably well; placements usually land later, so send them for value reporting and don't expect Meta to learn from them. Meta has no way to retract a conversion, so guarantee-period fallouts have to come out of your own ROAS math.

Where it breaks: Instant Forms. Lead ads with "years of Java experience" or "current rate" questions store that data inside Meta, and the leads never reach the ATS with an identifier attached unless someone builds the sync. Pull Instant Form leads into the ATS with their Meta lead ID, and send the later stages back against that lead ID rather than a website click.

Meta · IT staffing · what breaks

Why Meta under-reports for IT staffing firms

  1. 01

    Candidate and client leads in one conversion action

    Candidates outnumber clients heavily and take the entire budget.

  2. 02

    Contract and permanent placements valued identically

    A recurring margin and a one-time fee are not the same thing.

  3. 03

    Placements that fall through inside the guarantee

    A candidate who leaves in week six is not revenue.

  4. 04

    Fbclid and _fbc never reaches the record

    fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.

Meta · IT staffing · the fix

What working looks like — Meta · IT staffing

  • Filled roles as the money event

    Contract at expected total margin, permanent at the fee.

  • Client acquisition tracked separately

    Its own conversion action and its own campaigns.

  • Guarantee-period fallouts reversed

    Because the fee is refundable and often refunded.

Meta · IT staffing · architecture

How Meta and IT staffing firms actually connect

  1. 1

    The conversion in IT staffing firms

    Two funnels mapped independently, and two revenue models inside one of them. Contract margin accrues over the assignment; permanent fees land at once, and blending them makes both unreadable.

  2. 2

    Meta Ads needs a click to match

    event_name from the standard set with exact casing, event_time in seconds, a shared event_id, an action_source, and hashed user_data that was normalized before hashing. Purchase additionally requires value and currency.

  3. 3

    The identifier: fbclid and _fbc

    fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.

  4. 4

    Where it gets sent from

    The ATS for placements by start date and the CRM for client accounts — two reports, never summed.

  5. 5

    Deduplication and window

    This is the mechanism that decides whether adding CAPI helps or doubles your conversions. Both the Pixel and the server event must carry the same event_id — the order or booking reference works best, because both sides can produce it without coordinating. A case difference in the event name alone produces two events even with a matching ID. Read the Deduplicated indicator in Events Manager over a full week, not one session. Meta's default attribution is a 7-day click and 1-day view. View-through is included by default, which is a large part of why Meta claims more conversions than your other platforms — that overlap is expected rather than a fault.

Meta · IT staffing · events

The conversion map for IT staffing firms

Five events across two audiences and two revenue models.

Candidate applicationHigh volume, low value. Supply side.
Candidate submitted to a clientThe first meaningful candidate-side signal.
Client enquiryRare and valuable. Its own conversion action.
Role filled — contractMoney event, at expected margin over the assignment.
Role filled — permanentMoney event, at the placement fee.

Meta · IT staffing · diagnose

Diagnostic order — Meta · IT staffing

  1. 01

    Count records carrying fbclid and _fbc

  2. 02

    One conversion action for candidates and clients

    The defining mistake in staffing accounts.

  3. 03

    Job-board syndication traffic

    Arrives with no click identifier and drags coverage figures down.

  4. 04

    Assignment extensions

    A contract extended earns more margin than originally modelled.

  5. 05

    Read the Deduplicated indicator and the per-event match quality score, both read over seven days

    Match quality is where most Meta accounts lose attribution, and it's almost always normalization rather than coverage. An email hashed with a capital letter, or a phone hashed with brackets, produces a perfectly valid hash that matches nobody and errors nowhere. Normalize first, then hash, and read the score per event rather than overall.

Meta · IT staffing · prove

How it gets proven — Meta · IT staffing

Source of truth

The ATS for placements by start date and the CRM for client accounts — two reports, never summed

  • Filled roles reconciled per placement against what each platform reports.
  • Identifier coverage measured separately on the candidate and client funnels.
  • Contract margin models shown as calculations from your own assignment history.
  • Job-board traffic identified and excluded before coverage is quoted.
  • The Deduplicated indicator and the per-event match quality score, both read over seven days read directly, not inferred from an upload succeeding.

Meta · IT staffing · free audit

What we check in the free audit

  • Count records carrying fbclid and _fbc
  • One conversion action for candidates and clients
  • Job-board syndication traffic
  • Assignment extensions
  • Read the Deduplicated indicator and the per-event match quality score, both read over seven days

Checked against

The ATS for placements by start date and the CRM for client accounts — two reports, never summed

Get my free conversion tracking audit

Free30 minutesNo obligation

Meta · IT staffing · when not to buy

When you don't need this — Meta · IT staffing

  • If Meta already reports conversions that reconcile against the ats for placements by start date and the crm for client accounts within a few percent, this is working and there is nothing to buy.
  • Measure identifier coverage yourself first — pull your last hundred records and count how many carry fbclid and _fbc.
  • If you're advertising a business type Meta restricts data collection for — health being the obvious one — the parameters you can legitimately send are narrower, and that constraint should shape the build rather than be worked around.

Meta · IT staffing · what we deliver

What gets built — Meta · IT staffing

  • Click identifier captured on both funnels separately

    Candidate and client journeys live on different pages.

  • Carried into the ATS and the CRM

    Onto the candidate record and the company record respectively.

  • Filled role fires the conversion

    At the placement value with the placement type.

  • Fallouts inside the guarantee reversed

    Common enough in tech contracting to matter.

  • Dispatch via the Conversions API

    Server events go through CAPI with an action_source describing where the conversion happened. Offline outcomes flow through the same API rather than a separate product. Verify current field names against Meta's documentation before building — this surface changes.

Written guarantee

95%+ tracking accuracy

Measured against The ATS for placements by start date and the CRM for client accounts — two reports, never summed. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Meta · IT staffing questions, answered

Yes, any ad offering jobs, contract roles included, has to be declared under it in the US and some other markets. Ads selling staffing services to hiring companies are not job ads, but run them as separate campaigns.

Free · 30 min

Get Meta reporting what IT staffing firms actually earn

Free30 minutesNo obligation