Skip to main content
All CollectionsAnalyzing your Candu Content
Get Data Out of Candu with Webhook
Get Data Out of Candu with Webhook

Analyze & track your content views, interactions and form responses by syncing Candu data with the rest of your tech stack

Lauren Cumming avatar
Written by Lauren Cumming
Updated over a week ago

Candu webhooks allow you to automatically send data from Candu (the sender) to another application (the receiver), such as your CRM, analytics tool, or database. This allows you to do further analysis and tracking outside of Candu! 📈

Webhooks allow you to send automatically:

  • Content views: triggered whenever one of your users views embedded Candu content

  • Interaction Events: triggered whenever one of your users clicks on an interactive Candu component such as a card or button

  • Form Responses: triggered when a Candu Form is submitted.

Common use cases for webhooks

  • Analytics Tools like Mixpanel, Heap, or Amplitude - connect all of your data in one place so you can see if engagement with Candu content has any impact on product activation, adoption, or retention

  • Your CRM - if you are using Candu Forms, you may want to update contact records with new data captured

  • Slack—You may want to notify a channel when a high-intent CTA, like 'Upgrade Now,' is clicked.

Using Candu Webhooks

In your Candu account, you can access Webhooks by going to 'Settings' > 'Integrations' > 'Outgoing Webhooks.'

A screenshot showing where to set up a webhook in Candu.

There are two ways you can setup Webhooks:

  • Your engineering team will be able to set up and configure Webhooks for you. Our developer docs can be accessed here.

  • You can use a no-code tool like Make or Zapier (guide here) to connect with your existing tech stack.

Monitoring Webhooks

Once you have set up Webhooks, you can see enable/disable & edit them anytime from the Integrations screen in Candu.

How to monitor your outgoing webhooks in Candu.

You can also click 'View' to see a log of all the recent Webhook events that have occurred:

A screenshow showing recent webhook events for Zapier.

Click into any individual event to see what was sent - a response of 200 means the event was successful:

An example of a triggering event for an outgoing webhook.

You can filter the list of events to see if any errors have occurred and check the response to see what the issue is. If you want to try sending the event again, you can hit the' Resend' button.

How to filter webhook events and interactions.
Did this answer your question?