Webhooks are commonly used in conjunction with custom development. They are an easy way to have your product or application receive a signal from Lytics when we notice a change in a user's state (enter segment, leave segment). This can be very valuable for triggering changes in multiple systems without having to 'ask' our platform for an update. Instead we 'tell' your system when something has changed, so that you can take action. If an audience definition needs to be changed and it has an active webhook we recommend stopping the webhook workflow and recreating it after making the changes.
If you use webhooks to export an audience that relies on a time-based trigger, for example, users who have been modified within a window of time, it is important that the window be at least 30 minutes. Smaller windows may not be reliable due to the pipeline necessary for checking segment membership at a specific time.
Combining Lytics and webhooks with lightweight webapp is an incredible way to utilize a unified user profile in thousands of different custom experiences across any channel, standard or custom. Send a recommended product to a specific user, at the right time of day for them, cross channel.
Check out Mobile Messaging with Lytics Webhooks and Serverless Functions to walk through a real-world example using a Lytics webhook.
See our Subscription API documentation for more information about utilizing webhooks with Lytics.
Visit webhooks.org to learn more.
For development and testing we have found webhook.site a valuable way to see the type of data that Lytics provides when a webhook is triggered.