How to issue certificates for webinars and conferences
Online and in person, the pattern is the same: one list, one design and a rule for who qualifies. The details that trip people up are the rule and the export.
Short answer
Set an attendance rule, export the attendee list from your webinar or registration tool as a CSV file, remove those who do not qualify, and issue. Certifyd does not connect directly to webinar or ticketing tools today, so the CSV file or the REST API is the bridge.
Set the rule first
Online events produce a lot of data and no obvious cut-off. Decide in advance what earns a certificate: registering, joining, staying for a minimum share of the session, or answering a closing question. Tell attendees up front so nobody is surprised afterward.
Get the list out of your platform
Most webinar and registration tools can export attendees as a spreadsheet. Save it as CSV and keep the name and email columns, which Certifyd requires. Certifyd issues from the list after the event; it does not track attendance inside your webinar tool.
- Remove registrants who never joined.
- Merge duplicate rows for people who joined from two devices.
- Fix names typed as handles or initials, because the name prints on the certificate.
Tier the certificates
- Attendees receive a certificate of attendance.
- Speakers can receive a badge or a different certificate from their own list.
- Bilingual events can issue in English or Spanish; emails and verification pages work in both.
Each certificate or badge is one credential, so a person given both uses two.
Send soon, and let it spread
People value a certificate most in the days after the event. Each recipient can share it to LinkedIn from their portal, which puts your event name in front of their network. Certifyd does not issue continuing-education credit and does not accredit events; if your attendees need accredited credit, that comes from the body that accredits you.
Webinar and conference mistakes to avoid
Events scale quickly, and so do small mistakes. These are the ones that cause the most clean-up.
- Issuing to everyone who registered, then explaining to non-attendees why they received one.
- Leaving the attendee list in the platform's raw format, with columns Certifyd cannot read as first name, last name and email.
- Waiting weeks, by which time attendees have forgotten the session and some emails have gone stale.
- Forgetting the monthly allowance: a 300-person conference cannot be issued on the free plan's 12 credentials a month.
Do a test with a handful of real attendees first. If the names print well and the emails arrive, send the rest. The free plan is enough to rehearse the whole flow with a small group.
Checklist before you send
- The attendance rule was announced before the event.
- The list is exported as CSV with name and email columns.
- Non-attendees and duplicates are removed.
- Speakers have their own certificate or badge.
- Your monthly allowance covers the whole list.
Questions
Does Certifyd work with Zoom or my ticketing tool?
Not directly today. Export the attendee list as a CSV file and import it, or send it through the REST API.
How many certificates can I send at once?
Bulk issuing from a CSV file is on every plan. Your plan sets the monthly allowance, and the free plan includes 12 credentials a month, so a large event needs a paid plan.
Does re-sending an email use another credential?
No. Re-sending an email or downloading the PDF again never uses another credential.
