Skip to main content

Custom Webhooks

Written by Wendy

Lantern supports sending webhook payloads directly from the More Integrations tab. Under the Webhooks section, you can configure up to three webhook URLs per quiz. This feature allows you to send quiz taker information and results directly to your own system or external apps such as Make.com or Pipedream.

How to Set Up

  • Open your quiz in Lantern, then go to More Integrations → Webhooks.

  • In each input box, enter the full webhook URL of the service or system that should receive the payload (for example: https://example.com/webhook). You can add up to three different webhook URLs before clicking Save.

Image showing the More Integrations tab in Lantern's quiz editor, with Webhooks selected from the left-hand menu. The Webhooks settings panel displays three fields for entering webhook URLs and a Save button.

  • Run a test quiz submission to confirm data is being received.

  • Use tools like RequestBin, Make.com, or Pipedream to inspect and validate the payloads.

Payload Data

Each webhook payload includes:

  • Quiz Info: the quiz's URL handle (sent as quiz_id), quiz name, session ID, and the results link (full and short).

  • Customer Info: email, phone, first name and last name (each sent as N/A when not collected), plus IP address, browser, operating system, language, country, and the start and completion times.

  • Responses: Includes the customer’s quiz answers that are shared with the webhook, including choice-based and open-ended responses. Date Field responses are sent in YYYY-MM-DD format. Answers from questions set to Don't share or Don't store are not included in Custom Webhook payloads. Learn more about Sensitive Data Controls.

  • Products: recommended product IDs, variants, ranking, scores, price, currency.

  • Content blocks: the variant each content block showed and its score.

Webhooks are sent as soon as the quiz is completed. If a customer leaves their email later, through the optional email sign-up on the Results Page, that email is not sent to your webhooks. If your endpoint needs the customer's email, collect it on the Optin Page before results instead. Learn how in Collect customer emails.

Example Use Cases

  • Custom Integrations: Connect to CRMs, internal dashboards, or analytics tools.

  • Automation Platforms: Send quiz data to Make.com or Pipedream for advanced workflows.

  • Internal Systems: Capture leads directly into your own database or notification system.

Notes

  • Lantern supports a maximum of three custom webhooks per quiz.

  • Make sure your receiving endpoint can handle JSON payloads.

  • Webhook URLs apply to the live quiz as soon as you click Save; you don't need to republish. Use a test endpoint first if the quiz is already live.

  • Always test your setup before publishing the quiz live.

  • Each completion is sent once and isn't retried, so keep the endpoint available. Use the Sessions report or its CSV export to catch up on anything missed.

  • Requests aren't signed, so use a hard-to-guess URL.

  • Put your most reliable endpoint in the first box, since a first URL that can't be reached also stops the other two.

Custom webhooks send quiz data to the URLs you enter. If you want to follow what shoppers do inside the quiz, step by step, in Google Tag Manager, Google Ads, Microsoft Clarity, Northbeam, Hyros or your own scripts, see how to track quiz events with your own tools.

Custom webhooks provide merchants with a flexible way to connect Lantern quizzes to any system that accepts HTTP requests. This ensures your quiz data flows exactly where you need it, without relying solely on Zapier.

Did this answer your question?