Omnisend is included on every Quinn plan, including Free. Connect it alongside Klaviyo or Mailchimp if you use more than one tool. Your Omnisend plan determines which segments and automations you can use.
- In Omnisend, create an API key with contacts.read, contacts.write and events.write permissions. Keep the key private.
- Open Integrations in Quinn and choose Omnisend. Paste the key into Private API key, then connect.
- The connection check verifies that the key can read contacts. A real quiz delivery checks contact and event write permissions. A successful connection test creates no test contact or event.
- The option Also send quiz takers who haven’t agreed to email marketing starts off. Leave it off to send only quiz takers who agreed to marketing. Enable it only if you also want those leads sent. New contacts are Non-subscribed; existing subscriptions are preserved.
- Complete a published quiz on your storefront and submit an email. Preview mode saves no leads and sends nothing. In Omnisend, find the email in Audience, open its profile and check its custom properties and activity.
Non-subscribed contacts count toward Omnisend’s contact limits and may affect your bill. See how Omnisend handles Non-subscribed contacts.
After connecting, change the checkbox and choose Save preferences to save without entering your key again.
What arrives
For leads allowed by your setting, Quinn sends the captured email, name and phone, quiz answers and recommended products. Each quiz has a separate quinn_ prefix for its custom contact properties. The Completed Quinn quiz custom event carries the completion details. Find the event in Omnisend’s custom events settings and use it in a workflow supported by your plan.
The phone is quiz data, not an SMS subscription. Only recorded marketing consent can subscribe an email. By default, quiz takers without that consent send no contact or event. If you enable the option to also send them, new contacts are added as Non-subscribed and existing subscriptions are preserved. Turning the option on does not backfill previously skipped leads.
Check delivery or disconnect
The Omnisend card shows the last connection check and real quiz delivery separately. Delivery happens in the background. A bad key stops further delivery attempts until you reconnect with a working key. Check the displayed reason, correct the key or permissions, and test again.
If acceptance could not be confirmed, check the contact’s activity in Omnisend before retrying. Omnisend’s real-time events do not provide deduplication for automation triggers. Quinn avoids automatically resending an event after an ambiguous timeout.
To stop sending new quiz details, choose Disconnect and confirm. This deletes the saved encrypted key. Contacts and events already sent stay in Omnisend.