Engaged with my partners on LinkedIn
Parameters, defaults and rules of the "Engaged with my partners on LinkedIn" signal template.
Know when prospects engage with your partners on LinkedIn: let your partner open the door. It reads the activity on the pages and the shared content of the companies of a partner list.
| Key | engaged-with-my-partners-on-linkedin |
| Category | my_network |
| 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 |
|---|---|---|---|---|---|
| list_id | integer | Yes | The ID of one of your partner lists, from GET /v3/lists | — | The partner list to watch. |
| scopes | array of string | Yes | discovery, account_monitoring (at least one) | — | Where the signal looks. |
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
list_idcarriesx-list-type: partnerin the response. No list is created for you. You can move the setup to another list later.- 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 | parameters.list_id is missing, or does not reference an existing partner list in this workspace. |
| 409 | The signal template is archived. |
Example
parameters of a setup:
{
"list_id": 9,
"scopes": ["discovery"]
}