Omnisend
Send quiz emails to Omnisend as tagged contacts with their answers, and start automations from the “Teacup quiz completed” event with the shopper’s products.
Available on Starter, Growth and Plus
#What the connection does
With Omnisend connected, every email a shopper leaves in your quiz becomes an Omnisend contact, tagged with the quiz and the result, with the shopper’s answers as contact properties. A “Teacup quiz completed” event carries their products and a one-click cart link, ready to start an automation.
#Connect Omnisend
- In Omnisend, open Store settings → API keys and click Create API key.
- Give the key access to Contacts and Events, create it and copy it.
- In Teacup Quiz, open Integrations and paste the key into API key in the Omnisend section.
- Click Connect Omnisend. You see “Omnisend connected (…)” with your Omnisend store’s address.
| Message | What to do |
|---|---|
| “That doesn’t look like an Omnisend API key.” | Only part of the key was pasted, or something else. Copy the whole key again. |
| “Omnisend didn’t accept that API key. Check that it has access to contacts and events.” | Create a key with access to Contacts and Events. |
| “Omnisend couldn’t be reached right now (…). Please try again.” | A passing problem at Omnisend. Try again in a moment. |
The key is stored encrypted. Once connected, the section shows Connected and the key’s first and last characters, with “No quiz emails sent to Omnisend yet.” until the first email goes through. On the Free plan, Connect Omnisend is off and the section says “Omnisend comes with Starter and up.”
#The contact
Each accepted email creates the contact in Omnisend, or updates it if it’s already there:
| Field | What it holds |
|---|---|
| Tags | “source: teacup quiz”, “teacup: {quiz name}” and, on result-page quizzes, “teacup result: {result name}”. |
One teacup_ property per profile answer | A question with the short label “Skin type” becomes teacup_skin_type, holding the answer, like “Oily”. |
teacup_quiz | The quiz’s name. |
teacup_result | Result-page quizzes only: the result’s name. |
Profile answers come from the questions you gave a Short label on the results page: see Collecting emails. The phone number from the email step isn’t sent to Omnisend.
#Subscriptions and consent
- The shopper ticked your marketing box: the contact’s email status is set to subscribed, with Teacup Quiz recorded as the source of the consent, and Teacup Quiz asks Omnisend to send its welcome message.
- The shopper didn’t tick it: the contact is added or updated, and its subscription status stays as it was.
#The “Teacup quiz completed” event
Each accepted email also sends one event, with these properties:
| Property | What it holds |
|---|---|
quiz | The quiz’s name. |
result | On result-page quizzes, the result’s name. Otherwise empty. |
result_url | The result’s landing page, when it has one. |
for_whom | Who the picks are for, like “oily skin”: the Good for text of the answer to the first question with a short label, or the result’s name. Can be empty. |
answers | The profile answers, by short label. |
products | Each product with title, url, image, price, step and good_for. |
cart_url | A link that puts every product in the cart. |
total | The products’ total, like $86.00. |
Products that can’t be bought right now are left out, and prices are in your store’s currency, as in the Klaviyo event. Note the spelling: Omnisend’s event is “Teacup quiz completed”, while Klaviyo’s is “Teacup Quiz Completed”.
#Start an automation
- Take your quiz on your store and leave an email, so Omnisend receives the event once. Open your store with Open your store in the setup guide or Try it on your store in Put it on your store: then you can leave the same address again for every test. With a link you typed yourself, use a fresh address or different answers if you tested in the last 24 hours.
- In Omnisend, create an automation that starts from the custom event “Teacup quiz completed”.
- In the email, show the event’s
productsand add a button that links tocart_url. - Turn the automation on.
#If contacts stop arriving
If Omnisend is down, busy or can’t be reached, Teacup Quiz tries again a few seconds later: always for the contact (sending it twice changes nothing), and for the “Teacup quiz completed” event only when Omnisend answered that it didn’t take it (too many requests, or unavailable). An event that may have arrived isn’t sent again, so your automation never emails a shopper twice. When it still fails, that email isn’t sent to Omnisend; it stays on the Emails page. A key Omnisend refuses isn’t tried again. There’s no day-long resending like Klaviyo’s.
While Omnisend is connected, its section on Integrations shows how it went:
| What you see | What it means |
|---|---|
| “Last quiz email sent to Omnisend: …” with the time | The last email that went through. Compare it with the newest email on the Emails page. |
| “No quiz emails sent to Omnisend yet.” | No email has reached Omnisend since you connected. |
| “The last email may not have reached Omnisend” (red), with the reason and “The email is still saved on the Emails page.” | Sending the latest email to Omnisend failed. When Omnisend refused it or was too busy, it didn’t arrive; after a timeout or an error on Omnisend’s side it may have arrived anyway (Teacup Quiz doesn’t send the event again then, so it can’t arrive twice). The banner goes once an email goes through again. |
| Reason | What to do |
|---|---|
| “Omnisend didn’t accept that API key. Check that it has access to contacts and events.” | The key was deleted or lacks access. Create a key with access to Contacts and Events, click Disconnect, then connect with the new key. |
| “Omnisend couldn’t be reached right now.” or “Omnisend couldn’t take it right now (…).” | Omnisend was down or busy. Nothing to change: later emails go through when Omnisend is back. |
- The quiz must be published with an email step that has a Heading.
- The shopper must leave an email: skipped steps send nothing.
- The same email with the same quiz and answers within 24 hours is sent only once, except in tests opened with Open your store or Try it on your store.
#Disconnecting, and changing plans
Click Disconnect next to Connected and confirm “Stop sending quiz emails to Omnisend?” with Disconnect. You see “Omnisend disconnected”. The section’s status, such as the last email sent, is cleared. Contacts already in Omnisend stay.
Still need help?
Chat with us: you talk to a real person, not a bot. Or email us with your store’s address (your-store.myshopify.com).