Mentioned competitor brand on LinkedIn
Parameters, defaults and rules of the "Mentioned competitor brand on LinkedIn" signal template.
Know when prospects mention a competitor on LinkedIn: posts naming the competitors of your company.
| Key | mentioned-competitor-brand-on-linkedin |
| Category | competition |
| 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. |
| keywords | array of string | No | At least one keyword | The names of the companies in your competitor lists (see below) | The competitor names to look for. |
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
keywordsout, the names of the companies in your competitor lists are stored. Archived or deleted competitor lists are ignored. There is no limit on how many. - One persona: every company of every competitor list is used.
- Several personas: the companies of the competitor lists linked to the setup's persona, plus the lists linked to no persona. Pass
persona_idwhen you create the setup. - Each company is named by its name when known, otherwise by the first part of its domain (
hubspot.co.ukbecomeshubspot). - Keywords you send always win over the default. Sending
keywords: []is refused. - The list and get routes show this default for one persona when you pass
persona_idtoGET /v3/signal-templates. In a workspace with several personas, withoutpersona_id, this property carries nodefault. It carries none either when there is no company to name, because the competitor lists are empty. - 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.keywords is left out and your workspace has no competitor list holding a company. Set up a competitor list first, or add keywords. |
| 422 | parameters.keywords is empty. Send at least one keyword. |
| 409 | The signal template is archived. |
Example
parameters of a setup:
{
"scopes": ["account_monitoring"],
"keywords": ["hubspot", "salesforce"]
}