Apply Link Tracking
Control the query string Cavuno appends to outbound Apply links, including Off, Auto, Custom, and per-feed overrides for destinations that reject unexpected parameters.
A
JHosted Apply buttons can append a short query string so destination ATS or career sites can attribute traffic back to your board. Some upstream hosts reject unexpected query parameters (for example TYPO3 cHash or other signed URLs) and return 404. Apply link tracking lets you choose what, if anything, Cavuno appends.
Tracking is decided at click time (and in the apply gateway). Job records never store a stamped URL.
Before you begin
Decide whether most destinations accept an extra query parameter. If only some import feeds break, keep the board on Auto and turn tracking Off on those feeds. If a partner requires specific keys (utm_*, source, and similar), use Custom on the board or on that feed.
Board modes (Settings → Features)
- Go to Settings → Features
- Find Apply link tracking
- Choose a mode and save
| Mode | What gets appended | When to use |
|---|---|---|
| Off | Nothing | Destinations reject unknown query params, or you do not want outbound tagging |
| Auto | ref=<live board host> | Default for almost every board. The host follows domain changes |
| Custom | The query string you enter (for example ?utm_source=board&utm_campaign=jobs) | A partner or analytics contract needs a specific shape |
Auto is a named product mode, not a frozen string. Today it means ref plus your live board host. Unset board config behaves as Auto, so existing boards keep historical ?ref= behavior.
Custom field rules
- Enter a query string with or without a leading
? - If a value is exactly your live board host, Cavuno stores it as a host template so it keeps updating when the domain changes
- Blank Custom saves as Off
- A Custom string that is exactly the Auto shape is stored as Auto
Feed override (Jobs → Import)
Each import feed can override the board policy for jobs from that feed:
- Go to Jobs → Import
- Open the feed
- Set Apply link tracking to Inherit board default, Off, or Custom
| Mode | Behavior |
|---|---|
| Inherit board default | Use the board Features policy |
| Off | Append nothing for jobs from this feed |
| Custom | Use this feed’s query string instead of the board’s |
Feed Custom replaces the board policy (no merge). Use Off on feeds whose apply URLs break when any query param is added, while leaving the board on Auto for everything else.
Where stamping happens
- Hosted Apply button (before other click trackers)
- Apply gateway when creating an outbound intent
- Never when saving the application URL on the job
Both paths use your board’s canonical public host from the server. Preview hosts, www vs apex, and local ports cannot diverge from production.
Recommended setup
- Leave Features on Auto unless you have a reason not to
- For a broken destination, set that feed to Off first (narrowest fix)
- Only set the board to Off if every outbound Apply must stay clean
- Use Custom when a partner asks for specific keys
Verify the setting
Open a public job in a private window, click Apply, and inspect the destination URL in the address bar or network panel. Confirm Auto adds ref= with your live host, Off adds nothing, and Custom matches the string you saved. For a feed override, open a job from that feed and confirm only that feed’s policy applies.
API
Board policy is exposed on GET / PATCH /v1/settings as applyUrlAttribution:
{ "mode": "off" }appends nothing{ "mode": "append", "params": [{ "key": "ref", "valueTemplate": "{{boardHost}}" }] }matches Auto- Absent config means the Auto default (
ref={{boardHost}})
See the API reference for the full schema, including Custom params and feed overrides.
Related guides
- Recurring XML feeds: Import feeds where per-feed Off is often the right fix
- Password protection: Another Settings → Features control
- MCP settings reference: Agent-facing settings operations