Overview
Altvia Integration
Sync investor events and LP engagement with Altvia. Track AGMs, fundraising events, and investor relationships through Altvia Functions with automatic RSVP and attendance sync.
See It in Action
Section titled “See It in Action”Watch how the integration handles a real investor event. From guest list to check-in to Altvia.
How It Works
Section titled “How It Works”Your investor relations team lives in Altvia. They track LP relationships there. Build reports there. Log meeting notes there.
But when you run events, guest data ends up in spreadsheets. After every AGM, someone manually updates Altvia with who showed up. Weeks later. When the GP asks about investor engagement, the data is incomplete.
Gatsby acts as your staging area for investor events. It captures RSVPs and attendance at the door, cleans up the data (typos, walk-ins, plus-ones), and pushes clean records back to Altvia automatically.
Your CRM stays the source of truth. Gatsby feeds it event participation data.
What Syncs
Section titled “What Syncs”This is a Salesforce integration under the hood. Altvia uses Salesforce custom objects. If you’ve read the Salesforce integration page, you know how this works.
The difference is terminology. Functions instead of Campaigns. Function Attendees instead of Campaign Members.
RSVP Status
Invitation responses sync to Function Attendees. When an LP responds to your AGM invitation, their status updates in Altvia automatically.
Values: None, Invited, Declined, Accepted, Waitlist, Maybe
Attendance Status
Check-in data syncs to Function Attendees. Ground truth of who actually showed up.
Values: N/A, Yes, No Show
Function Attendee Updates
Adding or removing guests in Gatsby updates Function Attendee lists in Altvia. The reverse works too.
First-Party Contact Updates
When investors update company or title during registration, those changes can sync back to their Salesforce Contact record in Altvia. First-party data from the LP themselves. Not stale enrichment databases.
You control the sync direction per field. See Data Flow Options for details on Sync, Enrich, and One-Way settings.
Linking Events to Functions
Section titled “Linking Events to Functions”Each Gatsby event connects to an Altvia Function. Guests become Function Attendees. RSVP and attendance data syncs to their record.
Connecting to an Existing Function
-
Open your event in Gatsby.
-
Go to Event Details.
-
Select an Altvia Function from the dropdown.
-
Save.
Creating a New Function from Gatsby
-
In Event Details, click Create New instead of selecting existing.
-
Name the Function.
-
Optionally select a parent campaign.
-
Save. The Function creates in Altvia automatically.
What You Need
Section titled “What You Need”Prerequisites match the Salesforce integration. See the Salesforce integration page for full setup details.
Prerequisites (Same as Salesforce)
- Marketing User checkbox enabled on the connecting user’s Salesforce profile
- Change Data Capture enabled in Salesforce Setup
- Your Altvia login URL (typically
https://login.salesforce.com)
See Salesforce Integration: Prerequisites and Permissions for step-by-step instructions.
Security Note
Gatsby is SOC2 Type 2 compliant. The integration uses OAuth for authentication. No passwords stored.
The Altvia integration requires an additional subscription. Contact us on Slack or email for pricing.
Altvia-Specific Configuration
Section titled “Altvia-Specific Configuration”After completing the standard Salesforce connection, enable custom objects for Altvia Functions.
Enabling Custom Objects
-
Go to Team Settings > Linked Services > Salesforce.
-
Toggle Use Custom Objects to ON.
-
Map the fields:
- Event Object:
Function__c - Event Object Name:
Name - Event Start Date:
Start_Date__c - Event End Date:
End_Date__c - Guest Object:
Function_Attendee__c - Guest Contact ID:
Contact__c - Guest Event ID:
Function__c
- Event Object:
-
Save.
Change Data Capture for Custom Objects
In Salesforce Setup, ensure these custom objects are in Selected Entities:
Function__cFunction_Attendee__c
Add these in addition to Campaign, Campaign Member, and Contact if you also use standard Campaigns.
Fallback Account
New contacts need a Salesforce Account. Configure a fallback for LPs that Gatsby can’t match to an existing Account.
Many PE/VC firms use a generic account like “Event Registrations” or “Gatsby Contacts.” Your team can reassign new contacts to proper Accounts in Altvia after the event.
See Salesforce Integration: Configuring Fallback Account for setup steps.
Common Questions
Section titled “Common Questions” How is this different from the Salesforce integration?
It’s the same integration, configured for Altvia’s custom objects. Altvia uses Functions (custom Salesforce objects) instead of standard Campaigns. You get all the same sync capabilities, just mapped to Altvia’s data model.
Do I need to follow the full Salesforce setup?
Yes. The Salesforce page covers prerequisites, permissions, and field configuration in detail. This page covers only the Altvia-specific custom object mapping.
What if we use both standard Campaigns and Altvia Functions?
You can. The integration supports both. When linking an event, you’ll see both standard Campaigns and Functions in the dropdown.
When does data sync?
Most updates sync immediately. Check in an LP at your AGM. Altvia updates in seconds.
Bulk operations (CSV imports, mass RSVP updates) sync in batches every few minutes. Still fast. Just not instant.
Does this cost extra?
Yes. The Altvia integration is an add-on. Contact us for pricing.
What about de-duplication?
Same as Salesforce. The integration matches on email address to prevent creating duplicate contacts. See Salesforce Integration: De-duplication for details.