Integrations

Integrations#

Overview#

Tafkar integrates with 36 Applicant Tracking Systems (ATS), split into three categories:

Bidirectional (22 systems)

Vacancies are imported and applications are submitted back to the ATS via API.

External URL (9 systems)

Vacancies are imported. Applicants are redirected to the ATS-hosted application page.

Embedded Form (5 systems)

Vacancies are imported. Applications are submitted through ATS-provided embedded forms or widgets.

Bidirectional Systems#

These systems support vacancy import and application submission via Tafkar forms with API submission:

  • AFAS

  • Bullhorn

  • Carerix

  • Connexys

  • Cornerstone

  • Emply

  • Greenhouse

  • Homerun

  • HR Office

  • Jobylon

  • JobylonV2

  • Otys

  • Recruitee

  • RecruiteeAts

  • SmartRecruiters

  • SuccessFactors

  • Talentsoft

  • Teamtailor

  • Tigris

  • Trakstar

  • Webqube

  • Workday

Import-Only Systems#

External URL Redirect#

Applicants are redirected to the ATS-provided application URL.

  • Avature

  • CV Warehouse

  • Daywize

  • Digital Recruiters

  • Easycruit

  • Harver

  • Jobvite

  • Netive

  • Salesforce

Embedded Forms#

Applications use embedded forms or widgets provided by the ATS.

  • Byner: JavaScript embed with dynamic form IDs per vacancy

  • ConnexysJson: JSON-based form variant of Connexys import

  • Hireserve (Ubeeo V1): Widget-based integration with referral tracking

  • HomerunJSON: JSON-based form variant of Homerun import

  • UbeeoV2: Iframe embed with Hireserve fallback

UTM Parameter Support#

Tafkar captures UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content, utm_id) from landing page URLs via JavaScript (first-touch attribution, requires marketing cookie consent). These are forwarded to ATS systems that support them during application submission.

Import-only systems (External URL and Embedded Form) do not receive UTM data since Tafkar does not submit applications to them.

ATS

supported

parameters sent

method

AFAS

yes

utm_source

configurable custom field

Bullhorn

no

Carerix

yes

utm_source, utm_medium, utm_campaign, utm_term, utm_content, utm_id

XML applySource + applyTags nodes (feature-flagged)

Connexys

yes

utm_source (defaults to “Website”), ga_client_id, ga_tracking_id, utm_custom

utmSource field on Registration object; GA parameters via hidden form fields (Salesforce embed)

Cornerstone

yes

utm_source

submissionSource field

Emply

yes

utm_source

mapped to sourceMediaId UUID (project-specific)

Greenhouse

no

Homerun

no

HR Office

no

Jobylon

yes

utm_source

originalReferrer field

JobylonV2

yes

utm_source

originalReferrer field

Otys

yes

utm_source, utm_medium, utm_campaign, utm_term, utm_content

JSON UtmTags object in custom fields

Recruitee

yes

utm_source

candidate[referrer] form field

RecruiteeAts

no

SmartRecruiters

no

SuccessFactors

no

Talentsoft

yes

utm_source, utm_medium, utm_campaign, utm_term, utm_content, utm_id

custom block fields (project-specific mapping)

Teamtailor

no

Tigris

yes

sourceUrl

UTM_URL_long__c custom field

Trakstar

no

Webqube

yes

utm_source, utm_custom, ga_client_id, ga_tracking_id

direct JSON fields in application body

Workday

yes

utm_source

XML source node (project-specific mapping)

Application Status Feedback#

Some ATSs receive the applicant’s Google Analytics client ID (ga_client_id) and tracking ID (ga_tracking_id) alongside the application data. When the application status changes in the ATS, it can call back to Tafkar’s webhook endpoint (POST /webhooks/ga-event), which forwards the event to Google Analytics via the Measurement Protocol. This enables conversion tracking in GA for recruitment campaigns.

Both GA4 and Universal Analytics (GA3) are supported — the tracking ID format (G- vs UA-) determines which protocol is used.

Data flow:

  1. Applicant lands on job page — JavaScript captures GA client ID from the browser

  2. Application is submitted — ga_client_id and ga_tracking_id are sent to the ATS with the application

  3. Application status changes in the ATS (e.g. candidate is hired)

  4. ATS sends a webhook to Tafkar with the status, client ID, and tracking ID

  5. Tafkar forwards the event to Google Analytics as a conversion event

Supported event types:

  • ContractProposition

  • Denied

  • FirstInterview

  • Hired

  • Rejected

  • SecondInterview

  • Withdrawn

ATS support:

  • Connexys (Salesforce embedded form) — JavaScript injects ga_client_id, ga_tracking_id, and utm_custom into hidden form fields before submission

  • Webqube — sends ga_client_id and ga_tracking_id as direct JSON fields in the application body

ATS Documentation#