Skip to end of metadata
Go to start of metadata

We are looking to implement a new field for CiviContibute pages that will allow a user to assign a source code to a contribution form. All contributions made through that page be assigned the source code.

So the process would go:

1) CiviCRM Admin creates contribution page

2) On the "Titles and Setings" page, a user will be presented with an optional "Course Code" field under Donation Type

3) User will fill in a alphanumberic string

4) Once contribution page is set to live

This is a pretty general approach to this I think could work. This allows us people to a) have a more granular way to filter contributions, b) opens up doors for better split testing of pages.

Comment from Alpha International:
Would be great to build this in such a way that source codes could also be added to a payment when an off-line contribution is added by admin staff. But that makes things a little more complicated, as you would really want a predefined list of source codes from which you select one as you add the gift. Otherwise you are liable to data entry errors. We would be looking to implement something like this at some point in the future - both for source codes but also for fund codes (where the money is allocated to)

The "contribution type" property is an existing approach for linking "fund codes" to a contribution page. When creating contribution types, you can enter an "accounting code" (which can be a fund code). Each online contribution page is linked to a contribution type (and hence the fund code) - which is included in contribution exports. This approach should work well for use cases where there's a 1:1 relationship between the contribution page and the fund code. Would be good to hear about use case where this approach breaks down. (Dave Greenberg)

Labels
  • None

Creative Commons License
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 United States Licence.