Templated Webhooks

Templated Webhooks or Incoming Webhooks is a generic integration for collecting data.

How It Works

Kevel Audience supports receiving event data in real time from incoming webhooks. This integration is available for a limited number of third party integrations, but we do integrate with new services according to client request.

A specific URL is available for each specific integration. Please make sure you adjust this URL to match your CDP domain. The URL can be used to configure the webhook integration with the third party.

• Mailgun – https://tr.cdp.domain.com/events/templated/mailgun
• Postmark – https://tr.cdp.domain.com/events/templated/postmark
• Sendinblue – https://tr.cdp.domain.com/events/templated/sendinblue
• Segment - https://webhooks.cdp.domain.com/sources/segment

Segment

Kevel Audience supports receiving events from Segment as a webhook destination.

To get started feel free to follow the Segment documentation on how to setup a webhook destination and make sure to specify and adapt the webhook endpoint https://webhooks.cdp.domain.com/sources/segment for your domain.

Supported events are listed below.

Supported Events

Kevel Audience currently supports both Segment Identify and Segment Track event types. Additionally, user attributes are derived from the event's context and traits fields.

Track

Kevel Audience uses the types defined by Semantic Event Spec to map incoming events to the CDP specification. Furthermore, the geolocation is extracted as-is from the event's context. This information is derived from the user's IP only if the geolocation is unavailable. All the events supported by Kevel Audience are documented below alongside their mapping. Events not listed are translated to a custom event type with the customType set to Segment {event name}.

Email

• Email Bounced => emailBounce
• Email Delivered => emailDelivery
• Email Link Clicked => emailClick
• Email Opened => emailView
• Unsubscribed => emailUnsubscribe

E-Commerce

• Product Added to Wishlist => addToWishlist
• Product List Filtered => productImpression
• Product List Viewed => productImpression
• Checkout Step Completed => checkoutStep
• Product Reviewed => productFeedback
• Product Clicked => productClick
• Product Viewed => productView
• Order Cancelled => orderPlace
• Order Completed => orderPlace
• Order Refunded => orderPlace
• Order Updated => orderPlace
• Products Searched => search
• Cart Viewed => cartView
• Product Added => addToCart
• Product Removed => removeFromCart
• Wishlist Product Added to Cart => addToCart

Identify

Matching User IDs is supported via the Identify event type. The list of IDs extracted are:

• email as Plaintext Email
• phone in the E.123 format and converted to Phone Number SHA256

In addition, the following user-related attributes are extracted from the event's context and traits fields.

• geo.latlong.latest
• geo.latlong.list
• geo.country.latest
• geo.country.list
• geo.city.latest
• geo.city.list
• devices.family.latest
• devices.family.list
• devices.os.latest
• devices.os.list
• devices.type.latest
• devices.type.list

Authorization / Authentication (Optional)

Segment allows defining a shared secret to validate the incoming events. To use this authentication method, start by setting up the shared secret on the Segment's webhook destination and then communicate it with your Customer Success Manager.

For more information feel free to visit the Segment documentation.