Connect Quizproof to Zapier

The Quizproof Zapier app starts a Zap when a shopper finishes a quiz or opts in, so you can add them to Mailchimp, a Google Sheet, HubSpot or thousands of other apps. It works on Zapier's free plan: a Zap with a Quizproof trigger and one action is a two-step Zap, and you don't need "Webhooks by Zapier". It's available on every Quizproof plan.

Connect#

1. Go to Settings › Integrations › Zapier, name a key (for example "Mailchimp Zap") and select Create key.

2. Copy the key (qpk_…). It's shown once: Quizproof keeps only a fingerprint of it.

3. Select Open Quizproof in Zapier, make a Zap and choose a Quizproof trigger.

4. When Zapier asks you to sign in to Quizproof, paste the key. Zapier names the connection after your store, for example "My Store (my-store.myshopify.com)".

5. Choose the trigger's options, test it, add your action and turn the Zap on. The Zap then shows under Zaps on the Zapier page in Quizproof.

A store can have 5 active keys. One key can serve many Zaps; create one per person or tool if you want to revoke them separately.

The triggers#

Quiz Completed starts the Zap when a shopper finishes a quiz and sees their recommended products. It carries the quiz and the products. No shopper details and no answers. Option: Quiz (leave empty for every quiz).

Shopper Opted In starts the Zap when a shopper who finished a quiz leaves their email and agrees to be contacted. It adds the shopper's email, phone, Shopify customer id, consents and saved answers. Options: Quiz (leave empty for every quiz) and Audience (required, below).

Audience: who starts the Zap#

A shopper can agree to email marketing, to text messages, or only to getting their results by email. Choose who starts this Zap:

• Agreed to email marketing: use this for an email marketing list (Mailchimp, Klaviyo, ActiveCampaign …).

• Agreed to SMS marketing: use this for a text message list.

• Any consent, including results email only: every shopper who opted in, for example to save them in a CRM. Don't add these shoppers to a marketing list: some only asked for their results.

There's no default, so a shopper is never added to a marketing list they didn't agree to. Quizproof checks the choice when the shopper opts in and again right before it sends: if the shopper withdrew that consent meanwhile, the Zap doesn't start.

Only a key that can receive shopper contacts can use Shopper Opted In. When Settings › Privacy lets only the store owner see respondent data, keys created by other staff can't, and their Shopper Opted In Zaps stop (the Zapier page shows them as off). Ask the owner to create the key.

The fields#

Both triggers:

• Event ID (id): unique per event. Map it into your action to skip a repeat (see below).

• Created At: when the event happened (ISO 8601, UTC).

• Shop Domain, Quiz Name, Quiz Handle, Quiz Version.

• Session ID: the quiz session.

• Market Country: the shopper's market (two-letter code), or empty.

• Results Link: a link to the shopper's results page (valid 7 days), or empty.

• Product Count and Product Titles (comma-separated).

• First/Second/Third Product Title, URL, Image URL, Price, Currency, Available, Product ID, Variant ID: empty when the quiz recommended fewer products. Price is in the shopper's market currency, empty when Quizproof doesn't know it.

• Products: every recommended product as line items, for actions that take a list.

Shopper Opted In also has:

• Email, Phone (empty when not given), Shopify Customer ID (empty until Shopify saved the customer).

• Agreed to Email Marketing, Agreed to SMS Marketing, Agreed to Results Email: true or false.

• Answers (Text): one line per saved answer, "Question: answer". Answers: the same as line items. Only answers of questions set to save to the customer are included.

When you test the trigger, Zapier shows up to 3 recent events from your store. Shopper Opted In shows real shoppers only to a key that can receive shopper contacts (each such test is logged under Settings › Privacy); otherwise, and when there are none yet, it shows one made-up example.

Duplicates and order#

An event can reach Zapier more than once (for example when Zapier answered slowly and Quizproof sent it again), and events can arrive out of order. Prefer actions that update or create ("Add/Update Subscriber", "Create or Update Contact") over ones that always create, and map Event ID where the action can use it.

When something goes wrong#

• Quizproof retries a failed delivery for about 14 hours. When Zapier asks it to slow down, it waits as long as Zapier says.

• When a Zap is turned off or deleted, Zapier tells Quizproof and the Zap disappears from the Zapier page.

• The Zapier page lists each Zap's last 50 deliveries. Zapier's own Zap history shows what the action did.

Revoke a key#

Revoke on the Zapier page turns a key off at once: Zaps using it stop receiving data, and deliveries waiting to be sent are cancelled. In Zapier the connection then fails with "This key was revoked in Quizproof"; reconnect it with a new key.

Uninstalling Quizproof#

Uninstalling revokes every key and stops every Zap. After a reinstall, create a new key and reconnect your Zaps.

Privacy#

Shopper Opted In sends the shopper's personal data to your Zapier account and the apps your Zaps use; what happens to it there is up to you (you're the controller). When a customer asks to be forgotten, Quizproof cancels deliveries still waiting, but can't recall ones already made: delete the data in those apps too.