Webhooks send data from one app to another using a URL. Simple as that.
App A pushes data to a webhook. App B receives it. No fancy setup, no complicated integrations.
Use cases for webhooks
Build any marketing automation you want using your quiz data:
- Email product recommendations to quiz takers who didn’t convert
- Send discount codes based on their specific answers
- Trigger email sequences for different customer segments
- Push quiz data to your ESP, CDP, or CRM for richer customer profiles
Two types of webhooks
- Question answered – Fires when someone answers a specific question (great for real-time tracking)
- Result viewed – Fires when they reach the quiz results page (perfect for follow-up sequences)
You can set exactly which quiz, question, or answer triggers each webhook. Want to trigger only when someone selects “Budget under $500”? Easy.
Understanding the data structure:
The webhook uses your internal names from bluebarry. This keeps everything consistent but means you need to set these up properly:
- Internal question names – Change these in your funnel’s left-hand menu where all your question settings live
- Internal answer values – Update these in the “Flow” section of your quiz builder
Pro tip: Make your internal names actually make sense. “Q1” and “A1” won’t help you when you’re building automations at 2am. Use descriptive names like “budget_question” and “under_500” instead.
Webhook data overview
Here’s everything that gets sent with each webhook:
- advisor_id (your quiz funnel ID)
- session_id (unique for each quiz taker)
- question_name (for every question answered)
- answer_values (for every question answered)
- input_values (for text input questions)
- product_id (internal bluebarry product ID)
- product_name
- product_url
- product_image_url
- All product properties that were used for filtering/matching
This gives you everything you need to build automations based on exactly what your customers told you they want.