Engaged with my content on LinkedIn

Know when prospects engage with the client's posts, the client's company page or the content of the client's team. It reads the posts of the client's own company page and of the people on the client's "All my employees" list. With account monitoring, only engagers from the client's key accounts are kept.

Set this signal up with POST /v3/partner/workspaces/{partner_workspace_id}/signal-setups: send the template's id as signal_template_id and the parameters below in parameters. Its id is in List a client's signal templates. Any parameter not listed here is refused with a 422.

Parameters

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_id defaults to the client's "All my employees" list: setup.fields shows its id as the default, it is stored when the setup is created and returned when you read it. Any employee list is accepted, and you can move the setup to another one later. null is refused like for any parameter that has a default. Find its id with List the lists of a client (type=employee), and add or remove people with Add members and Remove a member.
• setup.fields does not show the list_id default: the server applies it when the setup is created.
• The company page read is always the client's own: there is no company page parameter, and company_page is refused like any unknown parameter.
• Setting this signal up needs the client's persona to have at least one job title and one location, otherwise the request is refused with a 422. With several personas, send persona_id when 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:

Example

parameters of a setup:

{
  "scopes": ["account_monitoring"]
}

Read back with GET, the stored parameters carry the default list:

{
  "scopes": ["account_monitoring"],
  "list_id": 812
}