Quiz Bridge

Quiz form sends market: "uk" | "us" | "de" | "fr". Worker routes to the correct Shopify store using per-market admin tokens.

Each quiz response becomes a customer metafield. Suggested namespace: quiz. Example for Brain Fog Quiz UK Variant A:

POST /admin/api/2024-04/customers.json
{
  "customer": {
    "email": "[email protected]",
    "accepts_marketing": true,
    "tags": "quiz-completed, brain-fog-uk-a, variant-a",
    "note": "Brain Fog Quiz UK A | UTM: google/cpc/brainfog-q2",
    "metafields": [
      { "namespace": "quiz", "key": "id", "type": "single_line_text_field", "value": "brain-fog-uk-a" },
      { "namespace": "quiz", "key": "variant", "type": "single_line_text_field", "value": "a" },
      { "namespace": "quiz", "key": "primary_concern", "type": "single_line_text_field", "value": "foggy mornings" },
      { "namespace": "quiz", "key": "result", "type": "single_line_text_field", "value": "focus_pro" },
      { "namespace": "quiz", "key": "completed_at", "type": "date_time", "value": "2026-05-04T..." }
    ]
  }
}

The classic mistake: a single endpoint that validates, processes, AND writes the email. If any step fails, the email is gone. The robust pattern: write the email durably first, then attempt processing. If processing fails, the data still exists and is replayable.

// Bad: email lost if any step fails
async function handleSubmit(req) {
  const data = await req.json();
  await validateEmail(data.email);          // could throw
  await sendToCRM(data);                    // could throw
  await sendConfirmationEmail(data.email);  // could throw
  return { ok: true };
}

// Good: email captured durably first
async function handleSubmit(req) {
  const data = await req.json();
  await env.KV.put(`sub:${id}`, JSON.stringify(data));  // ALWAYS happens
  // Below can fail freely; data already saved
  try { await sendToCRM(data); } catch { logForRetry(); }
  try { await sendConfirmationEmail(...); } catch {}
  return { ok: true };
}

This Worker is the foundation for an entire Brainzyme edge data plane. Same pattern works for: contact forms, sample requests, partner inquiries, abandoned-cart emails, quiz answer A/B test events, GA4 server-side measurement protocol, and (in Phase 2 of the broader bridge) triggering local Claude Code tasks. One Worker, evolving route surface. Zero per-form infrastructure.