Salesforce + Version2 Integration Customer Onboarding Guide

Overview

This guide explains how donor data flows between Version2 and your Salesforce or Ascend environment, including portfolio setup (Data In), engagement data return (Data Out), opt-out handling, and activity mapping.

1. Building Your VEO Portfolio (Data In)

Provide a portfolio file of primary contacts only. Each record should include a valid Contact Record ID (CRM_ID). Optionally assign a fundraiser using the FUNDRAISER field.

Recommended: Use Salesforce Campaigns to organize VEO donors. Contacts are added as Campaign Members, and Campaign Member Status can track engagement state (e.g., Active, Opted Out).

Ascend: Contact Reports are associated with both the Contact and their Household Account. Only include primary contacts in your portfolio file.

2. Data Return & Engagement Processing (Data Out)

Version2 generates a Data Return File containing engagement activity. This file is imported into a Version2-managed custom object in Salesforce.

A Scheduled Salesforce Flow processes records in bulk and maps them to Activities (Task object) in Salesforce or Contact Reports in Ascend.

Messages are labeled as Inbound (donor response) or Outbound (VEO message). Conversation ID groups threads; Message ID identifies individual messages.

3. Opt-Out & Communication Preferences

Version2 returns opt-out signals for Email, SMS, and All channels.

Salesforce: Email opt-out maps to the standard Email Opt Out field. SMS and global opt-outs require custom fields.

Ascend: Opt-outs are managed using Service Indicators.

4. Field Mapping Overview

Quick Summary

Data In: Upload primary contacts with CRM_ID. Use Campaigns for organization.

Data Out: Data Return File → Custom Object → Scheduled Flow → Activities/Contact Reports.

Opt-Outs: Map appropriately to Salesforce fields or Ascend Service Indicators.

Need support?

For questions or help, please email version2support@givzey.com.