Seeding Campaign

Gain insight into the success of seeding campaigns by filtering data by user group (based on Demographic data). This report is helpful during a seeding campaign as well as post-seeding campaigns to see and share the participation and impact of a campaign(s) by a user group. If some groups do not have high participation, it can be used to generate a user list to target communications.

The report is located in the Stock Reporting folder of the Repository. Below, you’ll find more information about fields and filters in this report. 

If you're new to Benevity Reporting, learn more about how to generate a stock report and apply filters

Users with access to Benevity Reporting can generate this report. 

Filtering your report

You can apply the following filters to the Spark User List stock report:

  • Seeding Identifier
  • User Status
  • Accepted Legal

Additional columns

You can include up to 4 additional user fields in the report columns. Select a field from the dropdown to add it as an additional column when you run the report. 

  • Custom classification 1
  • Custom classification 2
  • Custom classification 3
  • Custom classification 4


Seeding Identifier

The identifier specified for the seeding process. 

User Status

You can filter the report by User Status: 

  • Active: An active user is included in the last demographic file that was uploaded. The user can log in to their account. 
  • Inactive: An inactive user is no longer included in the demographic file. They were once included in the file and had a Benevity account created. They can no longer log in to their account. 

User Accepted Legal

When a user logs in for the first time they must accept the Benevity Terms of Use. This field indicates whether the user has logged into the program and accepted those terms or not. 

User Spark Instance Country

Spark instance countries are selected during implementation to give local users the ability to make tax-effective donations, in countries where we have a foundation partner, or donate via payroll in their local currency. All users will be mapped to one of these instances during implementation. 

Example: if you have only enabled the US instance because you have a very high percentage of US employees, a US user will be mapped to this instance. However, an employee based in Mexico would also be mapped to the US instance country. 

Example: if you have enabled the UK and France instances, because you have a high percentage of both UK and French employees, a UK user will be mapped to the UK and a French user to France. However, an employee based in Italy is likely to be mapped to the French instance country. 

The User Information | User Country field should be included in the report to indicate the country the employee is located in, not the mapped instance.

Was this article helpful?
0 out of 0 found this helpful