Adding and Using Custom Fields

Custom fields allow you to enhance the donor experience in Version2 by providing additional CRM data to the Virtual Engagement Officer (VEO). This supplemental information helps the VEO tailor outreach, messaging, and actions using richer constituent context than what is available in the standard Portfolio file alone.

When custom fields are used, they become part of your Portfolio file and must be included and updated with every Portfolio file delivery to Version2.

Purpose of custom fields

Custom fields are designed to give the VEO meaningful context about your donors that supports more relevant and informed engagement. They supplement, rather than replace, the required fields in the standard Portfolio file.

Examples of appropriate custom field use include:

• Graduation school or class year
• Most recent event attended
• Areas of interest
• Role indicators such as volunteer, board member, employee, or patient

Custom fields should represent stable attributes that add value to donor communications.

Custom fields cannot be used for exclusion logic, such as Do Not Solicit or Do Not Email indicators.

Custom field limits and scope

Each organization may use up to 10 custom fields.

Key considerations:

• Custom fields must be reliably exportable from your CRM
• All custom fields apply at the organization level
• Custom fields are not portfolio-specific

Because these fields are referenced across engagement logic, consistency across file deliveries is essential.

Defining custom fields before submission

Before custom fields are added to Version2, they must be reviewed to ensure they can be used effectively by the VEO.

You should work with:

• Your Onboarding Manager before launch, or
• Your Customer Success Manager after launch

For each custom field, you will need to provide:

• A clear and descriptive field name
• A brief 1–2 sentence description explaining the field’s meaning and intended use

The Custom Fields Submission tab in the Version2 Data Templates workbook should be used as a guide when defining your fields.

Review and mapping process

Once your custom fields are finalized, complete the Custom Fields Submission Template and submit it through the appropriate channel:

• Via Trello to your Onboarding Manager (pre-launch), or
• By emailing version2support@givzey.com (post-launch)

After submission, the fields will be reviewed and mapped within Version2. Allow at least one week for this process before including the fields in your Portfolio file.

Adding custom fields to the Portfolio file

After confirmation that your custom fields are ready, they can be added to your Portfolio file.

When doing so:

• Add one column per custom field
• Place custom field columns after the standard Portfolio file columns
• Use clear, descriptive column headers
• Use underscores instead of spaces in header names
• Clearly differentiate similar fields
• Keep headers under 200 characters
• Do not use commas or quotation marks in headers
• Ensure headers exactly match the names submitted in the Custom Fields Submission Template
• Keep header names consistent across all future uploads

Once complete, upload the file using the standard SFTP process.

Adding custom fields after launch

Custom fields can be added after launch as your data needs evolve. Before submitting new fields, contact your Customer Success Manager to ensure they are reviewed and properly mapped.