RudderStack lets you add any source that supports a webhook and use it to send events to your preferred destinations.
You can configure webhooks as sources only for the platforms that support them.
RudderStack recommends using the webhook source only if your input data is not in the standard RudderStack event format. In such cases, you can write a transformation to convert the data into the standard event format. To ingest events with the standard RudderStack event format, it is recommended to use an HTTP source instead.
Getting started
Follow these steps to set up your webhook source in the RudderStack dashboard:
In this example, events are ingested from Mailchimp into RudderStack by configuring a webhook.
Go to your RudderStack dashboard and click Add Source. From the list of Event Streams sources, select Webhook.
Assign a name to your source and click Continue.
Your webhook source is now created. Note the Webhook URL containing the Write key as a query parameter:
For this example, Google Analytics is configured as a destination.
Next, add the webhook URL to your source platform - in this case, Mailchimp.
You can configure webhooks as sources only for the platforms that support them.
The following image shows the webhook URL added in Mailchimp:
Add and test your webhook URL. You can use the Live Events functionality to view the events tracked in real time.
When the users perform any action configured in the source, the source platform will automatically send the generated events to the webhook URL.
In this example, Mailchimp sends the updates under Trigger on Events (seen in the above image) as the user events to the webhook URL with the content type application/x-www-form-urlencoded.
The content type can vary in case of the other webhook sources.
RudderStack then takes the data, creates the payload, and sends it to the destinations connected to the webhook source (Google Analytics, in this case).
You must also add the appropriate Transformation to transform the payload into a destination-specific format before sending it to the destination. Refer to the Payload creation and transformation section for more details.
Payload creation and transformation
This section details how RudderStack receives the data from the webhook source platform and creates the resulting payload.
Continuing with our Mailchimp example, suppose a customer subscribes to Mailchimp. Mailchimp then sends the following data to RudderStack:
Transform this payload as per the event format accepted by destination. To do this, use RudderStack’s Transformation feature. A sample transformation is as shown below:
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.