Archer uses a feed of jobs from SAP SuccessFactors so your jobs are posted and paused automatically between SAP SuccessFactors and hackajob.
This setup only needs to be done once.

What You’ll Need To Share

1. Attribution Method: Share how applications are attributed to hackajob, usually by appending a suffix to the application URL (see Source Attribution section below).

2. Job feed access: Either confirm your career portal URL or provide an XML/RSS/JSON feed of open roles (see Job Feed section below).

The hackjob team will use both to get everything connected and tested.

Source Attribution

Source attribution ensures that when a candidate applies through hackajob, the application is recorded with hackajob as the source in your SuccessFactors reporting. This works using a standard URL parameter that SAP SuccessFactors already supports.

How It Works

When Archer sends a candidate to apply for a role, it appends a tracking parameter to the application URL. For example:

https://careers.successfactors.eu/careers?company=yourcompany&career_job_req_id=12345&jobPipeline=hackajob

The key parameter is jobPipeline=hackajob. This is a standard SuccessFactors mechanism used by all major job boards. Archer handles appending this parameter automatically, no development work is required on your side.

What Your SAP Team Needs to Do

Your SuccessFactors administrator simply needs to verify that:

• The jobPipeline parameter is recognised and tracked in your SuccessFactors instance.

• The value hackajob appears correctly in your source reporting (e.g. the Job Board Name column in Ad Hoc Reports, or the Source field on applications).

If your organisation uses Career Site Builder (CSB) rather than the classic career portal, source tracking may use UTM parameters instead. Please let your CSM know which career site you use, and we’ll confirm the correct attribution approach.

Job Feed

Archer needs visibility of your open roles so it can source and invite relevant candidates. There are two options:

Option A: Job Feed

If a direct feed is preferred, your SAP team can provide one of the following:

• XML feed: a standard job posting XML feed URL

• RSS feed: an RSS feed of open positions

• JSON API: a JSON endpoint exposing job requisitions

Option B: Career Portal

If your jobs are publicly listed on your SuccessFactors career portal, Archer can capture them directly. This is the simplest approach, no action is required from your team. Simply share your career portal URL with your CSM and we’ll handle the rest.

Feeds can be open (publicly accessible) or authenticated using API keys. If authentication is required, your SAP team will need to provide API documentation, endpoint URLs, and credentials to your CSM.

Setup Steps

Step 1: Share Details with Your CSM

Send your CSM the following:

• Your career portal URL

• Confirmation of how source attribution is tracked (jobPipeline or UTM)

• If using a feed: the feed URL and any authentication details

Step 2: We Test Everything

Your CSM will configure the integration, verify that jobs are being captured correctly, and test that applications are attributed to hackajob in your SuccessFactors reports.

Step 3: Go Live

Once testing is complete, Archer begins sourcing and inviting relevant candidates. Your roles will update automatically and applications will flow into SuccessFactors, no extra work needed.

Appendix: Technical

For your SAP SuccessFactors Administration Team

This appendix provides the technical details your SAP SuccessFactors team will need to support the hackajob/Archer setup. It covers source attribution configuration and job feed options.

1. Source Attribution Configuration

hackajob uses the standard jobPipeline URL parameter to attribute candidate applications. This is the same mechanism used by Indeed, LinkedIn, and other major job boards integrated with SuccessFactors Recruiting.

1.1 Mechanism

When a candidate applies through hackajob, the apply URL includes the following parameter:

&jobPipeline=hackajob

A full apply URL follows this pattern:

https://{career-site}.successfactors.eu/careers?company={company_id}&career_job_req_id={req_id}&jobPipeline=hackajob

This parameter is appended automatically by hackajob’s platform. The value hackajob is then stored in the SuccessFactors database and appears in:

• The Job Board Name column in Ad Hoc Reports

• The Source field in the Application section of candidate records

1.2 Verification Steps

To verify that attribution is working correctly:

1. Confirm that the jobPipeline parameter is enabled and tracked in your SuccessFactors Recruiting instance. This is a standard feature, if you are already tracking sources from other job boards (e.g. Indeed), no additional configuration is needed.

2. Submit a test application using a URL containing &jobPipeline=hackajob and verify the source appears correctly in your reporting.

3. Confirm the value appears in the Ad Hoc Report under the Job Board Name column.

4. hackajob will also submit test applications during setup.

1.3 Career Site Builder (CSB) Considerations

If the organisation uses Career Site Builder rather than the classic SuccessFactors career portal, source tracking may use UTM parameters (utm_source, utm_campaign) instead of, or in addition to, the jobPipeline parameter. In this case:

• hackajob can be configured as a source using: utm_source=hackajob

• The Campaign URL Builder under Recruiting → Source Tracker can be used to verify the tracking configuration.

• Please confirm which career site version is in use so that the correct attribution method can be applied.

1.4 SAP Reference Documentation

The following SAP Knowledge Base Articles provide additional detail on the jobPipeline mechanism:

These articles are available on the SAP Support Portal (login required).

2. Job Feed Options

hackajob requires access to the organisation’s open job requisitions. There are two supported approaches:

2.1 Structured Job Feed

If a structured feed is preferred, the following formats are supported:

Authentication

Feeds can be either publicly accessible or secured with authentication. If authentication is required, please provide:

• API endpoint URL(s)

• API key or OAuth credentials

• API documentation (endpoints, request/response schemas, rate limits)

• Any IP whitelisting requirements

2.2 Career Portal

hackajob can capture jobs directly from the public career portal. This approach requires no action from the SAP team. Archer will automatically detect and sync open roles from the career site URL.

This is the recommended approach as it requires no feed configuration, API credentials, or ongoing maintenance.

3. Summary Checklist

Please provide the following to your hackajob Customer Success Manager:

For questions or support, please contact your hackajob Customer Success Manager.