134
edits
Proposal For Mozilla Foundation Donor Data: Difference between revisions
Jump to navigation
Jump to search
Proposal For Mozilla Foundation Donor Data (view source)
Revision as of 19:24, 5 April 2010
, 5 April 2010no edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
=== '''Proposal for Capturing Financial Information for Mozilla Foundation''' === | === '''Proposal for Capturing Financial Information for Mozilla Foundation''' === | ||
'''Summary''': Mozilla Foundation amasses data about our donors, the causes they give to and how they match up against our fundraising and engagement targets. We need an effective framework for communicating progress against these targets. | '''Summary''': Mozilla Foundation amasses data about our donors, the causes they give to and how they match up against our fundraising and engagement targets. We need an effective framework for communicating progress against these targets. | ||
Mozilla Foundation will start to use CiviCRM within the next few months which will provide metrics for our donations, but the Foundation may benefit from a system implemented by | Mozilla Foundation will start to use CiviCRM within the next few months which will provide metrics for our donations, but the Foundation may benefit from a system implemented by a metrics team. Additionally, it may be helpful to do a comparison of the two methods of data collecting to see what CiviCRM finds and what is mined through the Metrics data since both use information from the PayPal feed/access. One proposal is to use the data retrieval API to query and thread information from the PayPal system by authenticating and retrieving account totals. | ||
'''Current Challenge of Process for Fundraising Data Pulling:''' | '''Current Challenge of Process for Fundraising Data Pulling:''' | ||
| Line 17: | Line 17: | ||
To present Mozilla Foundation's donation and financial reporting in an accurate and timely way in order to track fundraising progress for campaigns. | To present Mozilla Foundation's donation and financial reporting in an accurate and timely way in order to track fundraising progress for campaigns. | ||
'''Project Timeline:''' | '''Project Timeline:''' Four weeks, approximately. | ||
'''Teams/Individuals Involved:''' | '''Teams/Individuals Involved:''' | ||
| Line 27: | Line 27: | ||
==='''General Project Plan:'''=== | ==='''General Project Plan:'''=== | ||
'''Phase I (Week 1.1):''' Among Mozilla Foundation, team members discuss a strategy for automating data pulling. | '''Phase I (Week 1.1):''' Among Mozilla Foundation, team members discuss a strategy for automating data pulling; discussions have already begun with CiviCRM. Determine what type of standard reports we will receive with CiviCRM and then discuss what MoFo may need in addition to see if Metrics may help in gathering this information. | ||
'''Phase II (Week 1.2):''' Plan 2-3 meetings between the Foundation and Metrics team to determine what decisions need to be made for donations PayPal process | '''Phase II (Week 1.2):''' Plan 2-3 meetings between the Foundation and Metrics team to determine what decisions need to be made for donations PayPal process | ||
| Line 35: | Line 35: | ||
* For external use: Is our goal to present information to our donor and/or to encourage others to make the decision to donate more money along a path that we dictate (does this go against the idea of Choice for users)? i.e. are there areas that we feel donors should be encouraged to donate to in particular? | * For external use: Is our goal to present information to our donor and/or to encourage others to make the decision to donate more money along a path that we dictate (does this go against the idea of Choice for users)? i.e. are there areas that we feel donors should be encouraged to donate to in particular? | ||
'''Phase III (Week 2):''' Once process is determined, Metrics team would be able to use the data retrieval API to query for information from system, authenticate and retrieve account totals so there is no chance of data being misplaced. We would be able to retrieve information from the last thirty days for the web request. | '''Phase III (Week 2 and 3):''' Once process is determined, Metrics team would be able to use the data retrieval API to query for information from system, authenticate and retrieve account totals so there is no chance of data being misplaced. We would be able to retrieve information from the last thirty days for the web request. | ||
* By creating a script, the process would be completely automated on a regular schedule (i.e. weekly or monthly); if this is not possible, there would need to be a push process so we could retrieve the latest data. | * By creating a script, the process would be completely automated on a regular schedule (i.e. weekly or monthly); if this is not possible, there would need to be a push process so we could retrieve the latest data. | ||
* From PayPal, Metrics can | * From PayPal, Metrics can parse the spreadsheet into a CSV file | ||
* IT will have information on how much was donated, the time of day, which causes were donated to, where we get our donations. | * IT will have information on how much was donated, the time of day, which causes were donated to, where we get our donations. | ||
'''Phase IV (Week | '''Phase IV (Week 4): Using data''' | ||
* Metrics can extract this information so MoFo can have the data for email, newsletters or general dashboard on website. Having this information would make disseminating the information easier. | * Metrics can extract this information so MoFo can have the data for email, newsletters or general dashboard on website. Having this information would make disseminating the information easier. | ||
* Other options: use Flot to plot donation trend information privately (for the board) and give MoFo access to this for long term trending. | * Other options: use Flot to plot donation trend information privately (for the board) and give MoFo access to this for long term trending. | ||