This page outlines the recommended user experience for integrating Ad Sync into your software, with a focus on avoiding duplicate job ads and giving hirers a clear path to post a curated job ad via classic or Enhanced Job Posting when needed.
- Configure integration: Once a hirer has signed an Ad Sync agreement with SEEK and configured their posting rules, your software should provide an interface where a hirer can configure their SEEK Ad Sync ID.
- Create a job ad: The default assumption should be: “If I publish a position, a SEEK job ad will be posted automatically via Ad Sync.“ Your software should always offer a classic or Enhanced Job Posting option for hirers who want more control over a particular job ad.
- Prevent job ad duplication: When a hirer chooses a classic or Enhanced Job Posting alternative, your software should send
seekPostingMethod: 'Other'in thesyncPositionsmutation to indicate that Ad Sync should not manage the posting. If a position already has a SEEK job ad and the hirer attempts to create another SEEK ad for the same position, encourage the hirer to edit the existing job ad rather than creating a new one.The hirer can still post multiple job ads if needed, but your software should discourage it when it appears unintentional. - Display status & source: Once you’ve synchronised the position to SEEK, your software should surface the resulting job ad and its source in your software with its current status
- Edit an Ad Sync job ad: Your software should allow Ad Sync job ads to be edited via classic or Enhanced Job Posting.Display a message to inform the hirer that once they manually edit a job ad, changes from the requisition will no longer sync automatically to it. Further changes to the job ad can be managed through classic or Enhanced Job Posting.
Step | Requirement | Rationale |
|---|---|---|
Configuration | Provide an interface for hirers to specify their SEEK Ad Sync ID and select a company identifier field for multi-account mapping. | Integration cannot function without it. |
Create a job ad | Always trigger Ad Sync when a job is posted externally. Always offer classic or Enhanced Job Posting as an alternative; if selected, call Ad Sync with seekPostingMethod: 'Other'. | Gives hirers flexibility and prevents duplicate ads. |
Create a job ad | Display a message that positions will be posted via Ad Sync by default. | Good UX practice to set expectations. |
Create a job ad | If no classic or Enhanced Job Posting ad is selected, send the Ad Sync ad or prompt the hirer to confirm. | Core Ad Sync functionality. |
Create a job ad | Pass one location per Ad Sync position, materialise multi-location requisitions as separate Ad Sync ads. | SEEK will reject ads with multiple locations. |
Display status | Consume lifecycle events via webhooks and display the current status of Ad Sync job ads. | Hirers need visibility into what happened to their ad. |
Display status | If an Ad Sync position is not posted, allow the hirer to edit the requisition or post via classic or Enhanced Job Posting. | Fallback path, to ensure all ads are posted. |
Edit an Ad Sync job ad | Support classic or Enhanced Job Posting editing of Ad Sync job ads. Show a message that if the hirer edits the job, future changes from the requisition won’t sync automatically. | Improves control for power users. |
Prevent duplication | Detect existing SEEK job ads and warn hirers before they create a duplicate. | Discourages accidental duplication but hirers can still post multiples intentionally. |