CiviCRM Community Forums (archive)

I second xavier,

Activity for mailing should be more granular, (up to email opened, bounced, link clicked, etc)

I will also work on a mailing report that will allow bounced and other action performed through a mailing to be put into groups.

Down side I guess is that it will create more overhead in the db?


Chang

i think we need better archival systems for older mailings (and activities) in place BEFORE we even consider making activities of the various "mailing events".

There is already an issue of the mailing event tables in the DB growing to be quite large. This makes backups and migrations quite an issue (check the forums for some posts on this).

My point wasn't to create each click as a new activity too much activities indeed IMO.

My suggestion was to change the status of the existing mass mailing activity. Should cost an UPDATE status=clicked or opened, no INSERT involved (for click or read).

What goes big ? the tracking of each link ? The idea would be to archive and instead of keeping each link click stored, do the sum one, store it and delete all the individual records ?

bounces and replies are probably the two email that might be worth storing for "analysis" and improving things. However this can be made part of the event table for now.

I suggested using the activities because
1) the code exists already to create an activity from an incoming email
2) That's where the users want to see it IMO, you go to the activity, you see the mail sent and the reply/bounce

a different option might be to consider the "mailing events" as virtual activities

Sounds an interesting approach.

As for the activity status per component, made up your mind ?