Custom Field FAQs

Custom fields allow you to tailor your donor’s experience by providing supplemental CRM data to the Virtual Engagement Officer (VEO). This enables personalized messaging and actions based on rich constituent context. If used, custom fields are included in your Portfolio file and must be updated with every delivery to Version2.

How do custom fields work in Version2?

Custom fields allow you to provide additional CRM data to the Virtual Engagement Officer (VEO) so donor outreach can be more personalized and context-aware. These fields supplement the standard Portfolio file and must be included and refreshed with every Portfolio file delivery if they are used.

What are custom fields used for?

Custom fields give the VEO additional insight beyond what is available in the standard Portfolio file. They can be used to inform messaging, tone, and engagement logic.

Common examples include:

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

Custom fields should represent stable, meaningful attributes that enhance donor context.

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

How many custom fields can you use?

You may include up to 10 custom fields per organization.

Important considerations:

• Custom fields must be fields you can reliably export from your CRM
• All custom fields are organization-wide
• Custom fields are not tied to individual portfolios

Consistency is critical, since these fields must be updated with every Portfolio file submission.

How do you define custom fields correctly?

Before submitting custom fields, connect with the appropriate contact:

• During onboarding: your Onboarding Manager
• After launch: your Customer Success Manager

They will help confirm whether the fields you are considering can be used effectively in VEO communications.

For each custom field, you must provide:

• A clear, descriptive field name
• A brief 1–2 sentence explanation of what the field represents and how it should be used

The Custom Fields Submission tab in the Version2 Data Templates workbook should be used as your reference and guide.

What happens after custom fields are submitted?

Once your custom fields are finalized:

1. Complete a copy of the Custom Fields Submission Template

   Submit it through the appropriate channel:

   • Onboarding Manager via Trello (pre-launch)
   • Email to version2support@givzey.com (post-launch)

After submission, the fields will be reviewed and prepared for use. Allow at least one week before including them in your Portfolio file.

How do you add custom fields to your Portfolio file?

When adding custom fields to your Portfolio file, follow these rules carefully:

• Add one new column per custom field
• Place custom field columns after the standard Portfolio file columns
• Use clear, descriptive column headers
• Use underscores instead of spaces (for example: GRADUATING_SCHOOL)
• Differentiate similar fields clearly (for example: GRADUATING_SCHOOL_2)
• Limit headers to 200 characters
• Do not include commas or quotation marks in headers
• Ensure headers exactly match what was submitted in the Custom Fields Submission Template
• Keep header names identical across all future uploads, as changes will cause mapping issues

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

Can you add more custom fields later?

Yes. Additional custom fields can be added after launch.

Contact your Customer Success Manager before submitting new fields so they can be properly reviewed and mapped.

Need support?

For questions or help, please email version2support@givzey.com. If you are still in onboarding, please connect with your Onboarding Manager.