What this helps you do
Blasts lets you reach attendees directly, with their permission. Each attendee installs the free Blasts app once (the phone app, or the browser extension on a computer) and connects to your event. From then on, every update you send arrives on their phone, clearly marked as from you, instead of competing with the rest of their inbox on the morning of the event. Your ticketing or registration platform still owns registration and payment: the Hub communicates with the audience that registration produces.
When to use it
Start at the moments attendees are already paying attention: the registration confirmation page, the ticket email, the know-before-you-go message, packet or badge pickup, and check-in signage. Do it again for each edition, though returning attendees are already connected.
How to do it
- Open Connections in your Hub and click Sync connections once so your enrollment code is published.
- Where the enrollment link is enabled for your Hub, this is your main acquisition path: one standing link, and each person who opens it gets their own enrollment page. Paste it into the registration confirmation page, the ticket email and the know-before-you-go message.
- Click Print the enrollment kit for the printable page with the code, the three steps and the audiences attendees can choose. Put it on badge inserts, packet-pickup signage and the information desk.
- Each attendee installs Blasts, opens Settings, enters your code and taps Join, or follows your enrollment link.
- For people who registered but never scanned, export the opted-in attendee list from your ticketing platform and use Invite one person or Add many at once. Invitations are checked on Blasts and spread out at up to 200 a day.
- Point your registration form or its confirmation step at the inbound webhook on Integrations, or use the Zapier app, so each new registrant is invited the day they buy.
- Accept requests under People who want to connect, or turn on auto-accept in Settings during the registration window.
Example
The enrollment link goes in the ticket confirmation and the kit is printed for the packet-pickup banner. Attendees connect over the weeks before the event, and by the time the parking notice goes out on Friday night most of the room has it on their phone. On event morning, when a gate changes, the organizer reaches them in one send rather than posting a sign and hoping.
Good to know
- It is permission-based: attendees opt in, and they can mute or disconnect anytime, including after the event.
- The connection persists after the event ends, so next year's edition starts with an audience instead of a cold list. Whether you may invite those people to a future event is a consent question, not a technical one: say at enrollment that you will send news about future editions.
- There is no ticketing or registration connector. Your attendee list reaches the Hub as a CSV export, through the inbound webhook, or through Zapier.
- Import columns: your file needs an email column. The Hub also recognizes name, first name, last name, phone, address, city, state or province, ZIP or postal code, country, birthday, household, and interests (a column headed audiences, tags, groups or lists works too). Files are limited to 5,000 rows and 2 MB, with a preview before anything is sent.
- The Reach funnel on Connections shows where every attendee stands (known, invited, requested or connected) and how they arrived: code, import, webhook, request or Zapier.