Dataro Integration for Salesforce
Last updated: September 22, 2026
Overview
Dataro is a technology company that provides state-of-the-art propensity scores for not-for-profit organisations. These propensity scores can be used to simplify list selections for future fundraising campaigns, identify donors at risk of canceling their recurring gifts, and other common fundraising goals. An integration between Dataro and our client’s CRM provides the simplest way for clients to take advantage of Dataro’s propensity scoring technology without the need to manually move data between one system and another.
The following documentation outlines the steps involved in an integration between Dataro and a Salesforce environment.
Dataro Integration Steps (Salesforce)
In order to integrate with Dataro, we simply require our clients to install our ‘connected app’ to allow us to communicate with the environment via the Salesforce APIs (REST, Bulk & Metadata APIs).
Using these APIs we perform various tasks essential to the generation of propensity scores and business intelligence dashboards.
- Pull a variety of data points on a regular basis (see below)
- Create and maintain fields on the Contact object to store the propensity scores
- Regularly push updated propensity scores into the system
Once the integration is completed, our client can use the scores in their system to create Reports and Campaigns. Additionally, the data from their system is processed to produce Reports and Analytics in the Dataro App.
Data extraction
Dataro only uses data that is essential for generating propensity scores. For example, donors can be identified by their Contact ID generated by Salesforce, so there is no need for Dataro to store a donor’s full name. A table setting out the fields extracted by Dataro for the purposes of integrated propensity scoring, please see Appendix A.
Dataro Scores
Dataro provides scores for a variety of ‘propensities’. Examples of propensities include Propensity to Give to an Appeal Gift, Propensity to Upgrade a Regular Gift, or Propensity to Churn from an RG Program. Dataro’s predictions are provided both as a Score (on a spectrum from 0-1, with 0.5 being a 50% chance of taking the relevant action) and as a Rank (with 1 being the highest). Scores and ranks will exist as custom fields on the Contact object.
For example, if you have purchased the RG Churn propensity, the following fields will be created in your system:
|
API Name |
Label |
Type |
|
Dataro_RG_Churn__c |
Dataro RG Churn |
Number(6,9) |
|
Dataro_RG_Churn_Rank__c |
Dataro RG Churn Rank |
Number(18,0) |
Personal Information Handling
Dataro is committed to delivering high-level service and satisfaction to its clients. As we deal with data on a daily basis, effective information security management is critical for our organisation, employees and clients. We seek to abide by privacy by design principles, and accordingly do not extract or store any Personal Information (as defined in the Privacy Act 1988 (Cth)) unless strictly necessary to provide our services. For example, we expressly do not store any of the following data: Last Name, Email Address, Phone Number(s), Street Address, Financial Payment Details (e.g. credit card numbers or expiry).
In some instances, we will extract data that may be classified as Personal Information. Such information is never stored on disk. This information is extracted so that it can be transformed into a more usable form for the purposes of our modelling (for example, we may extract email addresses for the purpose of identifying whether or not an individual has an email address). The Personal Information is then permanently destroyed.
Physical security
- Dataro uses cloud services provided by Amazon Web Services (AWS). All Dataro resources are hosted in Australian regions in secure facilities provided by AWS.
Data security
- Data is stored at rest using AWS Simple Storage Service (S3). The data is stored in private buckets encrypted using AES-256 and accessible directly only by the principles using multi-factor authentication protocols (MFA).
- Data is extracted from the client’s Salesforce instance using Salesforce’s Bulk API directly into Dataro’s AWS Virtual Private Cloud using a Docker container running on a server which exists only for the duration of the ingest process. No data is saved to the disk of this machine. Data is processed in the same manner. The results of each process (i.e. propensity scores and model metadata) is stored as encrypted files in S3 per the above.
- Dataro uses Amazon GuardDuty Intelligent Threat Detection to autonomously monitor our systems for any unusual activity.
- Access Logs: All access to our systems are logged for auditing purposes.
Access Control
- All access to data within Dataro environments is governed by access rights controlled by Dataro’s principles. Access to Dataro environments within Dataro is limited only to the most senior employees who have been trained in our security protocols.
Appendix A: Objects extracted and stored by Dataro
|
Object |
Notes |
|
Contact |
All PII fields are excluded from the Bulk API request |
|
Opportunity |
|
|
Account |
|
|
npe03__Recurring_Donation__c |
|
|
npe01__OppPayment__c |
|
|
Campaign |
|
|
CampaignMember |
|
|
AAkPay__Payment_Txn__c |
If the user has installed and is using the AAKonsult Recurring Payments plugin |
|
AAkPay__Recurring_Payment__c |
If the user has installed and is using the AAKonsult Recurring Payments plugin |
|
AAkPay__Recurring_Payment_Txn__c |
If the user has installed and is using the AAKonsult Recurring Payments plugin |
Appendix B: Field names on contact record
Appeals module
|
API Name |
Label |
Type |
| Dataro_DM_Appeal__c | Dataro DM Appeal | Number(9,6) |
| Dataro_DM_Appeal_Rank__c | Dataro DM Appeal Rank | Number(18,0) |
| Dataro_DM_Appeal_500__c | Dataro DM Appeal >$500 | Number(9,6) |
| Dataro_DM_Appeal_500_Rank__c | Dataro DM Appeal >$500 Rank | Number(18,0) |
| Dataro_24M_Lapsed__c | Dataro 24M Lapsed | Number(9,6) |
| Dataro_24M_Lapsed_Rank__c | Dataro 24M Lapsed Rank | Number(18,0) |
Recurring Giving Module
|
API Name |
Label |
Type |
| Dataro_RG_Churn__c | Dataro RG Churn | Number(9,6) |
| Dataro_RG_Churn_Rank__c | Dataro RG Churn Rank | Number(18,0) |
| Dataro_RG_Upgrade__c | Dataro RG Upgrade | Number(9,6) |
| Dataro_RG_Upgrade_Rank__c | Dataro RG Upgrade Rank | Number(18,0) |
| Dataro_RG_Reactivation__c | Dataro RG Reactivation | Number(9,6) |
| Dataro_RG_Reactivation_Rank__c | Dataro RG Reactivation Rank | Number(18,0) |
Convert to RG Module
|
API Name |
Label |
Type |
| Dataro_Convert_to_RG__c | Dataro Convert to RG | Number(9,6) |
| Dataro_Convert_to_RG_Rank__c | Dataro Convert to RG Rank | Number(18, 0) |
Mid Value Module
|
API Name |
Label |
Type |
| Dataro_Convert_to_RG__c | Dataro Convert to RG | Number(9,6) |
| Dataro_Convert_to_RG_Rank__c | Dataro Convert to RG Rank | Number(18, 0) |