Your First Quiz

This is the fastest path from an empty admin to a working quiz on the storefront. Ten minutes if you have a small WooCommerce catalogue ready; fifteen if you want to wire a lead-capture integration.

By the end you’ll have:

• One quiz, four questions, mapped to your real products.
• A preview tab to test the flow without publishing.
• A published snapshot the storefront can read.
• A shortcode embedded on a page.

Before you start

You need an activated Dino Discover (see Installing the Plugin) and at least a handful of WooCommerce products in your catalogue. Tag a few of them so the recommendation engine has something to work with — even something as basic as summer, winter, gift is enough.

Step 1 — Create a quiz

Open Dino Discover → Quizzes in the admin and click + New quiz.

Give it a name (it’s only visible to you), then click Create. The Builder opens on the Edit tab with an empty Navigator on the left and an empty editing area on the right.

[SCREENSHOT: The empty Builder with the Navigator panel on the left and the empty editing area on the right.]

The Builder has four workflow tabs across the top: Edit, Connect, Share, and Metrics. You’ll spend most of your time on Edit.

Step 2 — Add the questions

Click + Add question in the Navigator. Pick a question type — there are seven:

Type	What it looks like on the storefront
Single-select	One option chosen from a list of radio buttons or pill choices.
Multi-select	Several options chosen from a list of checkboxes or pills.
Rating	A 1-to-N star or pip rating.
Slider	A continuous range, numeric or labelled.
Number	A free-form numeric input with optional min/max bounds.
Image choice	One option from a grid of product images.
Free text	A short text input. Useful for “Anything else we should know?”

Add a question, type the prompt, then add the answers. For each answer, the Upvotes panel on the right lets you weight that answer towards specific products or product variants.

Don’t over-weight upvotes

Each answer is one vote. The recommendation engine sums every vote a shopper accumulates and ranks products by total upvotes. You don’t need to assign large numbers — 1 for “this product fits this answer” is the common case. Save the higher weights for answers that clearly disqualify or clearly nail a product.

Repeat for three more questions. Four is a good first-quiz length — long enough to filter the catalogue meaningfully, short enough that shoppers will finish.

Step 3 — Wire the routing

Every answer has a routing pill on the right edge. By default it’s set to → Default — meaning “go to whichever question comes next in the Navigator.” You can change it to:

• → <any other question in this variant>, to branch.
• → End, to short-circuit straight to the results.

Routing is variant-scoped: each A/B variant has its own routing graph. For your first quiz, leave everything as Default.

Step 4 — Preview the flow

Click Preview in the Builder top bar. A storefront preview opens in a new browser tab. It uses a one-shot nonce that expires after 30 minutes — you can use it as much as you like inside that window.

[SCREENSHOT: The Preview tab rendering the in-progress quiz draft.]

Step through the quiz. The recommendation panel at the end shows the products your draft would surface. If the wrong products come back, head back to the Builder and adjust your upvote weights.

Preview reads your draft

Preview is the only thing on the entire site that can read an unpublished draft. It’s gated by an admin session + a 30-minute nonce, and every preview view is logged in the audit log. The live storefront route always reads the latest published snapshot — never your in-progress edits. See Drafts, Publishing & Snapshots for the contract.

Step 5 — Publish a snapshot

When the preview looks right, click Publish in the Builder top bar. Add a short note (“first published version”) and confirm.

Publishing does three things atomically:

1. Validates the draft against every quiz invariant (every answer routes somewhere; every referenced product exists; no orphaned nodes).
2. Serialises the draft into a single immutable snapshot row and stamps it with a SHA-256.
3. Flips dd_quizzes.published_snapshot_id to point at the new snapshot.

From this moment, the storefront sees the new version.

Step 6 — Embed the quiz

Open the page or post where you want the quiz to appear. Add a Shortcode block (the core Gutenberg one) and paste:

[dino_discover quiz="your-quiz-slug"]

Replace your-quiz-slug with the slug shown next to the quiz name in the admin (it’s also visible on the Share tab). Save the page.

Visit the page on the storefront. The quiz boots, the storefront bundle loads on first interaction, and the published snapshot does the rest.

[SCREENSHOT: The published quiz running on a storefront page.]

Step 7 — (Optional) wire lead capture

Open the Connect tab in the Builder. Three integrations ship today:

• Webhook — a JSON POST to any URL you control.
• Klaviyo — direct push to a Klaviyo profile and list.
• Mailchimp — direct push to a Mailchimp audience.

Add an API key, click Test, then enable the integration. Captured leads are pushed asynchronously off the request path; failures are logged and retried.

What’s next

• How Dino Discover Works — the engines and ideas under the hood, explained in plain prose.
• Drafts, Publishing & Snapshots — the editing lifecycle and the storefront’s published-only contract.
• Question Builder — the deeper reference for question types, routing, and variants.
• Embedding the Quiz — shortcode attributes, layout modes, and what’s not yet shipped in Beta.