Webhooks (Cloud Destinations)

  • Cloud
  • Destinations

MetaRouter makes it easy to send your data to webhooks from server-side, mobile, and client-side. Once you follow the steps below, your data will be routed through our platform and pushed to webhooks in the appropriate format.

What are webhooks and how do they work?

A webhook is a custom, user-defined callback function fired in response to an HTTP POST request. It's a useful tool for apps that want to execute code in response to an event occurrence. For example, you might want to post a message to a Slack channel every time a user completes a custom "Sign Up" track event in your app.

It's an efficient way to provide realtime updates.

A webhook submits realtime user data, ties customer information to a dedicate API, records mobile and e-commerce data, and maps events to custom features within FB ads and Google Analytics.

Get instant, realtime notifications without having to manually poll your data.

Why send data to Webhooks using MetaRouter?

If you're already setup with MetaRouter, you can start using webhooks. Any data you collect with MetaRouter can be sent to up to 5 webhook destinations.

Read below to kickoff your integration and start gaining insights.

Getting started with Webhooks and MetaRouter

Add your domain name into the webhook connector on your MetaRouter dashboard and give your new connection a unique name.

Click Save to activate your pipeline.

Sending to multiple webhooks

For each webhook you'd like to enable, enter the full URL where MetaRouter should send data. You'll be able to provide up to 5 webhooks.

© 2020 MetaRouter

Disclaimer: MetaRouter Cloud leverages code from several of Segment's fabulous library of open-source tools, including their source SDKs, destinations, and core Analytics.js library. As some of the core configurations outlined in our docs are largely identical to Segment's, we often re-purpose, and in some cases copy, directly from Segment's docs. In the cases where we have forked Segment's tools, we acknowledge and attribute all credit to Segment for their creation and subsequent documentation.