Organizing Transactions into a Three-Level Hierarchy

While thinking about how you intend to set up your Kindful account, you may consider how you have historically tracked your donations. Kindful manages your transactions by default in a hierarchy of campaigns and funds (two levels). You may have tracked, or want to track, an additional layer within your donations. Whether you are configuring your Kindful account or preparing your data for a "Custom Services Import," this article provides information about the best practices for organizing your transactional data into three levels/tiers. 
 
Note: There is a limit of three custom fields on a campaign. This applies to a transaction as well, since every transaction is required to have a campaign. 
 

Organizing Transactions

You have three options for handling level 1, level 2, and level 3:
 

1) Fund - Campaign - Sub-campaign

2) Fund - Campaign - Custom Field

3) Fund - Campaign - Cause

You should review this opinion along with your knowledge of your source data, what you've learned while experimenting in the sandbox, and watching videos in order to make an informed decision.
 

1) Fund - Campaign - Sub-campaign

What it means:
 
In this case, every transaction is tied to either a campaign or a sub-campaign. Sub-campaigns are merely grouped underneath (parent) campaigns in the Admin UI so that you can find them more easily. 
There is no automated "roll up" in reporting. However, it is easy to manually construct "or" queries to report on all of the sub-campaigns of a parent campaign. 
 
The main benefit here is that you can free up a custom field for other uses.
The main downside relates to the importing process. There is no way to specify the hierarchy of campaign and sub-campaigns in the import process. All campaigns are imported on the same level. 
 
After the import process is complete, you can reorder/organize your campaigns in the Kindful admin. You can then view all of your campaigns as a tree. This can be accomplished via a Sandbox trial. 
 
For more information about organizing Campaigns into a hierarchy, please see this article.

2) Fund - Campaign - Custom Field

What it means:
 
There is a custom field stored on the campaign for the third level. You can filter by the campaign (level 2) or by the campaign's custom fields (level 3). Filtering by campaign returns everything at level 2. Filtering by the custom field returns everything at level 3. 
 
The main benefit is that you get granular and roll-up reporting easily.
The main downside is it that would take up a campaign custom field (you are limited to three).
 

3) Fund - Campaign - Cause

What it means:
 
The third level of your historical data is all applied to a cause. Causes require a team. This solution is the most cumbersome because it does not fit the intended use of the cause module. You would get the reporting capability similar to option 2. However, this solution is not recommended. 
The main benefit is the ability to use a Custom Field in another way. 
 
The main downsides include needing to add teams to each cause and using the cause module in a way it ultimately wasn't designed to operate. 
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments