Registration forms
Collect registrations via Eventyvo — or keep your form and only use Eventyvo for downstream features.
Subscription required
Enable forms on your offer.
Two data situations
| Situation | What to do |
|---|---|
| People already register on your website (data in your DB) | Keep your form as SoR. For any Eventyvo feature that needs attendees (QR, Lab, certificates), mirror them into Eventyvo (CSV import / dual registration). Or migrate registration to Eventyvo forms going forward |
| Registrations already in Eventyvo | Model A CTA / subwebsite Register; Model B webhooks into your CRM |
Whole flows
Keep your form (hybrid)
Register on YOUR site → your DB
→ (optional) CSV / process into Eventyvo approved submissions
→ use Eventyvo for Lab / QR / badges later
Eventyvo as registration SoR
CTA / subwebsite Register on your site
→ Eventyvo form + payment
→ FORM_SUBMISSION* / PAYMENT_* webhooks → your CRM (Model B)
Website surface (Model A)
<div data-eventyvo="register" data-event-slug="my-event"></div>
<script async src="https://docs.eventyvo.com/embed/v1/eventyvo-embed.js"></script>
CTA opens Eventyvo-hosted registration — not a full in-iframe checkout. Full form on your domain: Subwebsite Register page.
Secure data out (Model B)
Subscribe to FORM_SUBMISSION, FORM_SUBMISSION_APPROVED, PAYMENT_SUCCESS / FAILED / REFUNDED. Verify HMAC — Payloads.
Zapier: GET .../zapier/submissions?eventId=.
Not supported
- Connect POST to create submissions from your DB
- Full checkout iframe embed
- Partner GraphQL submit APIs