TL;DR: If Signals is not showing expected results, first wait 48–72 hours after watchlist activation, confirm the watchlist is turned on, and remove restrictive filters. For website visitor signals, verify the tracker is installed on your production site and confirm browser network requests reach https://app.lemlist.com/api/visitors with status 200.
Symptoms
No signals appear after creating or activating a watchlist.
Signals shows the wrong companies or unexpected results.
Website visitor signals never appear.
Credits are consumed, but no new signals are visible.
LinkedIn signals seem delayed or incomplete.
Companies from a monitored list are missing from Signals.
Environment
Applies to Signals watchlists in lemlist.
Applies to website visitor, hiring, and LinkedIn signals.
Website visitor troubleshooting requires access to your production site and browser developer tools.
LinkedIn signal behavior depends on supported activity types only.
Step-by-step fix
Issue 1: No signals received
Check how long ago the watchlist was activated.
Wait 48–72 hours after activation before expecting signals to appear.
Open the watchlist and confirm the watchlist is toggled on.
Review the watchlist filters and remove restrictive conditions.
Temporarily broaden the filters to increase matches.
If the watchlist uses website visitor signals, verify the tracker is installed correctly on the production site.
If the watchlist monitors a company list, confirm the listed companies have valid domains.
✅ Verify: Signals start appearing after 48–72 hours, or new companies begin matching after filters are broadened.
Issue 2: Wrong or unexpected results
Review the active filters on the watchlist.
If irrelevant companies appear, narrow the filters.
Confirm the expected result type is a company, not an individual contact.
For LinkedIn watchlists, confirm you are only expecting personal profile activity and organic post engagement.
Do not expect company page engagement, paid ads, or sponsored content to appear in LinkedIn signals.
If the watchlist is restricted to a contact list, expect a lower detection rate.
✅ Verify: The companies shown in Signals better match the refined filters and supported signal sources.
Issue 3: Website tracker not working
Confirm the tracker is installed on the production website.
Do not test the tracker only on a staging or preview environment.
Open the website in a clean browser session.
Disable ad blockers and avoid privacy-focused browsers during the test.
Open browser developer tools.
Go to the Network tab.
Reload the production website.
Look for a
POSTrequest tohttps://app.lemlist.com/api/visitors.Confirm the request returns status
200.✅ Verify: The network request appears with status
200, and visitor-based signals begin showing after processing time.
Issue 4: Credits consumed but no signals
Check the watchlist type.
If the watchlist is a hiring watchlist, confirm expectations for credit usage.
For hiring watchlists, credits are charged per company monitored, not per hiring event detected.
If the watchlist shows insufficient credits, do not assume the watchlist is deactivated.
Top up credits if you want monitoring to continue automatically.
Deactivate the watchlist manually if you do not want it to resume after credits are added.
✅ Verify: Credit usage matches the number of monitored companies, and the watchlist status behaves as expected after credits are added.
Issue 5: Filters return zero signals
Review all active filters on the watchlist.
Check whether the watchlist combines too many conditions, such as geography, visit duration, and a specific URL.
Remove all filters temporarily.
Set website tracking to all pages.
Wait 48–72 hours.
If signals appear after removing filters, rebuild the filters gradually and test again.
If the watchlist monitors a company list, confirm missing companies are not missing domains.
Understand that companies without a domain are excluded from monitoring automatically.
✅ Verify: Signals appear with broad settings, then continue appearing as filters are reintroduced carefully.
Issue 6: LinkedIn signals are delayed or incomplete
Check when the watchlist was last refreshed.
Expect LinkedIn signals to refresh once per day, not in real time.
Confirm the watchlist is tracking supported LinkedIn activity only.
Supported LinkedIn activity includes personal profiles and organic engagement.
Unsupported LinkedIn activity includes company pages, paid ads, and sponsored content.
If the watchlist is limited to a contact list, expect a very low detection rate.
✅ Verify: Results update on the next daily refresh and only include supported LinkedIn activity types.
Confirm it's fixed
✓ Signals appear within 48–72 hours of watchlist activation.
✓ The watchlist is turned on and not blocked by restrictive filters.
✓ Website tracker tests show a
POSTrequest to/api/visitorswith status200.✓ LinkedIn signals match supported activity types and update on the daily refresh cycle.
✓ Credit usage matches watchlist behavior, especially for hiring watchlists.
Why it happens
Most Signals issues are caused by activation delay, restrictive filters, unsupported signal sources, or incorrect expectations about how tracking works. Prevent repeat issues by starting with broad filters, testing on production only, and confirming the expected behavior for website, hiring, and LinkedIn signals before narrowing the watchlist.
Alternatives
Use broader watchlist filters first, then narrow conditions after signals begin appearing.
Test website visitor tracking in a clean browser without extensions before changing tracker code.
Use rule-based exclusions instead of trying to exclude specific companies by name.
Expected behavior, not a bug
Signals shows companies, not individual contacts.
You cannot exclude specific companies by name.
Only rule-based exclusions are available, such as geography, pages visited, and time on site.
You cannot automatically add contacts to a campaign directly from Signals.
LinkedIn signals do not support company pages, paid ads, or sponsored content.
Companies without a domain are excluded from company-list monitoring automatically.
Escalate if unresolved
Share the watchlist type, activation time, current filters, watchlist status, and whether the watchlist is toggled on.
For website visitor issues, include the production URL, tracker installation method, a screenshot of the browser Network tab, and the request status for
https://app.lemlist.com/api/visitors.For LinkedIn issues, include the watchlist scope, whether it is restricted to a contact list, and examples of expected activity that did not appear.
For credit questions, include the watchlist type, current credit balance, and the exact watchlist status shown in the app.