View Issue Details

IDProjectCategoryView StatusLast Update
0000603Composrnewsletterpublic2020-03-28 01:03
ReporterChris GrahamAssigned To 
Severityfeature 
Status non-assignedResolutionopen 
Product Version 
Fixed in Version 
Summary0000603: Newsletter tracking, include tracking code integration
DescriptionCreate new table, newsletter_receipt_tracking:
 AUTO id // Randomised tracking ID, so cannot be easily guessed
 AUTO_LINK t_archive_id // This is the ID into the newsletter_archive table (which stores the text for a send)
 EMAIL t_email_address
 SHORT_TEXT t_forename
 SHORT_TEXT t_surname
 SHORT_TEXT t_secure_identifier
 TIME t_has_read
 TIME t_has_clicked


NEWSLETTER LINK CLICKING TRACKING...

This table is designed to record who has read a particular newsletter. Each recipient is given a row in this table.

Automatically include the unique recipient tracking ID as a tracking parameter into all website URLs included in a newsletter. It would use the standardised '_t' tracking code system. However, it would be codified in such a way that the actual recorded tracking code will be based on the newsletter archive ID not the ID passed (as otherwise we'd have thousands of unique tracking codes in the system). For example, maybe we make a convention that a tracking code that looks like nr<number> is a newsletter recipient ID and processed as just described. Such codes would also cause the newsletter_receipt_tracking:has_clicked field to be updated too.


NEWSLETTER READ TRACKING...

New script to do read-tracking via embedded images, updating the newsletter_receipt_tracking:has_read field when it is hit. Automatically include this in the default template.

New admin interface for showing the newsletter_receipt_tracking table against the archive of what was sent - gives general stats, and a CSV download link.

Option to download aggregated CSV against all sendings, so you can see how many mails each recipient read.


IMPROVED BOUNCE HANDLING...

In addition to click and read tracking, one might also want to track bounces.
Composr already has support for removing bounced addresses from newsletters. Allow this to also remove email addresses from member accounts. This will reduce the chance of spam blocks.
Allow bounce handling to run in a Cron hook.

Document the importance of newsletter cleansing:
1) We need to regularly delete subscribers who are stale, to avoid getting flagged as a spammer
2) We need to regularly delete subscribers who are stale, to reduce the cost/time for sending future newsletters
3) We want to be able to have focused lists of the most active readers
TagsRoadmap: v12, Type: Avoiding e-mail spamblocks
Attach Tags
Time estimation (hours)16
Sponsorship open

Relationships

related to 0003437 non-assigned Newsletter events log 
related to 0002142 non-assigned Improved subscriber management 
related to 0002259 resolvedChris Graham New stats/KPI system 
related to 0001563 non-assigned Change bounce reporting to automated tool 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2017-03-23 16:20 Chris Graham Relationship added related to 0002259
2017-06-09 20:22 Chris Graham Category newsletter => core
2017-06-09 20:22 Chris Graham Summary Tracking => Improved tracking system
2017-06-09 20:22 Chris Graham Description Updated View Revisions
2017-06-09 20:22 Chris Graham Additional Information Updated View Revisions
2017-06-09 20:22 Chris Graham Category core => stats
2017-06-09 20:23 Chris Graham Summary Improved tracking system => Improved tracking system (including newsletter integration)
2017-06-09 20:25 Chris Graham Description Updated View Revisions
2017-11-28 00:05 Chris Graham Relationship added related to 0003437
2017-11-28 00:12 Chris Graham Relationship deleted related to 0001563
2017-11-28 00:19 Chris Graham Tag Attached: Type: Avoiding e-mail spamblocks
2017-11-28 00:23 Chris Graham Relationship added related to 0001563
2017-11-28 00:24 Chris Graham Relationship added related to 0002142
2019-06-27 18:08 Chris Graham Tag Attached: Roadmap: v11
2020-01-18 03:41 Chris Graham Category stats => newsletter
2020-01-18 03:41 Chris Graham Summary Improved tracking system (including newsletter integration) => Newsletter tracking, include tracking code integration
2020-01-18 03:41 Chris Graham Description Updated View Revisions
2020-01-18 03:41 Chris Graham Tag Detached: Roadmap: v11
2020-01-18 03:46 Chris Graham Description Updated View Revisions
2020-03-28 01:03 Chris Graham Tag Attached: Roadmap: v12