> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plyne.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Signal Types

> Understand what each Plyne signal looks for, how it is configured, and how to read its results through the API.

Discover what brings a Lead or Account into your results: content engagement, profile matches, hiring activity, or technology usage. Each signal connects a record to the evidence behind its discovery.

Names, icons, and colors match the portal. Open a card’s details for configuration guidance, evidence interpretation, and its API type ID.

## Signal Agent sources

Choose sources and criteria in the portal. Use the API to retrieve the saved results and explore their signal history.

> [card] You & Your Company
>
> People engaging with posts from your LinkedIn company page or personal profile.
>
> > [accordion] Configuration & evidence
> >
> > * **Configure:** Your LinkedIn company page, your personal LinkedIn profile, or both.
> > * **Read the finding:** The relevant post or interaction and the person's profile provide the context for qualification. An engagement shows contact with your content; it does not establish purchase intent by itself.
> > * **API type:** `your_company_engagement_signal`

> [card] Competitor Engagement
>
> People engaging with posts from the competitor company pages you follow.
>
> > [accordion] Configuration & evidence
> >
> > * **Configure:** Competitor company pages. The portal also lets you exclude people who work at those competitors.
> > * **Read the finding:** Inspect the source post and recorded interaction to understand what drew the person's attention. This does not mean the person uses the competitor's product or intends to switch.
> > * **API type:** `competitor_engagement_signal`

> [card] Post Engagers
>
> People engaging with LinkedIn posts about the topics and keywords you track.
>
> > [accordion] Configuration & evidence
> >
> > * **Configure:** Keywords, the post date range, and whether to include post authors. When enabled, authors are also evaluated as potential Leads.
> > * **Read the finding:** The matching post and interaction explain the topic connection. The keyword match is on the post, rather than necessarily on the person's own profile.
> > * **API type:** `topic_engagement_signal`

> [card] Industry Experts
>
> People engaging with posts from the experts and creators you follow.
>
> > [accordion] Configuration & evidence
> >
> > * **Configure:** The LinkedIn profiles you want to watch.
> > * **Read the finding:** The watched profile supplies the content source; the discovered person is a participant in that content's audience. The discovered person is not necessarily the expert whose profile you configured.
> > * **API type:** `profile_engagement_signal`

> [card] Recent Updates
>
> People matching your ICP who recently changed roles or published on LinkedIn.
>
> > [accordion] Configuration & evidence
> >
> > * **Configure:** Recent job changes, recently active profiles, or both. The job-change window controls how far back to look for a role change.
> > * **Read the finding:** Check whether the saved evidence concerns a job change or recent publishing activity. These are different reasons for discovery, even though they share one signal type.
> > * **API type:** `recent_job_changes_signal`

> [card] Skills & About
>
> People whose profile skills, About section, or headline match your criteria.
>
> > [accordion] Configuration & evidence
> >
> > * **Configure:** Skills, About/headline keywords, or both, alongside the agent's ICP.
> > * **Read the finding:** A profile match describes declared experience or interests. It is a profile-based discovery signal and may not correspond to a recent event.
> > * **API type:** `skills_about_signal`

> [card] Hiring Activity
>
> Companies hiring for your target roles, and relevant contacts at those companies.
>
> > [accordion] Configuration & evidence
> >
> > * **Configure:** Hiring criteria such as role titles, description keywords, job location, and posting age, together with the target account and contact profile.
> > * **Read the finding:** A matching job posting is company-level evidence. A discovered contact works at the matching company; the posting does not imply that this contact personally published the job or owns the hiring process.
> > * **API type:** `hiring_signals`

> [card] Tech & Product Stack
>
> Companies using or mentioning your target technologies, and relevant contacts there.
>
> > [accordion] Configuration & evidence
> >
> > * **Configure:** Target technology groups and the available company, job-evidence, and contact criteria in the portal.
> > * **Read the finding:** Evidence may come from technology observations and supporting job postings. A finding can establish relevant technology usage or mentions without proving the exact date a company adopted a product.
> > * **API type:** `tech_stack_signals`

## Read signal results

Use `signal_types` on [Leads](https://docs.plyne.ai/signals/leads.md) or [Accounts](https://docs.plyne.ai/signals/accounts.md) to select entities associated with a source. The returned `evaluation` contains the selected assessment and its linked findings. Those findings can have a different type from the source that matched your filter.

Use [Lead signal history](https://docs.plyne.ai/signals/lead-signals.md) or [Account signal history](https://docs.plyne.ai/signals/account-signals.md) to inspect the individual findings for one entity. The same type filter restricts history entries themselves. Older findings remain available while retained, including unqualified or unclear findings that do not appear as current qualified results.

```json Example filter theme={null}
{
  "signal_types": ["topic_engagement_signal", "profile_engagement_signal"],
  "cursor": { "limit": 50 }
}
```

`found_at` is when Plyne saved a finding. History's `observed_at` is the source observation time when available, and is `null` otherwise. A profile match, job posting, and social interaction can have different source dates and evidence availability. See the [Data Dictionary](https://docs.plyne.ai/api/data-dictionary.md) for the complete field definitions.

## Other sources in saved results

Saved results can also contain contact recommendations and relationship findings from other workflows. These source IDs can be returned by the API, but they are not additional choices in the eight-source Signal Agent configuration above.

> [card] Suggested Contact
>
> People recommended as relevant contacts at a matching company.
>
> > [accordion] Source & evidence
> >
> > * **Source:** Contact recommendations from a company or ideal customer profile (ICP) match.
> > * **Read the finding:** The company finding explains why the Account matters. The recommendation explains why this person is a relevant contact.
> > * **API types:**
> >   * `suggested_contact_signal`
> >   * `matched_company_icp_contact_signal`

> [card] Direct Access
>
> Existing contacts who provide direct access to a target Account.
>
> > [accordion] Source & evidence
> >
> > * **Source:** Saved relationship findings for a target Account.
> > * **Read the finding:** Review the saved explanation and source context to understand the contact's connection to the Account.
> > * **API type:** `relationship_signals.direct_access`

> [card] Introduction Paths
>
> Possible introduction paths through a connector to a target Account.
>
> > [accordion] Source & evidence
> >
> > * **Source:** Saved relationship findings describing a connector and target Account.
> > * **Read the finding:** A path describes a possible connection. It does not confirm that an introduction has been requested or accepted.
> > * **API type:** `relationship_signals.introduction_paths`

> [card] Person Engagement
>
> Saved interactions that provide relationship context for a person.
>
> > [accordion] Source & evidence
> >
> > * **Source:** Saved relationship findings about interactions involving a person.
> > * **Read the finding:** Review the explanation and available source links to understand the interaction and its relationship context.
> > * **API type:** `relationship_signals.person_engagement`

Older relationship findings may use underscore forms such as `relationship_signals_direct_access`. When filtering saved history, use the exact `type` returned for the finding. Older technology findings may similarly retain `technology_adoption_discovery`; their display name is Tech & Product Stack.

Legacy results may contain other source IDs even when they are no longer selectable in a new Signal Agent. In particular, `group_community_engagement_signal` is retained for older configuration and findings, but cannot be selected when configuring a new Signal Agent. The API preserves stored source IDs rather than relabeling them as another signal.

Imports and aggregate qualification decisions are not additional signal-history entries. Also, `signal_count` counts independently configured qualified sources, not the total number of retained findings; repeated findings from the same source configuration do not each add another source.

See [Accepted Filter Values](https://docs.plyne.ai/api/accepted-filter-values.md) for the filter reference, and [Pagination and Filters](https://docs.plyne.ai/api/pagination.md) for source scope, dates, and cursor behavior.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.