Leanplum's user guides and developer documentation.

Leanplum Documentation

Leanplum's user guides, SDK setup, API docs, and more resources are here to help you get the most out of A/B testing, Campaigns, Messaging, and Analytics.

A webhook is a simple notification that is sent as an HTTPS POST request after something occurs. You can use webhooks to send real-time Leanplum user data to another server.

For example, you could send a webhook to confirm when a user reads a message. Or, you could send a webhook that triggers a third-party service to do something, like send an email, Slack someone, or store something in a database.

Send a webhook

To send a webhook, you either need to create a new campaign or add a new action to an existing one. For more, see Create a campaign.

Set and customize the URL. This is where Leanplum will send the webhook data. The URL can be common to all users in the audience (fixed), or it can include personalized information about each user, using user attributes and/or event parameters. For more, see Personalize a message.

Set the content type. The content type is an HTTP header setting used when sending the actual POST request. You can choose between application/json and application/x-www-form-urlencoded.

🚧

Be sure to set this to the correct content type for the service or API you’re delivering the webhook to.

Send data with the webhook. You can send custom key-value pairs within the message that can be utilized by the server that receives the webhook. The values are set directly in Leanplum, and they can include personalized values. For more, see Message templating {{.

Authentication

Basic authentication can be used by appending the username and password to the url in the following format: https://username:[email protected] .

Sub-Delivery

Determines when your webhook will send. This is where you set your Action delivery.

See Sub-Delivery for more.

Updated 9 months ago


Webhook


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.