View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018067 | phpList 3 application | General | public | 01-04-16 15:51 | 03-01-19 13:56 |
| Reporter | gingerling | ||||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | duplicate | ||
| Product Version | 3.2.5 | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0018067: Bounces per campaign list, with export | ||||
| Description | Page listing all the subscribers who bounced a campaign, accessed by links to bounce tally on stats overview page See attached document for more info. Would save a lot of time and faffing to have this asap. | ||||
| Tags | No tags attached. | ||||
|
|
bounces-per-campaign-idea.pdf (147,571 bytes) |
|
|
I think the client gets this emailed to them btw, something I did not realise at the time. It's still useful to have in the interface, but it's good to know the data does exist already. |
|
|
The Advanced Statistics plugin provides a listing of the bounces for a campaign, which can be exported. But I didn't understand the raw/tally/bounce count columns in the attachment. Are they being accumulated across several campaigns? |
|
|
In that Raw is all the domains of the emails that bounce Tally is each domain listed just once Count is how many times that domain appeared in the raw data So for example Raw school-a.com school-a.com school-c.com school-b.com school-b.com school-a.com Tally school-a.com school-b.com school-c.com Bounce count 3 2 1 The reason I have been looking at things in this way is we have a few users who mail schools or government departments etc. Their list makeup is really complex, many more domains than general marketing or newsletters. Also these domains also often have strict and complex blocking and/or poorly configured bounce reports often. Delivering to them, even with a really clean, opt-in list, is had. I have been using this method to try and examine which domains to deal with first. For example, in this case I would prioritise school-a first. This can be done on a whole-install basic more easily, but a list-by-list or send-by-send approach allows me to target the most important domains and ignore historical data. |
