I got asked a couple of times now how to use FeedLetter - is it one form per email or one form per newsletter.
The intended use was one form per email you send out. So, if you write twice a week, you create 2 forms a week, for each email one.
Why? Because you get feedback on the individual emails and learn which topics work and which not. Also, the extended feedback is more specific. The UI is designed for that with the least clicks possible :-)
However, I know a couple of customers use it differently with only one form per newsletter. They still get their insights from votes and extended feedback.
I focus development on the intended use but will not force you to use it. If the other way works for you, go with it. I'll even support that way as much as possible without breaking the experience. Why? Because it's about you and I want you to get the most out of FeedLetter.
It's tempting to know who downvoted or dislikes your emails but know it might not help you at all. If people don't tell you via an anonymous form, something they feel safe, they won't tell you when you email them.
FeedLetter is driven by privacy, and I do not track your or my readers. And readers love that. They can tell you and me anonymously what they liked or disliked and why. And some of them even tell you who they are by filling out the optional name field on the extended feedback page.
Some even go so far and give you their email address in the comment field. So, if they really want to tell you who they are, they will do it. Either via FeedLetter or simply by sending you an email.
You could try to track them via your email provider's analytics, but that has some flaws as those analytics cannot track everyone. And no, they don't send along with an external link who clicked on it. So, FeedLetter has no way to know which user it was.
Anyway, I encourage you to experiment with the wording to get them to tell you their reasons. It's all about trust, feeling safe, and genuinely being heard.
You can customize all reader facing text.
There are a few reasons how those discrepancies happen.
It starts already at the newsletter provider level there because the tracking on the newsletter providers' level is already flawed aka not perfect. There're certain conditions, of course, with differences from provider to provider, because of the way those clicks are counted.
Also, they don't differentiate between actual clicks by the user or by an in-between system. I learned that in the early stages of FeedLetter with my mail providers mailerLite & mailchimp, for example, some users always had click records in mailerLite for ALL my voting links. Turned out some server checked all links before delivering the email to the user's inbox. Or with Mailchimp, where an automated process opened the links and caused votes in FeedLetter even the user hadn't triggered anything yet.
Then there’re other situations where differences can come from:
As a constant counter measure, I block for example all known IP ranges of AWS, Google Cloud or Azure and now certain Office 365 Outlook servers. Those are all votes from other SaaS & tools but never from a user.
However, I’ve never seen the ESP to block them in click tracking so they still count there. Only there own tools are removed from their click counting. No other systems.
The Ip blocking bot detection was introduced around July 2022 and I updated it twice recently with the major change of adding Office 365 Outlook "protection" servers.