Overview
Put customer feedback to work across your stack the moment it's submitted. Surveys webhooks send real-time survey responses to external systems such as email platforms (ESPs), help desks, CDPs or analytics platforms, even when they don't have a direct integration with Okendo.
Before you begin
đ Webhooks are available on the Advanced plan and above. View pricing.
New to webhooks? Read Getting started with webhooks and Okendo first.
Use cases for Surveys webhooks
Here are a few examples of what merchants use webhooks for:
Send survey response data to your ESP to create segments or trigger flows based on how customers respond.
Send survey data to your analytics platform or data warehouse for deeper customer insights - e.g. attribution data from surveys alongside data from other marketing channels.
Automatically create support tickets for feedback or specific issues raised in surveys.
Receive notifications when a survey response is submitted.
Events that can be subscribed to
You can configure webhooks to notify your system when a survey response is:
Created - The most common use case whenever a survey response is submitted.
Updated - When an existing response is updated with information - e.g. when an email is added to a response on the outro page to receive a coupon.
Deleted - When a response is deleted from the database - typically initiated by Okendo for specific cases.
Data included in each event
Survey info
Survey name
Survey ID
Survey response ID
Date of response
Channel
Channel description
Customer info
Email
Customer ID
Order ID
Marketing opt-in status
Answered questions
Reward or incentive offered (if applicable)
How to subscribe to Surveys webhooks
Webhook setup requires some developer support. Your team will need to:
Set up an endpoint to receive survey data in your desired platform or use a middleware such as Zapier.
Subscribe to webhook events through the Okendo API using the likes of Postman or through code.
Test and verify that the events are being sent and received correctly.
Refer to our technical documentation for the full setup details:
