Connect your Steep Marketing account to LeadCenter to automatically sync seminar and event registrations. When a registration matches an existing LeadCenter event, LeadCenter imports the registrant as a contact, adds the person as an attendee, and can also add guest attendees included with the registration.
This article covers:
Create your upcoming Steep events in LeadCenter before registrations start coming in. Steep registrations only sync to events that already exist in LeadCenter.
Recommended: Create the event in LeadCenter before registrations begin syncing. If a matching event does not exist yet, that registration is skipped. Creating the event later does not automatically import registrations that were already skipped.
LeadCenter runs an initial sync after the connection is saved. Depending on how many registrations already exist, the first sync may take a few minutes.
When a Steep registration matches a LeadCenter event, LeadCenter imports the registration into the same event, attendee, and contact areas you already use in LeadCenter.
Steep does not create or update the LeadCenter event itself. Event details such as the event name, date, time, venue, and capacity remain managed in LeadCenter.
LeadCenter matches Steep registrations to existing LeadCenter events using event details such as the start date, start time, ZIP code, venue name, city, and state.
The event title is not used for matching in-person events, so your LeadCenter event name can differ from the event name in Steep. For Steep webinars, LeadCenter can use the event name when more than one webinar is on the same date.
Matching works best when the LeadCenter event uses the same date, start time, and ZIP code as the Steep event.
For more detail about how LeadCenter matches registrations to events, see How LeadCenter Finds Events When Receiving Registrations.
When Steep marks a registrant as Appointment Set, LeadCenter assigns the event attendee status Appointment scheduled. This applies when a registration first imports and during the daily refresh for upcoming events.
Steep often sends Appointment Set together with its attended flag. LeadCenter still assigns Appointment scheduled in that case. For every other Steep status, the attended flag maps to Attended.
Other Steep values map as follows: Canceled to Cancelled by attendee, No Show to No show, Waitlist to Waitlist, Confirmed to Confirmed, and anything else to Registered.
Steep is the source of truth for attendee status on upcoming synced events. If you manually change an upcoming attendee's status in LeadCenter, a later Steep sync can change it back to Steep's current value.
After an event has started, LeadCenter stops refreshing that event's attendees, so statuses set in LeadCenter then stay in place.
If you delete an attendee in LeadCenter, later Steep syncs do not bring that person back.
If you manually change an upcoming attendee's status in LeadCenter, a later Steep sync can change it back to Steep's current value.
LeadCenter can send event emails and text messages when a new registration is imported or when an attendee status changes through the Steep sync.
For events marked Scheduled, LeadCenter can send the email or text message configured for Appointment scheduled when Steep reports Appointment Set. If no template is configured for that status, the attendee status still updates and no message is sent.
Event communications are sent only when all of these conditions are met:
If the event is still in Draft, Completed, or Cancelled status, attendee data can still sync, but event emails and text messages are not sent.
Guest attendees from Steep do not receive these event emails or text messages.
Before creating a new contact from a registration, LeadCenter checks whether the registrant already exists in your account.
For more detail about how LeadCenter matches registrations to existing contacts, see How LeadCenter Matches Event Registrations to Existing Contacts.
Because attendee updates are part of the daily refresh, changes made in Steep after the original registration can take up to 24 hours to appear in LeadCenter, and only while the event is still upcoming and within that 30-day window. After an event has started, attendee updates from Steep are not refreshed.
If a guest is removed from a registration in Steep, the daily refresh can remove that guest from the LeadCenter attendee list while keeping the primary registrant and any remaining guests intact.
Disconnecting Steep stops future syncs, but it does not remove events, contacts, or attendees that were already synced into LeadCenter. If a later sync rejects the API key, LeadCenter also disconnects Steep automatically.
If you disconnect Steep and connect it again later, LeadCenter treats the reconnection like a first-time connection. The next sync checks recent registrations only. It does not automatically replay every registration received while the integration was disconnected.
Create the applicable Steep events in LeadCenter before reconnecting. Registrations can import only when a matching LeadCenter event already exists.
A success message confirms that Steep is connected and the initial sync has started. You can continue using LeadCenter while the sync runs.
Need older registrations? A longer backfill is not performed automatically. Contact LeadCenter Support when registrations outside the recent sync window must be imported.
If you can't find the answers you're looking for, our support specialists are available to answer your questions and troubleshoot if necessary.