Job change
Parameters, defaults and rules of the "Job change" signal template.
Spot decision-makers who join or get promoted: new roles review vendors in their first months. With account monitoring, it looks among the people of your key accounts; with Discovery, anywhere.
| Key | job-change |
| Category | people |
| Watches | person |
| Setups | Discovery and account monitoring |
Set this signal up with POST /v3/signal-setups: send the template's id as signal_template_id and the parameters below in parameters. Its id is in List signal templates. Any parameter not listed here is refused with a 422.
Parameters
| Parameter | Type | Required | Allowed values | Default | Description |
|---|---|---|---|---|---|
| scopes | array of string | Yes | discovery, account_monitoring (at least one) | — | Where the signal looks. |
| use_persona_job_titles | boolean | No | true, false | true | Whether to also use the job titles of your persona, read at each run. |
| job_titles | array of string | No | Job titles | [] | The job titles Discovery searches for, on top of the persona's when use_persona_job_titles is true. Account monitoring is not filtered by title. |
| job_changes | array of string | No | new_company, promotion (at least one) | ["new_company", "promotion"] | Which job changes count: a move to a new company, a promotion, or both. |
Default is what the server stores when you leave the parameter out. — means there is no default: the parameter is required, or it is simply not set.
Rules
- When you leave
use_persona_job_titlesout, it istrue. The persona's job titles are read at each run, never copied into the setup, so the signal follows any later change to the persona. - The titles you send in
job_titlesare added to the persona's. To search only for your own titles, senduse_persona_job_titles: false. - Setting this signal up needs your persona to have at least one job title and one location, otherwise the request is refused with a
422. With several personas, sendpersona_idwhen you create the setup (see Create a signal setup).
Errors
A parameter that is missing, of the wrong type, or not an allowed value is refused with a 422 that names it under errors, for example parameters.scopes. These errors are specific to this signal template:
| Status | Cause |
|---|---|
| 422 | persona_id: the persona has no job title or no location (title Persona incomplete). Add what is missing to the persona first. |
| 422 | parameters.job_titles is empty while use_persona_job_titles is false. Send at least one job title. |
| 422 | parameters.job_changes is empty or holds another value. Send new_company, promotion or both. |
| 409 | The signal template is archived. |
Example
parameters of a setup:
{
"scopes": ["discovery", "account_monitoring"],
"use_persona_job_titles": true,
"job_titles": ["Head of Sales"],
"job_changes": ["new_company", "promotion"]
}