Account Monitoring
Monitor specific companies for business events and changes
Set up monitoring for specific companies in your sheets to track funding rounds, leadership changes, product launches, and other significant events. Unlike topic monitoring, account monitoring watches entities you've already discovered.
Prerequisites
Before starting, ensure you have:
- Completed the Topic Monitoring guide
- A sheet with existing entities to monitor (from search or CSV import)
- Your API key (see Authentication)
Understanding Account vs Topic Monitoring
Account monitoring (signal-sheet) watches entities from an existing sheet, while topic monitoring (signal-topic) discovers signals based on search criteria. Use account monitoring when you have a defined list of companies to track—your target accounts, customers, competitors, or prospects already in Linkt.
ICP Modes
Both monitoring types require an ICP with mode: "monitoring". See ICPs for mode details.
Step 1: Identify Your Source ICP
Account monitoring requires a source ICP with existing entities. This is typically a discovery ICP from a previous search or CSV import.
Response:
Note the id of the ICP containing entities you want to monitor.
Step 2: Create a Monitoring ICP
Create a separate ICP in monitoring mode for signal detection:
Response:
Step 3: Configure the Signal Task
Create a signal task with the signal-sheet configuration. This references your source ICP:
SignalSheetConfig Fields
| Field | Required | Description |
|---|---|---|
type | Yes | Config discriminator (must be signal-sheet) |
source_icp_id | Yes | ID of the ICP containing entities to monitor |
entity_type | No | Entity type to monitor (default: company) |
signal_types | Yes | Array of signal types to detect |
monitoring_frequency | No | daily, weekly (default), or monthly |
entity_filters | No | MongoDB query to filter entities |
webhook_url | No | HTTPS URL to receive completion notifications (see Webhooks) |
Step 4: Filter Specific Entities
Use entity_filters to monitor a subset of entities:
Filter by Industry
Filter by Employee Count
Filter by Multiple Criteria
MongoDB Query Syntax
Entity filters use MongoDB query syntax. Common operators include $eq, $ne, $gt, $gte, $lt, $lte, $in, $and, $or, and $regex.
Step 5: Execute Monitoring
Execute the task to start signal detection:
Response:
Step 6: Retrieve Account Signals
Once monitoring completes, retrieve signals with entity correlation:
Response:
Entity IDs Populated
With account monitoring, entity_ids contains the IDs of the monitored entities, allowing direct correlation between signals and accounts.
Signal-Entity Correlation
Account monitoring signals include entity_ids linking directly to your entities.
Correlating Signals to Accounts
Output Example
Building Account Intelligence
Aggregate signals per account to build comprehensive intelligence views.
Account Intelligence Dashboard
Signal Priority Scoring
Scheduled Monitoring
Set up recurring monitoring with appropriate frequency:
Monitoring Frequency Options
| Frequency | Use Case | Typical Accounts |
|---|---|---|
daily | High-priority targets, active deals | 10-50 |
weekly | General target accounts | 50-500 |
monthly | Extended watchlist | 500+ |
Example: Daily High-Priority Monitoring
Complete Example
Full workflow for setting up account monitoring:
Next Steps
- Topic Monitoring — Monitor by topic instead of accounts
- Webhooks — Receive HTTP notifications when workflows complete
- Signal Types Reference — Understanding all signal types
- Signals Reference — Signal data structure