Meta Conversions API for lead quality: send interviews and hires

What it does

Meta's delivery system looks for people likely to complete the event an ad set optimizes for. If that event is a click on a WhatsApp or contact button, Meta gets very good at finding people who click, and they are not always the people who show up to an interview. The pixel cannot see what happens next, because the conversation and the hiring decision happen outside the website. The Conversions API lets your server tell Meta about those later steps, so reporting and, with enough volume, optimization can move deeper into the funnel.

Every server event needs an event name, an event time, an action source and customer information that lets Meta match it to a person who saw or clicked an ad. Hashed email and phone give the strongest match, but you do not need them to connect an event to an ad click. The fbc value carries the fbclid that Meta adds to ad links and is usually kept in the _fbc cookie; fbp is Meta's browser ID from the _fbp cookie. Events with only these marks have lower match quality than events with contact details, which is the price of sending less data. Keep redirects from stripping URL parameters, or the fbclid is lost before your site can store it.

Timing matters. Meta accepts website server events only for a limited time after they happen, about seven days, and it credits conversions to ads within the ad set's attribution setting, where 7-day click is a common default. An interview held a month after the click may never be attributed. So send the event when the status changes, not in a monthly batch, and keep screening quick. If the pixel and the server ever send the same event, give both the same event name and event ID so Meta can deduplicate them. Check Meta's current documentation for the exact windows.

Using the events in campaigns is a separate decision. A custom event such as Interview can become a custom conversion and then be chosen as the optimization event, but an ad set generally needs about 50 optimization events in a week to exit Meta's learning phase. Most recruiting accounts do not have that many interviews. A practical path is to keep optimizing for the contact event, use Interview and Hire to judge ad sets, audiences and creatives, and test optimizing for interviews once volume allows.

In AdAce Ads the lead tracking script stores Meta's click marks fbc and fbp when a visitor taps a contact button. When that lead is marked “interview” or “hired” in Telegram or in the service, the service sends a server event, Interview or Hire, through the Conversions API with the fbc click mark and a hashed lead id. No names, phone numbers or emails are sent, and the script never collects them in the first place. The workspace emergency switch pauses sending. The same statuses also feed cost per interview and per hire by campaign and by candidate language.

Why it helps

• Meta sees which ad clicks turned into interviews and hires.
• No personal data leaves your pipeline: only the click mark and a hashed id.
• Ad sets and creatives can be compared by interviews, not by taps.
• A status tap in Telegram is enough; there are no manual uploads.

How to set it up

1. Install the lead tracking script from “Analytics” → “Leads” on the client's site.
2. Make sure Meta ads link to the site directly or through redirects that keep the query string, so the fbclid survives.
3. Mark leads “interview” or “hired” in the client's Telegram topic or in the service on the day it happens.
4. After the first marks, check in Meta Events Manager that Interview and Hire events are arriving.
5. If interview volume is high enough, create a custom conversion on Interview in Meta and test it as an optimization event.

Good to know