Quiz Kit helps you convert your own traffic and significantly increases conversions from your paid channels through guided commerce quizzes.

Quiz Kit

Contents

Benefits

Setup process

What data is passed

Send automated emails to Quiz Kit contacts

Use-case

Benefits

With the Quiz Kit app, you can create quizzes and embed them on your website. Thanks to the integration between Quiz Kit and Omnisend, all the answers will be sent along with the contact information to Omnisend and you'll be able to use them to segment your audience and send personalized emails.

Setup process

Firstly, create an API key. To do this click on your brand name in the top right corner -> Store settings:

Click on the 'API keys' section:

Then click the 'Create API Key' button:

Enter the name of your API key, keep default settings and click 'Save':

Then go to your Shopify admin and open the Quiz Kit app. Proceed to the Integrations tab and click the 'Connect' button under the Omnisend:

Then paste the API key in the pop-up box and click 'Save'.

That's it! The integration will be enabled. All the contacts that will fill any of your quizzes from now on will be passed to Omnisend.

Note! If you had any contacts fill out your quizzes prior to enabling the integration, they won't be synced to Omnisend with the quiz answers, but their email address should be automatically synced from Shopify.

What data is passed

Firstly, make sure to collect either email address, or phone number in your quiz. To do this go to the Settings tab when editing your quiz and click on the 'Email/SMS' section:

Then select the 'Show email/phone capture form before results' option. This way email address will be collected. If you want phone number to be collected through the Capture form, check the 'capture phone number instead of an email' box:

Collecting phone and email properties in the same quiz

If you want to collect both email and phone number, you can collect either phone, or email address through the Capture form that can be enabled under the Settings tab of your Quiz. Then add a question that will collect the other property (if you collect email through Capture form, add question to collect phone number and vice versa), enable the validation (Check the 'Enable phone number validation(E164) Example: +12125551212' checkbox to collect phone number; Check the 'Enable email validation' to collect email address) and set the 'Marketing property name' to 'phone' value to collect Phone numbers or to 'email' value to collect Email addresses. Here's an example how to collect Phone number in a Quiz question:

Mapping questions to default Omnisend properties

If you're collecting contact properties that are available as default ones in Omnisend (e.g. First Name, Address, etc.), make sure to set the name of the 'Marketing property name' as the name of the Omnisend property to map those properties to the corresponding fields in Omnisend. Here's a list of all property names in Omnisend and their parameter names:

Omnisend Property Name

Parameter name (set as Marketing property name)

Email address

email

Phone number

phone

First name

firstName

Last name

lastName

Country

country

State

state

City

city

Address

address

Postal code/zip code

postalCode

Gender

gender (Can be: m - male, f - female)

Birthdate

birthdate (should be collected in YYYY-MM-DD format)

When new email address and/or phone number is collected through the capture form in your quiz, contact is passed to Omnisend along with these properties:

  • email address (subscribed status);

  • phone (subscribed status);

  • first name (if mapped correctly, as explained here);

  • last name (if mapped correctly, as explained here);

  • Country (if mapped correctly, as explained here);

  • State (if mapped correctly, as explained here);

  • City (if mapped correctly, as explained here);

  • Address (if mapped correctly, as explained here);

  • Postal/zip code (if mapped correctly, as explained here);

  • Gender (if mapped correctly, as explained here);

  • Birthdate (if mapped correctly, as explained here);

  • QuizCompletionDate - custom property with the date when customer has filled out the quiz;

  • Result_subtitle - you set the result subtitle yourself, but since customers will receive different results, they'll see different subtitles;

  • Result_title - you set the result subtitle yourself, but since customers will receive different results, they'll see different titles;

  • All the question headings will be passed as custom properties along with the value customer has chosen/provided (e.g. What is your skin type will be passed as what_is_your_skin_type: option customer has chosen. If multiple options are selected by your customer for one question, all of them will be listed like this: option1, option2, option3 under one custom property) unless you set the Question Marketing Property Name to one of the default Omnisend properties;

  • id - Quiz Kit assigns unique contactID to each collected contact;

  • quizName - the name of the quiz contact has filled out;

  • tags: source: QuizKit, quiz: unique_quiz_code (it can be found on the Publish step of the Quiz setup).

Send automated emails to Quiz Kit contacts

To send automated emails to contacts passed by the Quiz Kit, you'll need to create a segment based on 'source: QuizKit' tag. If you want to send different emails to customers coming from different Quizzes, you should use 'quiz: unique_quiz_code' tag.

Once the segment is created, create an automation workflow based on Contact enters a segment trigger, and select your segment as trigger filter.

Use-case

Since all of the customer answers are passed to Omisend as custom properties, you can segment your audience based on those answers. For example, our test Quiz collects data about customers' skin type. So, here's an example segment based on one of the answers:

Later, we can use this segment to send these customers product recommendations for their skin type.

Feel free to experiment with segmentation. You can combine the quiz answers with each other and with other Omnisend filters too.

Did this answer your question?