Skip to main content
Data Export lets you take everything Alex holds about your hiring out as CSV files, so you can report on it in a spreadsheet or load it into another system. For one row per candidate, application and round, bucketed the way the Analytics page counts them, use Export CSV on the Analytics or Analytics 2.0 page, or the API’s Analytics entity below.

Requesting an export

  1. Log into your Alex dashboard.
  2. Go to Settings → Data Export.
  3. Switch on each entity you want, and set its filters. The count next to each entity shows how many records the filters match.
  4. Enter one or more email addresses and click Start Export.
Alex builds one CSV file per entity, compresses them into a single ZIP archive, and emails a download link to every address you entered. The email also lists the filters each file was built with, so it can be filed as a record of the export. The same export is available over the Alex API: POST /data-exports queues it, GET /data-exports/{id} returns a signed download URL when it is ready.

History and reruns

The History tab lists every export your company has requested, who requested it, the entities and filters it covered, and when it was created. A completed export can be downloaded from the row. An expired export can be rerun: the rerun opens with the same entities and filters, which you can change before starting it.

The entities

Each entity is one file in the archive, with one row per record. Where your company is connected to an ATS, the ATS’s own identifiers appear in extra columns named after it, such as Bullhorn ID or Bullhorn Req ID.

Jobs

One row per job.

Candidates

One row per candidate, with their most recent application and interview.

Interviews

One row per interview. Test interviews are left out. What the columns hold:
  • Status is the interview’s status: APPLIED (created, invite not sent yet), SENT, OPENED, PENDING, SCHEDULED, ACTIVE, PAUSED, INCOMPLETE, UNDERREVIEW, COMPLETED, CANCELLED, WITHDRAWN, EXPIRED, OUTREACH_FAILED (every way of sending the invite failed, so the candidate was never contacted) or REQUESTED_HUMAN (the candidate asked to speak with a person instead). A scheduled interview that never took place keeps SCHEDULED; the Status filter’s Missed option selects those whose time passed more than an hour before the export ran, and its Scheduled option selects the rest, including scheduled interviews with no time set.
  • Date Created is when the interview was created, which can be before its invite was sent.
  • Transferred is Yes when a phone interview was transferred live to a recruiter.
  • Handoff Status is the state of the recruiter call the candidate was handed off to: PENDING (invited to book, not booked yet), SCHEDULED, COMPLETED, MISSED, RECRUITER_CANCELLED or NO_AVAILABILITY (no recruiter time could be offered). It is blank when there was no handoff. A missed recruiter call shows here, not in Status.
  • Handoff Missed Reason is CANDIDATE_NO_SHOW or RECRUITER_NO_SHOW when it is known which side did not attend a missed recruiter call.

Activity

One row per event on a candidate’s Activity thread: every message, call, interview, workflow step, ATS write, task, note, application, status change and recruiter-call handoff, in the order it happened. It is the same thread you see on the candidate’s Activity tab. The export covers every candidate with an interview on the jobs you choose (any job when you choose none) that was created in the date range you choose, including interviews whose invite has not been sent yet. Test interviews do not count. Each candidate’s rows are their whole history, on every job, not only the events inside the range or on the chosen jobs. A date range is required, and one export covers up to 5,000 candidates; narrow the date range or the jobs to export more in parts. What the columns hold:
  • Kind is the event’s type: message, call, interview, step, ats, task, note, application, status, handoff, click, tailoredResume, surveyOpen or doNotContact.
  • Actor is who did it: alex, candidate, system, or the name of the recruiter or outside sender.
  • Channel, Direction and Recipients are filled for messages: email, sms or whatsapp; in or out; and the address the message went to when the row records one.
  • Event is the one-line summary: a message’s subject, a call’s title, a workflow step’s name, a task’s name, a status change’s new status, a handoff call’s title, a tax credit survey open and how many times the candidate has opened that link, or a Do Not Contact change your webhook made.
  • Outcome is how it ended: a step’s result or state, a task’s state, what changed a status (ats:Bullhorn, dashboard, withdrawal, reopen), a handoff’s outcome (booked, rescheduled, cancelled, missed, no_availability, completed), an interview’s recommendation, whether the tax credit survey is completed yet, or why a message or call failed.
  • Detail is what the event did, flattened: the fields a step wrote, the clauses a filter checked, the values a task collected, an interview’s score and duration, a handoff’s booked time and host, a Do Not Contact change’s new value. It is capped at 1,000 characters.
  • Text is the full text of a message, up to 5,000 characters.
  • Internal is Yes for events the candidate never saw, such as a note to the recruiter or a workflow step.
  • Ended At is when a step that took time, or a task, ended.

Tasks

One row per task Alex ran: the task’s name, when it was created, and how and when it ended. A task is anything a workflow’s Start Task step asks Alex to carry out, such as delivering an offer letter, collecting a document or confirming details. What the columns hold:
  • Task is the name of the task definition the task ran on. It is blank for a task defined inline on the workflow step.
  • Kind is CUSTOM for a task Alex carries out in conversation with the candidate, or CONNECTOR for one carried out by a connected service.
  • Status is QUEUED, ACTIVE, COMPLETED, EXPIRED, CANCELLED or ERROR.
  • Created, Completed and Deadline are when the task was created, when it ended, and when Alex stops waiting for it. Completed is blank while the task is still running; Deadline is blank for a task with no deadline.
  • Completion Source is how the task ended: reply, signal, trigger, webhook, manual, expired, delivered, or history when everything the task needed was already known and nobody was contacted. It is blank while the task is still running.
  • Completion Reason is a short explanation of why the task ended.

Unanswered Questions

One row per question candidates asked that Alex could not answer.

Interview Q&A

One row per interview question and the candidate’s answer. Pick at least one job, and choose the columns to include.

Analytics

Available over the Alex API only. In the app, the same file is Export CSV on the Analytics 2.0 page. The Analytics 2.0 page’s Export CSV for the whole company: one row per application and round, with the same columns, buckets, hours saved and task columns. The Analytics export section describes every column, including which ones repeat on each round row of an application and how to count them.
  • Invited date picks applications whose first interview was created in the range, then follows each of them through every later round, as the page does. It takes one of last_5_days, last_10_days, last_30_days, all_time, or custom:YYYY-MM-DD:YYYY-MM-DD; any other value is rejected. Leave it out to cover every application. The range ends no later than the moment the export starts, so the whole file is one snapshot.
  • The page’s WhatsApp source and live-transfer filters are not available here.
  • The file covers the whole company. The page’s export covers only the jobs the viewer’s role can see.
  • An Analytics export can’t be rerun from History; request it again over the API.