> ## Documentation Index > Fetch the complete documentation index at: https://docs.clearcue.ai/llms.txt > Use this file to discover all available pages before exploring further. # Signal Library > Every behaviour Clearcue can detect, how each one is sourced, and what you configure. Every signal starts with a **behaviour** — something a person or company does that tells you they're worth talking to. Pick one from the library, tell Clearcue what to watch, and choose how it's detected. ## How a signal is put together Each behaviour in the library offers one or more **sources** — different ways of catching the same behaviour. You can enable any combination. | Source | What it reads | | - | - | | **Social** | Posts, comments, and reactions on LinkedIn | | **Job board** | Live job listings from LinkedIn and major job boards | | **Database** | Clearcue's own database of career and employment records | | **Custom** | A post search plus an AI prompt you write yourself | Most behaviours can also be given **social research** and **web research**, which work through your tracked companies one by one instead of waiting for something to surface. What research adds to a signal, which behaviours support it, and how to configure it. You don't have to pick from the library. Describe the behaviour in your own words and Cue AI sets up the signal for you — it picks the behaviour, drafts the configuration, and shows it to you before anything is created. ## The library at a glance | Behaviour | Detects | Sources | Research | | - | - | - | - | | [Engaging with your brand](#engaging-with-your-brand) | People interacting with your own profiles | Social | — | | [Engaging with competitors](#engaging-with-competitors) | People interacting with a competitor | Social | — | | [Engaging with Top Voice or Brand](#engaging-with-top-voice-or-brand) | People interacting with an industry voice | Social | — | | [Hiring for a role](#hiring-for-a-role) | Companies hiring for a role you sell to | Social, Job board | Yes | | [Starting a new role](#starting-a-new-role) | People who just joined or were promoted | Social, Database | Yes | | [Announcing funding](#announcing-funding) | Companies raising a round | Social | Yes | | [Opening a new office](#opening-a-new-office) | Companies expanding to a location | Social | Yes | | [Attending an event](#attending-an-event) | People going to a conference | Social | — | | [Engaging with lead magnets](#engaging-with-lead-magnets) | People grabbing free resources | Social | — | | [Looking for an agency](#looking-for-an-agency) | People hiring an agency or freelancer | Social | Yes | | [Recommending a tool or service](#recommending-a-tool-or-service) | People endorsing a tool | Social | Yes | | [Making a first hire](#making-a-first-hire) | A company's first-ever hire in a market | Database | — | | [Hiring in a new location](#hiring-in-a-new-location) | Open roles where they have no staff | Database, Job board | — | | [Team growth or decline](#team-growth-or-decline) | A team growing or shrinking past a threshold | Database | — | | [Warm paths](#warm-paths) | Someone you know who can introduce you | Database | — | | [Keyword search](#keyword-search) | Posts matching your own query | Social | — | | [Custom AI signal](#custom-ai-signal) | Anything you can describe in a prompt | Custom | — | *** ## Engaging with your brand **Detects:** People warming up to your own brand and content. **Sources:** Social | Option | What it catches | | - | - | | **Engagers of your posts** | People who like or react to your posts | | **Comments on your posts** | People who leave a comment | | **Views your team's profiles** | People who viewed one of your profiles | | **Connects with your team** | New connection requests and accepted invites | **Configure:** Add your own profiles and company page. Enable the options you want. **Views your team's profiles** and **Connects with your team** need the LinkedIn login for that profile, because only its owner can see who viewed or connected. Clearcue walks you through connecting it after you save. You can also **import connections from a LinkedIn export**. Request your data from LinkedIn, then upload the `Connections.csv` file to the signal. It brings your existing network in one go, and you can upload a fresher export whenever you like. Importing is also the way to use this signal without connecting a LinkedIn login at all. Your network is then exactly as current as your last upload. **Example:** Add your CEO's profile and your company page, enable engagers and commenters, and you have a running list of people already aware of you. *** ## Engaging with competitors **Detects:** People interacting with your competitors' brands. **Sources:** Social | Option | What it catches | | - | - | | **Engagers of competitors' posts** | People who like or react to a competitor's posts | | **Comments on competitors' posts** | People who comment on them | **Configure:** Add competitor profiles or company pages. **Example:** Add three competitor pages. You get everyone engaging with them — people already interested in your category and actively comparing. *** ## Engaging with Top Voice or Brand **Detects:** People and companies interacting with a selected industry voice or brand. **Sources:** Social | Option | What it catches | | - | - | | **Engagers of a top voice's posts** | People who like or react to their posts | | **Comments on a top voice's posts** | People who comment on them | **Configure:** Add the profile or page of the voice you want to watch. **Example:** Track a well-known analyst in your category. Their audience is your audience, engaging in public. *** ## Hiring for a role **Detects:** Companies actively hiring for roles you sell to or sell through. **Sources:** Social, Job board · **Research:** social and web | Option | What it catches | | - | - | | **Hiring for a specific role** | Posts about hiring for the role | | **Posting jobs that match your criteria** | Live job listings matching your filters | **Configure:** The role or function you care about. ### Job board filters The job-board option matches real open roles rather than posts about hiring, with fine-grained control over who you catch. Every field is optional — fill in the ones that matter. | Filter | What it does | | - | - | | **Job title** | Match by keyword. Turn on **Advanced syntax** for boolean operators, phrases, proximity, and prefix wildcards. | | **Location** | Pick countries, or use advanced syntax for cities and regions. | | **Description keywords** | Boolean search over the job description — responsibilities and skills that aren't in the title. | | **Job type** | Full-time, part-time, contract, internship. | | **Remote** | Remote, on-site, or hybrid. | | **Agencies** | Include, exclude, or target recruitment agencies only. | | **Industry** | The hiring company's industry. | | **Seniority** | The level of the role. | ``` ("Head of Sales" OR "VP Sales") AND NOT junior ``` Full operator reference for the title field. Operators shared by every boolean field in Clearcue. **Example:** Title `"VP Sales" OR "Head of Sales"`, location United States, seniority Director/Executive, agencies excluded — US companies appointing senior sales leadership. Run both options together. The social one catches the excitement around a hire; the job board one catches every role that actually opened, including the quiet ones. *** ## Starting a new role **Detects:** People who have just joined a company or moved into a new role. New joiners have fresh discretion over tooling. **Sources:** Social, Database · **Research:** social and web | Option | What it catches | | - | - | | **Announcing a new hire or role** | Posts announcing the move — theirs, their company's, or congratulations | | **From the Clearcue database** | People whose profile shows they started a matching role, with no post required | **Configure:** The role or function to watch. The database option takes its own filters. ### Database filters | Filter | What it does | | - | - | | **Role title** | Boolean match against the title they started in. Use `AND`, `OR`, `NOT`; quote multi-word titles. | | **Started within** | Last 1, 3, or 6 months. 3 is recommended. | | **Company size** | One or more headcount bands, from `1` to `10,001+`. | | **Person location** | Countries the person is based in. | | **Company HQ location** | Countries their employer is headquartered in. | | **Industry** | Employer industries, picked from the known list so a mistyped name never silently matches nothing. | ``` "VP of Sales" OR "Head of Sales" OR "Chief Revenue Officer" ``` These two options answer the same question from different angles. The announcement only exists if the person chose to post; the database option doesn't depend on anyone posting at all. Run both. **Example:** Social option on "VP of Engineering", plus the database option with company size 201-500 — every new engineering leader at mid-market companies, whether or not they posted. *** ## Announcing funding **Detects:** Companies announcing a funding round at a stage you care about. **Sources:** Social · **Research:** social and web **Configure:** One or more round types — Angel, Pre-seed, Seed, Series A, Series B, Series C, Series D+. AI qualification filters for genuine announcements and drops investing advice, fund news, and general finance commentary. **Example:** Select Series A to reach companies about to scale their team and tooling. Add web research and you also catch the coverage that never appears on LinkedIn. *** ## Opening a new office **Detects:** Companies opening an office or expanding to a new location. **Sources:** Social · **Research:** social and web **Configure:** A city, region, or country. Announcements name cities, so a country is expanded into its main business hubs. AI qualification filters for real office openings and drops remote-work discussion and coworking promotion. **Example:** Enter "Germany" to track companies setting up locally — they need local vendors, partners, and services. *** ## Attending an event **Detects:** People going to, speaking at, sponsoring, or exhibiting at a specific event. **Sources:** Social There are two ways to track an event. Pick the one that matches what the event has — you don't need both. | Option | When to use it | | - | - | | **Attending or mentioning a conference** | The event has a LinkedIn page. Clearcue watches everyone posting about that page. | | **Posting about a conference (by keyword)** | The event has no page. Clearcue searches for the terms people use for it. | **Configure (page):** The event's LinkedIn page, plus the edition year, start and end dates, and hashtag. **Configure (keywords):** The event name and the terms posts use for it — the acronym with its edition year, the hashtag, the full name, the organiser's brand. You can also name the organiser, and flag anything else the name could be confused with. ``` "SDSS26" OR "#SDSS26" OR "Space Defense & Security Summit" ``` AI qualification narrows the results to real participation — attending, speaking, sponsoring, exhibiting, or inviting people to meet — and drops the organiser's own promotion, news recaps, and posts that merely name-drop the event. Speakers, sponsors, and exhibitors have committed budget to the event. They signal stronger intent than attendees, and Clearcue records which one each person is. **Example:** Track next year's edition of your industry's main conference a month out, and reach attendees before their calendar fills. *** ## Engaging with lead magnets **Detects:** People grabbing free resources — guides, templates, checklists — in exchange for a comment or a DM. **Sources:** Social Track lead magnets two ways: | Mode | What it watches | | - | - | | **By topic** | Any lead magnet in a niche, found by keyword search | | **By creator** | Lead magnets from one named creator | | Option | What it catches | | - | - | | **Engaging with a lead magnet** | Anyone reacting to the offer | | **Commenting on a lead magnet** | People who comment to request the resource | | **Commenting on a creator's lead magnet** | The same, scoped to your named creator | **Example:** Track "cold outreach" by topic. Everyone commenting to get the guide has told you what they're working on. *** ## Looking for an agency **Detects:** People looking to hire an agency, consultancy, or freelancer. **Sources:** Social · **Research:** social and web **Configure:** The service or discipline being sought. AI qualification keeps only posts where the author is the buyer, and rigorously drops agencies advertising themselves, recruiters, job listings, and listicles about choosing a provider. **Example:** Enter "web development" to find business owners actively looking — real buying intent, not browsing. *** ## Recommending a tool or service **Detects:** People recommending or endorsing a specific tool or service. **Sources:** Social · **Research:** social and web **Configure:** The tool or service name. **Example:** Enter a competitor's name to find people publicly endorsing them. Join the thread and introduce your alternative while the topic is live. *** ## Making a first hire **Detects:** A tracked company's first-ever hire in a country, in a department, or in both at once. **Sources:** Database A first hire is a company entering territory it has never been in. The first sales hire in the US, the first engineer in Germany — each one means a new budget owner and a new set of tools to buy. | Field | What it does | | - | - | | **What counts as a first** | **Any country** watches every market and names whichever country it turns out to be. **Specific criteria** lets you name the country, the department, or both. | | **Country** | The country the new hire is located in. | | **Department** | Picked from a fixed list of job functions — never free text, since a name that isn't on the list matches nothing at all. | | **Report hires from the last** | 3, 6, or 12 months. 6 is recommended. | Under **Specific criteria**, set a country, a department, or both. With neither, the signal would fire on every arrival at every company you track. Setting both is the strictest case. A "first German engineer" is a first that neither margin proves alone — the company may already have engineers elsewhere and Germans in other departments. "First" means first among the people working there **now**. A company whose only German salesperson left years ago counts a new German hire as its first — which is the point: nobody from Germany works there today, and someone just joined. **Example:** Specific criteria, country Germany, department Sales, 6-month window — your accounts putting their first salesperson on the ground in Germany. *** ## Hiring in a new location **Detects:** A tracked company with open roles in a country where it currently has no employees. **Sources:** Database, Job board This is a company entering a market it has no presence in — before any office announcement, and before the first hire lands. | Field | What it does | | - | - | | **Which markets** | **Any country** reports every country they're hiring in and have nobody in. **Specific countries** narrows to the markets you sell into. | | **Countries** | Always a country, never a city — the comparison is against where their people are, which is known at country level. | For market entry in general, use **Any country**. Which market they're entering is the answer, not the question — naming a list in advance means every market you didn't think of goes unreported. **Example:** Track 50 accounts with **Any country** and you get a card per gap: "3 open roles in Brazil, no employees there." *** ## Team growth or decline **Detects:** A tracked company whose headcount in a country, a department, or overall grew or shrank past a threshold you set. **Sources:** Database It measures who actually works there, so it reports the outcome of hiring rather than the intent. | Field | What it does | | - | - | | **Direction** | Growth or decline. One signal does one or the other. | | **Over the last** | 3, 6, or 12 months. | | **Countries** | Which countries to measure. Leave empty for every country. | | **Departments** | Which departments to measure, from the fixed job-function list. Leave empty for everyone. | | **Change in people** | At least — or at most — this many people, net. | | **Change in percent** | At least — or at most — this percentage, net. | | **Current team size** | Only report teams that currently have at least — or at most — this many people. | Set at least one minimum. With only maximums, a change of one person satisfies the signal. One signal measures one population. Naming several countries or departments **combines** them into a single number — Germany + France is one figure, not two. For per-country answers, create one signal per country. Percentage and people thresholds catch different companies. A 30% rule finds fast-growing startups and misses enterprises; a 500-people rule does the reverse. **Current team size — at least** is what stops a team going from 1 to 2 reading as 100% growth. **Example:** Growth, 6 months, department Sales, at least 30%, current team at least 10 — accounts scaling a real sales team. *** ## Warm paths **Detects:** Someone who currently works at a tracked company and shares real, dated history with a contact you already know. **Sources:** Database Shared history means the same employer or the same school, at overlapping times. Two people who were somewhere a decade apart never crossed paths, so they aren't a match. | Field | What it does | | - | - | | **Someone you know — LinkedIn profile URL** | The contact's own profile, not a company page. | One signal is one person. To surface warm paths through three contacts, create three signals — one per contact. Nothing else needs configuring. There's no prompt and no keyword: whether two careers overlapped is a matter of record. **Example:** Add your VP of Sales' profile. You get everyone at your tracked accounts who worked alongside them or studied with them — each one an introduction they can make personally. Matches are limited to people who work at a tracked company **today**. Someone who has since left offers no live introduction path. *** ## Keyword search **Detects:** Posts matching keywords or a boolean query you write. **Sources:** Social **Configure:** Your keywords, or a full boolean query. Optionally turn on the AI filter — Clearcue builds a relevance filter from your description so only genuinely relevant posts are captured. ``` "AI" OR "machine learning" ``` Operators, phrases, and grouping for every boolean field in Clearcue. **Example:** Track your category's vocabulary to find people discussing the problem you solve, before they've named a vendor. *** ## Custom AI signal **Detects:** Anything you can describe — a pattern none of the behaviours above covers. **Sources:** Custom Instead of choosing pre-built logic, you describe exactly what you want to find and AI evaluates every candidate against your criteria. **Configure:** Your prompt, plus who you want from the matching posts: | Option | Who you get | | - | - | | **Post creators** | The people who wrote the matching posts | | **Engagers of matching posts** | Everyone who liked or reacted | | **Commenters on matching posts** | Everyone who commented | ### Write an effective prompt Your prompt is a filter, not a search. It decides whether a piece of content counts. * **State what qualifies in one sentence.** "Qualify posts where the author says their team is struggling to hire developers." * **Name the hard disqualifiers.** Most of the work is exclusion. Rule out self-promotion, recruiters, job seekers, listicles, and secondhand commentary. * **Say who the subject is.** "When qualified, the subject is the post author" — or the company they name. * **Be concrete about edge cases.** If a balanced review shouldn't count, say so. The behaviours above come with prompts we've already tuned. Pick the closest one first — a custom prompt is for what's genuinely not in the library. ### Content vs signal qualification Two filters run at different moments: * **Content qualification** decides whether a post is relevant at all. * **Signal qualification** decides whether a specific person's engagement with it counts. Start with content qualification. Ruling a post out there means nobody who engaged with it reaches your records. A prompt only ever sees the post text. It cannot filter on company size, industry, seniority, or location — that information isn't in the post. Use [filters](/records/filters) and [audiences](/records/audiences) for those. *** ## Other ways to create a signal ### Describe it to Cue AI Type what you're looking for in your own words. Cue AI picks the behaviour, drafts the configuration, and shows you every proposed signal before anything is created. This is also how you reach behaviours and options that have no tile of their own. ### Lookalike signals Give Cue AI a few example posts you've found valuable and ask for more like them. It analyses what they have in common and generates the boolean query and AI prompt for you, which you can review and adjust before saving. Lookalike signals are created by asking Cue AI — there's no tile for them in the library. ### Outreach signals If you run outreach through HeyReach or Lemlist, their activity becomes signals automatically. These are powered by webhooks — they activate as soon as the integration is connected, with no profile or query to configure. | Integration | Signals | | - | - | | **HeyReach** | Message sent, InMail sent, first message reply, first InMail reply, any reply received | | **Lemlist** | Email sent, email replied, LinkedIn message sent, LinkedIn message replied | Outreach signals need an active [HeyReach](/integrations/heyreach) or Lemlist integration. *** ## Related Add research to a signal so it looks into your tracked companies directly. Pause, resume, edit sources, and understand signal limits. Combine behaviours so real intent separates itself from noise. How signals, audiences, and lists fit together. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.