What you track
For each entity you add (a person’s profile or a company page URL), you choose independently — add and manage tracked entities from the trigger’s Configuration tab, using Add Another Profile for each new one:- Whether to track new posts from that entity.
- Whether to track comments on those posts.
- Whether to track reactions (likes and other reactions) on those posts.
Polling
Swan checks tracked entities for new posts every hour. For any post published in the last 5 days, it also checks for new comments every hour. Reaction counts are captured once, shortly before a post ages out of that 5-day tracking window, rather than every hour — reactions tend to level off, so one snapshot near the end of the window is enough. There’s no notification sent when a polling cycle finds nothing new — this is an event-driven trigger, it only fires when there’s something to act on. Fetching posts and engagement primarily uses public LinkedIn data. If that isn’t available for a particular profile, Swan falls back to pulling it through your organization’s connected LinkedIn sender accounts, rotating across whichever account was used least recently so the load is spread out rather than hitting the same account repeatedly.Caps and filters
For the trigger, you can set:- Max comments / max reactions to pull per post — defaults to 1,000 comments and 200 reactions if you don’t set a lower cap.
- Headline include or exclude keywords — only engagers whose LinkedIn headline contains (or doesn’t contain) specific keywords count as a match. It’s one or the other: the trigger can filter by an include list or an exclude list, not both at once. This applies to commenters and reactors, not to the tracked entity itself.
- A topic filter — for posts, Swan can check whether a post’s content is actually relevant to a topic you describe, and skip it if it isn’t.