- the event as a Campaign
- each person as a Contact
- each registration as a Campaign Member
Who can connect
Organization Owners and Admins — the same permission as registering a webhook. A connection writes names, email addresses, and attendance from this Business Unit into another system. One Business Unit holds one CRM connection.Connecting
1
Open the drawer and choose CRM
The drawer’s Business Unit selector sets which unit is connected.
2
Connect Salesforce
The browser opens Salesforce to sign in and authorize orriven. On return, the console shows the unit’s events list and the tab shows the connection.
3
Confirm the connection card
The card shows the Salesforce org name (or its instance address), the instance, the time of the last sync, and — after consecutive errors — the number of consecutive failures.
Whether sign-in goes to Salesforce production or a sandbox is set per orriven deployment, not per Business Unit. To test against a sandbox before go-live, ask the platform administrator. A deployment with no Salesforce app registered shows “Not available yet” and the connect button is inactive.
What is synced
The mapping is fixed. People are written as Contacts, never Leads. Filing attendees as Leads creates duplicate Contacts.
Field values are read at sync time, not when the event occurred. A name corrected before the sync runs is the name that is written.
When it syncs
A sync is queued when a person is added to an event: an attendee added from the console, a registration confirmed (checkout completed or approved), or a registration checked in at the event door. Each queues three items in order — the Campaign, the Contact, then the Campaign Member. The Campaign Member waits for the other two instead of failing. Orders expiring, surveys, and other event types are not synced. Only records created after the connection are synced. Earlier registrations are not backfilled.Duplicates
The same person registering for a second event — or more than once for the same event — remains one Contact in Salesforce, with one additional Campaign Member. Each local object maps to one Salesforce record. Salesforce’s Email match is a second check.The sync log
Below the connection card, the tab lists recent syncs: the object (Campaign, Contact, Campaign member), the subject (the event’s name or the person’s email), the Salesforce ID once it exists, and the status — Queued, Syncing, Synced, or Failed. A failure is retried on the same schedule as webhooks — immediately, then 1 minute, 5 minutes, 30 minutes, 2 hours, and 6 hours after the previous attempt, six attempts in all — then marked Failed. A failed row offers Retry. Failures increment the connection card’s counter. The platform does not disconnect the integration. A Salesforce error does not block or roll back the registration or checkout that queued the sync.Disconnecting
Disconnect stops further syncing. Records already written stay in Salesforce, and the existing mapping is kept, so reconnecting later does not create second copies. Connecting and disconnecting are recorded in the audit log.Rules
- One Business Unit, one connection. The connection’s scope is the unit it was made in.
- Contacts, not Leads. The mapping is fixed; there is no field mapper.
- Fields are current. Salesforce receives the value at sync time.
- Erasure does not propagate. A data-privacy erasure in orriven does not delete the corresponding Salesforce records. Retention in that CRM follows its own policy.
- Not backfilled. Only registrations after the connection are synced.
Related
Developer tools
The drawer that contains the CRM tab.
Webhooks
HTTPS POST events, for systems other than Salesforce.
Attendees
Where registrations and contacts come from.
Members & roles
Why connecting is Owner/Admin only.