Capture webinar registrations as track events
Each webinar signup fires a "Registered" event tied to the work email and session name, so reminders and reporting agree.
New Submission on your "Webinar signup" form
Create a "Registered" track event in Segment tied to the user's email and the event name
One-directional. A submission triggers the action — nothing is written back into your form.
Webinar registrations tend to sit in whichever tool collected them. Reminder emails go out from one place, the attendance report comes from another, and the two numbers never quite line up when someone asks how the session did.
Sending a "Registered" track event to Segment gives every destination the same registration record, keyed to the work email and tagged with the session. Marketing teams running a monthly series use this so each session's funnel can be compared against the last without exporting anything.
Setting it up
- 1
Duplicate the Webinar Registration Form for each session and publish it. One form per session is what lets the session name be attached reliably later.
- 2
In Zapier, set the New Submission trigger to the form for the session you are promoting, and load a sample registration.
- 3
Add Segment as the action, choose Create Track Event, and name the event Registered so every session reports under one event name rather than one per webinar.
- 4
Map Work Email to the userId. It is the value your reminder tool and your attendance report both key on, which is what makes the two reconcile afterwards.
- 5
Type the session name into an event_name property as a static value — "Q3 pricing teardown", for example. Because you publish a form per session, that value is fixed for the whole Zap.
- 6
Map How did you hear about this webinar? to a source property, and Company to a company property, so registration volume can be broken down by channel and by account.
- 7
Pass Email Updates through as a marketingOptIn property, and let your email destination decide who gets follow-up sequences rather than the reminder itself.
- 8
Register once as a test, check the Registered event in the Segment source debugger, then turn the Zap on.
What maps where
Using the Webinar Registration Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Segment |
|---|---|
| Work Email | userId on the Registered track event |
| First Name | firstName property |
| Last Name | lastName property |
| Company | company property |
| How did you hear about this webinar? | source property |
| Email Updates | marketingOptIn property |
Variations worth knowing
Anything you'd like us to cover? is the most useful field on the form and the one most often left in the submissions list. Send it as a question property on the Registered event, and the host can pull the full list from the warehouse the morning of the session.
Add a second Segment action, an identify call carrying Company Size and Job Title as traits. Registration stays an event; seniority stays a trait. Sales destinations can then filter the same registration list down to the accounts worth a follow-up call.
If something isn't arriving
The event_name property was never set, so there is nothing to group by. Add it as a static value in each session's Zap — the form is per session, so the value only has to be typed once.
Check the trigger is New Submission rather than a scheduled search step. The submission trigger is real time, so a delay usually means the Zap is polling on a schedule instead of firing on the event.
Frequently asked questions
How do I send the session name with a webinar registration?
Publish one form per session and type the session name into the Zap as a static property. The registrant never sees or fills that field, and every event from that form carries the same session value without a mapping step.
Can one Zap handle a whole webinar series?
It can if the series shares a single form, but then every registration carries the same session name. Running one Zap per session costs a few minutes of setup and keeps per-session reporting intact for the rest of the year.
How fast does a registration reach Segment?
The New Submission trigger is real time, so the event usually lands in the Segment source debugger within seconds of someone hitting submit. Reminder tools connected as destinations pick it up on their own schedule after that.
Related automations
- Identify a new lead from a demo request
Every demo request becomes a Segment identify call, so the lead's traits reach your CRM, warehouse and ad tools at once.
- Log product feedback as an event
Each feedback response sends a "Feedback Submitted" event with rating and product category, ready to query beside in-app behaviour.
- Record a support request as an event
Each support form submission emits a "Support Requested" event with topic and priority, giving analytics a live view of inbound volume.
- Send order details as an Order Placed event
Each custom order submission emits an "Order Placed" event with product and quantity properties, feeding the warehouse without a developer.
- Track a newsletter signup as an event
Each subscribe form submission fires a "Signed Up" track event carrying the source, so every destination counts the signup the same way.
- Add webinar registrants to a remarketing list
Every webinar registration joins a Customer Match audience you can run follow-up campaigns to after the session.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free