134
edits
Proposal For Mozilla Foundation Donor Data: Difference between revisions
Proposal For Mozilla Foundation Donor Data (view source)
Revision as of 00:22, 6 April 2010
, 6 April 2010→Proposal for Capturing Financial Information for Mozilla Foundation
| (27 intermediate revisions by the same user not shown) | |||
| 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 | '''Summary''': Mozilla Foundation amasses data about our donors, the causes they give to and how the donations match up against our fundraising and engagement targets. We need an effective framework for communicating progress against these targets. | ||
In two-three months, the team aims to use CiviCRM, an open source relationship management tool for nonprofits; it helps track online fundraising and features a donor management component to track and manage contributions to the organization. | |||
In addition, the Foundation could benefit from a system implemented by the MoCo Metrics team. The following is a proposal for an additional method to track and gauge donor data; this would work by using the data retrieval API to query and thread information from the PayPal system by authenticating and retrieving account totals. It may be helpful for doing a comparison of the two data collection methods (CiviCRM and Metrics' data) since both would use information from the PayPal feed. | |||
'''Current Challenge of Process for Fundraising Data Pulling:''' | '''Current Challenge of Process for Fundraising Data Pulling:''' | ||
* PayPal monthly reports are tedious to mine | * PayPal monthly reports are tedious to mine | ||
* | * It is challenging to view the progress of the campaign | ||
* Data analysis is infrequent and time consuming since information needs to be analyzed and recorded to know how many specific projects receive donations | * Data analysis is infrequent and time consuming since information needs to be analyzed and recorded to know how many specific projects receive donations | ||
* MoFo needs to report this data monthly | * MoFo needs to report this data monthly | ||
| Line 15: | Line 19: | ||
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 and Interviewed:''' | ||
* Mozilla Foundation | * Mozilla Foundation | ||
* Metrics (Metrics Architect), Analytics, Business Intelligence | * Metrics (Metrics Architect), Analytics, Business Intelligence | ||
| Line 25: | Line 29: | ||
==='''General Project Plan:'''=== | ==='''General Project Plan:'''=== | ||
'''Phase I (Week 1.1):''' Mozilla Foundation members discuss | '''Phase I (Week 1.1):''' Among Mozilla Foundation, team members discuss a strategy for automating data pulling. Determine what type of standard reports we will receive with CiviCRM and then discuss what MoFo may also need to determine if Metrics helps 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):''' If MoFo is interested in working with Metrics: | ||
* Plan 2-3 meetings between the Foundation and Metrics team to determine what decisions need to be made for donations PayPal process | |||
* Discussion points for meeting: determine what questions have to be answered | * Discussion points for meeting: determine what questions have to be answered | ||
* Do we direct our focus to manipulate these funds? | * Do we direct our focus to manipulate these funds? | ||
| Line 33: | Line 38: | ||
* 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 | * 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) 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. | ||
* Work with WebDev | * Work with WebDev to determine what donation information will be open to the public for website. | ||
==='''Benefits for MoFo, MoCo and Community:'''=== | ==='''Benefits for MoFo, MoCo and Community:'''=== | ||
| Line 50: | Line 55: | ||
'''Weaknesses/Threats:''' | '''Weaknesses/Threats:''' | ||
* Accessing PayPal may be challenging to work with if we use an API because of password access | * Accessing PayPal may be challenging to work with if we use an API because of password access | ||
* There is nothing new to this method of data collecting that could be done easily with CiviCRM | |||
* MoFo may not be able to to share financial information when working with teams outside of the Foundation | * MoFo may not be able to to share financial information when working with teams outside of the Foundation | ||
* May be challenging to scrape the data | * May be challenging to scrape the data | ||
| Line 57: | Line 63: | ||
'''Strengths/Opportunities:''' | '''Strengths/Opportunities:''' | ||
* Quicker mining of data | * Quicker mining of data | ||
* Less reliance on an additional and external metrics program | |||
* More accurate results | * More accurate results | ||
* Builds a pipeline for metrics and reporting at Mozilla | * Builds a pipeline for metrics and reporting at Mozilla | ||
| Line 64: | Line 71: | ||
* Encourages methods to report financial information to Mozilla, internally and externally | * Encourages methods to report financial information to Mozilla, internally and externally | ||
* Develops accountability and transparency for our reporting (i.e. on website, newsletters, etc.) | * Develops accountability and transparency for our reporting (i.e. on website, newsletters, etc.) | ||
* Creates processes for the Foundation | * Creates processes for the Foundation | ||
* Once the data is produced, there may be the opportunity to have a visual reference of donation progress on Mozilla's homepage | * Once the data is produced, there may be the opportunity to have a visual reference of donation progress on Mozilla's homepage | ||
* Mozilla currently does not have a lot of data that is being made directly available to the public at the moment--having an efficient data pulling system builds a paper trail and | * Mozilla currently does not have a lot of data that is being made directly available to the public at the moment--having an efficient data pulling system builds a paper trail and makes a streamlined system for record-keeping | ||
==='''General Ideas/Thoughts for Project:'''=== | ==='''General Ideas/Thoughts for Project:'''=== | ||