Lead Capture
Every registration is linked to a profile. A registration from someone new creates their profile, so a published event is also a way to collect leads. This page explains how registrations find or create profiles, what they write to them, where they show up, and how workflows follow up.
Matching by Email
A registration is matched to a profile by its email address. When a profile with that email exists, the response is linked to it and no new profile is created. Each email address can register once per event.
New Profiles
When no profile has the email address, the registration creates one:
- with the first name, last name and email address from the form
- with a role in the institution at the lifecycle's initial state (see Lifecycle & Journeys)
- with the event registration as its source (see Profiles)
The source category is, in order of preference, the one chosen by staff in Add participants, then the event's Default source category. New events take their default source category from the institution's events source category setting.
Answers Written to the Profile
The First name, Last name and Email address fields, and any field mapped to a profile field in the earlier editor, write their answers to the profile. A mapped answer fills a profile field only when it is empty, unless the mapping was set to overwrite. Answers to other fields stay on the response; the responses list and its export show them.
When the visitor is signed in, the event page prefills the form from the same mapped profile fields.
Consent
The privacy policy and marketing consent agreements given on the event page are recorded on the profile, with the registration as their source. With Show marketing consent on form off, no marketing consent is recorded.
Where Registrations Show Up
| Place | What appears |
|---|---|
| The profile's activity stream | A "registered for" story naming the event, for each new registration |
| The inbox | A card for each new registration, when the inbox module is on |
| The profile's activity summary | The number of events registered for and attended, and the list of events with the person's response |
| The journey summary | The number of events attended |
| The event's responses list | The response, with the profile's columns |
Merging and Deleting Profiles
- Merging two profiles moves the source profile's event responses to the target profile.
- Deleting or scrubbing a profile removes its event responses, and the event's counters are updated.
Follow-Up Workflows
The event's Automation tab lists its workflows and creates new ones. It is shown to staff with automation access. A workflow starts on one of these triggers:
| Trigger | Starts when |
|---|---|
| Response is created | A new response is saved |
| Response is marked as Yes | A response is created as Yes, or changes to Yes |
| Response is marked as Maybe | A response is created as Maybe, or changes to Maybe |
| Response is marked as No | A response is created as No, or changes to No |
| Attendance is marked as Yes | Attendance becomes Attended |
| Attendance is marked as No | Attendance becomes Did not attend |
The first four triggers only start for responses submitted before the event's end date; the attendance triggers start at any time. Bulk updates and imports start triggers like single changes do.
The workflow steps offered for events are Wait, Send email, Notify staff of the registration, Send SMS, Add to product, Add to product by name or ID and Add tag. Conditions can test profile fields and the answers given on the registration form. See Automation for the workflow builder.
Note: Workflows are copied when an event is duplicated and removed when it is deleted.
Upcoming Events on Content Pages
Content pages can list the institution's published upcoming events, so prospects can find and open their event pages.