Every comment and reaction on an advocacy post happens with no record of who did it. Signals tells you exactly who engaged, with what post, and when, across your whole organization.
Employee advocacy intelligence: stop guessing who’s engaging with your content
DSMN8 Signals shows you every person who reacts to or comments on the LinkedIn posts your employees share, matched to the contact record you already own in CRMs like HubSpot or Salesforce.
Your advocacy posts already have an audience. Signals shows you exactly who’s in it.
Most employee advocacy reporting stops at social metrics. Get intelligence with DSMN8 Signals.
Employees share content, people react and comment, and that disappears into their LinkedIn notifications. A lead could be highly engaged but invisible to you, because web analytics only sees who clicked a link. Signals sees reactions and comments, matched to your CRM contact records. That's real employee advocacy intelligence and attribution.
Why it matters
Turn advocacy into a credible budget line
Employee advocacy programs get cut first when budgets tighten, because reach, impressions, and EMV don’t tie to pipeline. Signals ties that engagement to CRM activity on real contact records. Use it to show pipeline impact, or to show the right people are paying attention to your firm’s thinking.
Give sales a reason to care about advocacy
Sales reps are already your most active advocates, but the engagement their own posts generate never reaches their workflow. Signals logs it straight to the HubSpot or Salesforce record a rep already works from.
Feed marketing ops without extra tooling
Engagement lands on the contact record as a native HubSpot or Salesforce event, ready to plug into lead scoring (with separate point values for reactions and comments), retargeting segments, or workflow alerts to the contact owner, with no manual pulls from yet another platform.
See who's supporting each other internally, too
Because Signals captures internal engagement as well as external, program leaders can filter to see which colleagues are actively supporting each other’s posts, a quick way to spot your most engaged internal advocates.
How Signals Works
1: Employees share, people engage. Employees share company posts through DSMN8 as normal. Other people react to or comment on those posts on LinkedIn.
2: Signals lists everyone who engaged. Across your whole organization, filterable and sortable, searchable by company. Click a person to see exactly which posts they engaged with.
3: Connect a CRM to log it automatically. When HubSpot or Salesforce is connected (in Settings > Connectors), Signals matches engagers to contact records that already exist there and sends a custom event, only for contacts that already exist there.
4: Uncertain matches wait for a person. Where the match isn’t an exact LinkedIn URL hit, it sits in the Review queue until someone confirms or hides it.
Everything Signals Gives You
Audience
Every person who's engaged with your advocacy content, company-wide. Filter and sort by company, date, or CRM match status; search by company name.
Team
The other side of the same data: which employee posts are gaining that engagement, so program leaders can see which employees are earning that engagement.
Review queue
Where the CRM matcher can't confidently place an engager, it waits here instead of guessing, until someone confirms or hides it.
Connectors (Settings)
Connect HubSpot or Salesforce and choose how engagement is logged. Signals only matches to contacts that already exist in your CRM. It never creates new records.
Access
Company administrators always have Signals. Anyone else is granted access from their user record, with Review queue access granted as a separate permission.
Built to respect LinkedIn's terms
Resolved profile details live in a 24-hour cache and are never written to a database, a log, or your CRM. Signals surfaces the engagement, not a stored identity.
See exactly who your employee advocacy posts reached, and find out they're already in your CRM.
Frequently Asked Questions
What is Signals?
Signals shows you who’s engaging with your employee advocacy content on LinkedIn: reactions and comments on posts your employees share. When a CRM is connected, it logs that engagement against the contact record you already own.
Why do some rows just say “LinkedIn Member” instead of a name?
Signals resolves profile details through a 24-hour cache and never writes them to a database, a log, or your CRM, per LinkedIn’s terms. If a profile can’t be resolved in that window, the row shows “LinkedIn Member” rather than a stored name.
Does Signals create new contacts in my CRM?
No. Signals only logs engagement against contacts that already exist in HubSpot or Salesforce. It never creates a new record.
Why doesn't an engager's name show up in the CRM activity log?
Same reason as above: Signals doesn’t store or pass through identity data. The activity confirms that an engagement happened and logs it to the right contact; it doesn’t write the person’s name into your CRM.
What happens to engagements the matcher isn't sure about?
They sit in the Review queue until someone with Review queue access confirms or hides them. Once decided, that holds for the same person’s future engagements, with no repeat reviewing.
Can I give Signals to specific people without making them admins?
Yes. Company administrators always have access; anyone else is granted it from their user record in user management, with Review queue access granted as a separate permission.
Which CRMs does Signals connect to?
HubSpot and Salesforce, configured in Settings > Connectors.
Are colleagues included in the engagement count?
Yes. Signals captures all engagement, including your own team’s, and you can filter by internal versus external. That also makes it a quick way to see which colleagues are already supporting each other’s posts.