Simplenews statistics
djmystic82 - July 30, 2007 - 09:28
| Project: | Simplenews |
| Version: | 5.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | scor |
| Status: | won't fix |
Jump to:
Description
Is it possible to view statists for newsletters that have been sent out?
ie: how many emails were succesfully sent, how many emails have been viewed etc.

#1
I'm interested too, it should be very good. I think it's a feature request, not a support request...
#2
I've already implemented something like that, but I'll have to improve it and send a patch. The problem I have now is that the statistics are only for the last newsletter you sent, and you have to reset the statistics counters when you want to send a new newsletter. ideally each newsletter issue you send should have its own set of counters.
#3
I'm interested with your patch, it can give the way to make a module to manage that.
#4
I'll second (third) this. This is something that would make simplenews an even better module!
#5
I'd welcome this feature. I'd also suggest adding some basic stats to the lists, for example, current number of subscribers.
A little off topic, but logging (which would allow stats such as number of messages sent) would be a big improvement. On shared servers with little access to logs, there is little way to know what has been sent and the progress of a send. A log file, even a simple txt dump to a file would be a big improvement!
#6
the two features requested in the initial post are very different, though, right?
"how many emails were succesfully sent" -- yes, i'd love to see this. i assumed simplenews logged e.g. how many messages were sent (initially, and with each cron run), but it seems that's not so. i have no idea how much work that'd be to implement, but it'd be hugely valuable to have some way to gauge the progress of large mailings.
"how many emails have been viewed etc." -- in my understanding, these kind of stats would require a response back from the client, meaning HTML email, privacy concerns, and a whole other can of worms. personally, i'm happy to send plain text emails and forgo that type of functionality.
thank you, developers, for all your work on Simplenews!
#7
What happened to the ability to see the number of subscribers on a newsletter?
In previous versions, when viewing subscriptions, there was a number next to each subscriber. You could then select the last page to see how many subscribers you had to that newsletter at a glance.
That is now missing in the 5.0 version. Is there a reason?
#8
I'm using Simplenews in a production site and I consider vital these stadistics.
In reality will be very usesful to control if all subscribed users have received the e-mail.
In addition could be very usesful to have in the list of sent simple news the number of user subscribed when the simple news is sent and the number of users to which the e-mail has been sent or even better received without problem.
In addition could be very usesful to be able to resend the e-mail to failed users.
#9
Although received statistics are a difficult coding job, it would be only a line or two of code to put a figure for how many emails have been sent to a list. The only indication at the moment is that the newsletter is still being sent. Instead, it would be far better to see something like "Newsletter still sending: 544 sent of 3526 subscribers".
#10
I think that it is a very good imporvement.
#11
subscribing
#12
subscribing
#13
This function will not be implemented in 5.x. It requires a significant change of the code to get this realized.
6.x-1.x-dev now has a spool mechanism which enables future implementation for statistics.
If anyone is interested to chip-in for getting this into simplenews please let me know.
#14
subscribing
#15
Even basic statistics would be hugely useful, like how many subscribers in a list and a little more info about how many newsletters were sent out for a particular newsletter.
I think there would be a lot of ppl who would like this feature for 5.
#16
Anyone interested to pool op to fund this feature?
This is also a nice way of supporting the module maintainer!!
More info:
http://drupal.org/node/316604