Application signals track the progression of SEEK candidates through the recruitment process.
Feeding these back to SEEK helps to improve our search & recommendation capabilities,
and ultimately match candidates with the optimal positions on offer.Signal capture is required if the candidate used SEEK to apply for the position.
This includes:
The first signal that we capture from the external recruitment process is the application complete signal.
Note that an application complete signal does not imply a candidate source or Apply with SEEK usage;
Ad Performance analytics will only attribute completed applications where the candidate source is SEEK.Pass the The 
Pass the following correlating identifiers:Once your software has received a completed application from SEEK’s Apply Form,
subsequent status updates represent the candidate’s progress through the recruitment process.
Pass the
- Discovering the position through a SEEK job ad
- Using SEEK’s Apply Form
- Using Apply with SEEK to pre-fill an external apply form
Advertised on SEEK | Application source | Application method | Using Apply with SEEK | Send application completes? | Send application status updates? |
|---|---|---|---|---|---|
SEEK job ad | |||||
SEEK job ad | |||||
SEEK job ad | External apply form | ||||
Other source | External apply form | ||||
Other source | External apply form | ||||
Other source | External apply form | ||||
Other source | External apply form |
seek-token persisted from SEEK job ad or Apply with SEEK redirection as the correlating identifier.MutationVariables
CopyGraphQL Explorer
{"input": {
"typeCode": "ApplicationComplete",
// The identifier to correlate the signal back to SEEK job ad or Apply with SEEK redirection.
"token": "globalPublicTest-WfRFAhG25YC8ADe3QvxAVz",
"timestamp": "2020-01-02T00:00:00.000Z"
}
}ApplicationComplete signal represents a bespoke state—the completion of the application subprocess—so it does not require current and previous states to be supplied.The optional timestamp field can be provided to indicate when the application was completed by the candidate.Follow the relevant application complete signal guidance for Apply with SEEK or Ad Performance.Once a candidate has completed the external apply form for a given position,
subsequent status updates represent the candidate’s progress through the recruitment process.seek-tokenpersisted from SEEK job ad or Apply with SEEK redirectionpositionProfileIds of the SEEK job ads that correspond to the relevant positionAn array is accepted as the position may have been advertised on SEEK more than once. These identifiers are available in thePositionProfilePostedevent from Job Posting.
MutationVariables
CopyGraphQL Explorer
{"input": {
"typeCode": "ApplicationStatusUpdate",
// The identifier to correlate the signal back to SEEK job ad or Apply with SEEK redirection.
"token": "globalPublicTest-WfRFAhG25YC8ADe3QvxAVz",
// The identifiers to correlate the signal back to SEEK job ads.
"positionProfileIds": "seekAnzPublicTest:positionProfile:jobAd:27cuZeA47",
"current": {
// Omit `phase` if your software does not support hierarchies.
"phase": {
"label": "Hired",
"index": 5,
"total": 7
},
"status": {
"label": "Hired",
"index": 11,
"total": 14
},
"success": true,
"timestamp": "2020-01-02T00:00:00.000Z"
},
// Omit `previous` if your software does not track prior states.
"previous": {
"phase": {
"label": "Offer",
"index": 4,
"total": 7
},
"status": {
"label": "Offer accepted",
"index": 8,
"total": 14
},
"success": null,
"timestamp": "2020-01-01T00:00:00.000Z"
}
}
}candidateApplicationProfileId of the SEEK job application as the correlating identifier.This identifier is available in the CandidateApplicationCreated event from Optimised Apply.MutationVariables
CopyGraphQL Explorer
{"input": {
"typeCode": "ApplicationStatusUpdate",
// The identifier to correlate the signal back to the SEEK job application.
"candidateApplicationProfileId": "seekAnzPublicTest:candidateProfile:apply:5G5NaFDmy7UigvGy6aT6VT",
"current": {
// Omit `phase` if your software does not support hierarchies.
"phase": {
"label": "Hired",
"index": 5,
"total": 7
},
"status": {
"label": "Hired",
"index": 11,
"total": 14
},
"success": true,
"timestamp": "2020-01-02T00:00:00.000Z"
},
// Omit `previous` if your software does not track prior states.
"previous": {
"phase": {
"label": "Offer",
"index": 4,
"total": 7
},
"status": {
"label": "Offer accepted",
"index": 8,
"total": 14
},
"success": null,
"timestamp": "2020-01-01T00:00:00.000Z"
}
}
}