Contacts are the part of Eventleash that gets more valuable over time. Events come and go; the address book stays, and every event adds to it.
You find it under Contacts in the main menu. The Host role does not see it.
What a contact is
A person, with their details, independent of any event. They become a guest when you attach them to an event, but they stay one contact even if you invite them to twenty different ones: see How Eventleash works.
An email or a phone number is required. The email is the key: it identifies the contact and cannot repeat within the same address book.
The fields
| Field | What it is for |
|---|---|
| First name, surname | Used in emails, where the placeholder substitutes them |
| The contact's key, and where invitations arrive | |
| Phone | For contacts with no email, and for a quick call on the day |
| Language | Decides which language this person's communications come in |
| Company, role | Useful in B2B, and they are filters too |
| Gender, date of birth | Only if you segment on them: age is a range filter |
| Address, city, country | For printed invitations and geographic filters |
| Socials | Only the username goes in, not the full address |
| Sizes | For whoever hands out merchandise or clothing to guests |
| Notes | The free field, where everything else ends up |
| Photo | Optional, helps recognition at the door |
Fill in what you need. A contact with a first name, a surname and an email works perfectly well: the other fields exist for those who need them, not as homework.
Organising: categories, types and groups
Three ways of grouping, different in shape:
- Category and type are single values: a contact has one of each. Good for classifications that exclude one another — press, clients, suppliers.
- Groups is a list: a contact can be in several at once. Good for labels that add up — VIP, Milan, newsletter.
All three are filters in the list, and groups can be assigned in bulk to a selection: see Searching, filtering and bulk editing.
Creating a contact
From the create button in the list. That is the right way to add one or two people; for a whole list use the import, which is much faster and does not mistype.
You can also create a contact while adding guests to an event: type an email that is not in the address book and the person is created, and stays there after the event too.
Status, unsubscribes and bounces
Three different things that get mixed up constantly.
Status: active or blocked. You are the one who blocks a contact, from the icon in the list or in bulk on a selection. A blocked contact stays visible but is excluded from sends. Use it for people you no longer want to contact without deleting them.
Subscribed or unsubscribed. Not your decision: the person takes themselves off the list using the link in your emails. It applies to your whole account and cannot be undone from the application, as explained in Privacy, consents and unsubscribes.
Bounces. When an address rejects messages for good, the contact accumulates bounces and stops being a valid recipient. This is not a punishment: it protects your sending reputation, because continuing to write to addresses that do not exist is exactly the signal providers use to classify a sender as spam.
You can filter on all three in the list, and it is the quickest way to understand why a campaign reached fewer people than you expected.
Deleting a contact
Deletion is permanent and removes the person from the address book. The guests that contact had at past events remain, with their historical data: your event statistics do not change retroactively.
If the request comes from the data subject under GDPR, this is the right operation. If you just want to stop writing to them, block the contact instead: losing the history helps nobody.
The plan limit
Contacts in the address book count against your plan's limit — a ceiling, not a monthly consumption. The counter is at the top of the list and in Plans, quotas and billing.
If you are near the ceiling, a clean-up is worth doing before upgrading: contacts with too many bounces will never be of use again.