Salesforce Event Management

What to keep in the CRM and what to run in an event platform

The CRM is the system of record for people and relationships. It should know who attended, who is a customer, who is a prospect and what happened next. An event platform is the system of record for the event itself: ticket types, the registration form, the agenda, the badge, the check-in scan, the session count.

Trouble starts when one system tries to do the other's job. A CRM is not built to print a badge or scan a ticket at a door with no signal, and an event platform is not built to run a sales pipeline. Give each its job and sync the overlap.

A useful test is to ask who edits the data. If the event team changes it every day, such as a session room or a ticket price, it belongs in the event platform. If sales or marketing works from it every day, such as an account owner or a campaign, it belongs in the CRM. Data both teams touch, such as a registrant's job title, needs a rule about which side wins.

The data worth syncing

Sync the data that someone will act on, and leave the rest. Every field you add is one more thing to map, test and fix when it breaks. Four groups cover most needs:

Also decide how often each group moves. Registrations may need to reach the CRM within minutes so that sales can see a key account sign up, while attendance and session data can wait until the event closes. A single schedule for everything is simpler, but a faster one for the data people watch live is often worth a little extra setup.

• Registrants

  Name, email, company, ticket type, registration date and status. This is what lets marketing see who signed up and sales see which accounts are coming.

• Attendance

  Whether the person checked in, and when. Registered is not the same as attended, and follow-up depends on the difference.

• Leads

  Contacts captured at a booth or by staff, with notes and a rating if you use one, so the right owner sees them quickly.

• Sessions

  Which sessions a person registered for or attended, if you want to segment follow-up by interest. Decide if this is worth the effort before you build it.

Ways to connect an event platform to Salesforce

There are four general approaches. Which one fits depends on how much you need to sync, how fast, and who maintains it.

Whichever you choose, ask who is responsible when it fails. A built-in integration is supported by the vendor, an automation is supported by whoever built it, and a custom build is supported by your own developers. Teams that run many events a year usually want the first, and teams with unusual CRM setups often end up with the third.

• A built-in integration

  The event platform ships with a Salesforce connection. It is the quickest to start with, so long as it covers the fields and direction you need. Ask exactly what it maps.

• An automation tool

  A tool that links apps by triggers, such as a new registration creating a contact. It suits modest volumes and simple rules, and someone has to own the automations.

• An open API

  A direct build against the platform's API and Salesforce's. It gives the most control and takes development time and upkeep.

• File export and import

  A CSV exported after the event and loaded into the CRM. It is slow and error-prone but needs no setup, and is a sensible fallback for a first event.

A data-mapping table to fill in

Before anything is connected, decide which field in the event platform feeds which field in Salesforce, which system wins when they disagree, and how duplicates are handled. This table is the core of the plan.

Setup checklist

Work through these in order, and run the whole path with a test event before a real one.

1. 1

   Name the outcome

   Write one sentence: for example, every registrant and attendee appears in Salesforce within a day of the event, tied to a campaign.

2. 2

   Agree the owners

   Decide who owns the integration in marketing, in sales operations and on the event team. Unowned integrations break quietly.

3. 3

   Fill in the mapping table

   Complete it with a Salesforce administrator before connecting anything.

4. 4

   Decide the duplicate rule

   Match on email, say what happens when a record exists, and test with real duplicates.

5. 5

   Connect and run a test event

   Register a few test people, check some in, add a test lead, and confirm each lands in the right place.

6. 6

   Settle consent

   Record opt-in at registration and sync it, so follow-up respects what attendees agreed to.

7. 7

   Set up the reports

   Build the campaign and attendance reports sales will use before the event, not after.

8. 8

   Plan the failure case

   Know how to export and load the data manually if the sync fails on the day.

Pitfalls to avoid

Most problems with a CRM and an event platform come from the same few mistakes.

None of them is hard to avoid, but each is far easier to prevent in the planning stage than to repair after thousands of records have synced. Review this list with your Salesforce administrator before the first test.

• Treating registered as attended

  Sync check-in as its own status. Otherwise no-shows get follow-up meant for people who came, and the people who did attend get a message that treats them as absent.

• Letting duplicates multiply

  Two spellings of one company or two emails for one person create duplicate records. Set the match rule before the first import.

• Syncing everything

  Every extra field is one more thing to map and maintain. Sync what someone will act on.

• Ignoring consent

  An opt-out in one system must not be overwritten by a later sync from the other.

• Skipping the test

  An integration that was never tested end to end fails on event day, when nobody has time to look at it.

What Eventdex says about Salesforce

Eventdex's pages describe a Salesforce integration and give details at a general level. They describe real-time data exchange through APIs and connectors, covering attendee information, event schedules and registration details, and say it helps sales and marketing teams manage attendee data, registrations and leads in the CRM. Eventdex's FAQ also says it has a built-in Salesforce integration and connects to most other apps through Zapier and an open API.

The pages do not list which Salesforce objects and fields are mapped, so ask for that in a demo and check it against your own mapping table. Eventdex pricing is by quote.

• Salesforce integration page

  What the integration does, and how attendee data, registrations and leads reach the CRM.

  Eventdex and Salesforce integration

• All integrations

  Zapier, Salesforce, payment gateways, scanners, printers and single sign-on, listed in one place.

  Eventdex integrations

• Registration software

  The registration form, ticketing and check-in that produce the data you sync.

  Event registration software

• Zapier connection

  Connecting Eventdex to other apps through Zapier.

  Eventdex and Zapier