Launching an announcement or nudge is only half the job. The other half is knowing whether it worked. FeaturePin tracks the three events that matter for every campaign — impression, click, dismiss — and presents them in a dashboard designed for product decisions, not data engineering. No SQL, no event schemas to define, no analytics setup beyond the SDK you already installed.
The three events that matter
FeaturePin tracks three events per campaign. That is a deliberate constraint, not a limitation. More events create more noise. Three events create three clear questions: did the user see it, did the user act on it, and did the user close it without acting?
01 Impression
The campaign was rendered and visible to the user. Logged once per user per campaign — repeat views do not inflate the count.
02 Click
The user clicked the primary CTA button. For nudges, this is the key conversion signal: the user is going to try the feature.
03 Dismiss
The user closed the message without clicking the CTA. Useful for understanding awareness without conversion, and for diagnosing copy or targeting problems.
The ratio between these three events tells you most of what you need to know. High impressions with low clicks suggests a copy or relevance problem. High dismissals relative to clicks suggests the message is being seen by users who are not ready to act. If impressions are much lower than expected, the targeting condition may be too narrow or the campaign may not be reaching your most active users.
The analytics dashboard
The analytics view in FeaturePin shows impression volume over time, click-through rate, and dismiss rate for each campaign. You can filter by date range — 7, 30, or 90 days — and toggle between the overall summary and a daily breakdown chart.
The dashboard is designed for product decisions. You should be able to open it, see whether a campaign is performing, and decide in under a minute whether to keep it active, adjust the copy, or pause it. There is no setup required — analytics are on by default for every campaign from the moment it goes live.
What good numbers look like
Benchmarks vary by format and context, but these ranges are representative of healthy campaigns in typical SaaS products.
01 Modal impressions
70 to 90 percent of active users within the first week for a well-targeted campaign on a major release.
02 Banner impressions
60 to 80 percent of active users, depending on how often they log in during the campaign window.
03 Tooltip nudge CTR
15 to 35 percent for a well-targeted, contextually placed nudge. If you are below 10 percent, review targeting first.
04 Modal CTR
20 to 40 percent for an actionable CTA on a relevant launch. Lower for informational-only announcements.
These are diagnostic ranges, not targets. If your numbers fall well below them, it usually points to a targeting problem — the message is shown to users for whom it is not relevant — or a copy problem — the message does not communicate a clear reason to act. If your numbers are above the top of the range, you have a well-matched message and audience.
How to improve campaign performance
Analytics are useful only if they inform a next action. Here are the most common improvement levers.
- Narrow the audience. The more specific the targeting, the higher the click-through rate. If you are targeting all users, try narrowing to users who have visited the relevant section at least once in the last 30 days.
- Move the format. A tooltip fires in the right context. A modal fires on login. If the feature is specific to a section, a tooltip in that section will outperform a modal on the dashboard.
- Shorten the copy. If users are dismissing quickly, they are probably not reading the body. Cut the message to two sentences and test whether CTR improves.
- Check the CTA label. Specific labels outperform generic ones. 'Try the export feature' converts better than 'Learn more'.
- Review the inactivity window for nudges. A 14-day window may include users who are just infrequent. Try 21 or 30 days for features users only need occasionally.
Workspace-level analytics
Beyond individual campaign analytics, FeaturePin shows a workspace summary: total MAU for the current 30-day window, impression volume across all active campaigns, and the top five campaigns by impression count. This gives you a quick read on overall product communication health without opening each campaign individually.
The MAU counter is also the billing metric. It updates daily and reflects the rolling 30-day count of unique users your SDK identified. You can see the current count, the plan limit, and how many days are left in the current window from the Settings section. Limits come with a seven-day grace period before the account is locked.
Two features, one adoption job.
Announce releases inside your product. Nudge users who did not act. That is the whole system, and for small SaaS teams it is usually enough.