Product update: Webhooks & Converted Outcome

Webhooks for blocked sessions 🪝

We’ve just rolled out a brand new webhook feature! This allows you to receive real-time HTTP post data for blocked sessions directly to your own app or integration tools like Zapier, Make.com or 100s of other services.

With webhooks, it’s now easier than ever to take action where click fraud is detected and share the information directly with your team, whichever systems you work on.

This feature is only available on paid plans, you can read more about the technical side of webhooks in Hitprobe here.

What can you use webhooks for?

Webhooks are great because they let systems talk to each other without you needing to do anything extra. Instead of asking for updates repeatedly, webhooks automatically send you what you need the moment something happens.

You can receive webooks into your own internal systems, or use integration platforms like like Zapier, Make.com or others to trigger actions in your other apps.

For example, you could use:

• Slack: To send a team notification when a session is blocked.
• Google Sheets: To log details of each blocked session.
• Dashboards: Plot blocked sessions on your own company dashboards.
• Email or SMS: Trigger emails or text messages when sessions are blocked. Hitprobe can already send team members an email for each blocked session but this way you can filter the events and send exactly the email or message you want.
• Anything else: Integration platforms have 1000s of apps you can integrate with, so there are so many possibilities.

How to set up webhooks

Currently, webhooks are only available on a paid Growth or Enterprise plan, so you'll want to check your plan type first.

Once you've got that housekeeping out of the way:

• Log into your Hitprobe account
• Select the site you want to add the webhook to (from the site drop down in the top left)
• Select Manage site
• Scroll down to the Webhooks section and tap Manage
• Select Add webhook

From here, you'll be able to add your webhook name (we always suggest naming it something specific i.e. "Zapier (Zendesk) webhook" incase you're using an integration tool where you'll be adding multiple webhooks), and the endpoint URL.

‍Note: You'll need to obtain the endpoint URL from the webhook destination i.e. the system you're sending the webhook to. Typically, each destination will have their own method to enabling webhooks and generating the URL.

New conversion outcome 📊

We've also released another small (but useful) change that we also want to tell you about.

Your sessions and analytics data just got an upgrade. Now, you can filter analytics by converted sessions, offering deeper insights into your campaigns and clearer performance metrics.

There's now a "Converted" outcome added to the outcome filter on both the sessions and analytics views in Hitprobe. This segments each view by only the sessions that converted.