Configure Webhooks In VWO FullStack To Fetch The Latest Campaign Settings
VWO FullStack is an Experimentation and Feature Flagging platform for mobile apps and backend services. You can test and rollout/rollback features using VWO FullStack. All of this functionality is available with zero performance impact via easy-to-use SDKs. It allows you to test the algorithms, recommendation engines, subscription flows, etc.
Whenever you create a campaign in VWO FullStack, a settings file corresponding to your campaign configurations is stored on your server. If any campaign setting(s) are modified via the VWO app, the settings file stored at your server needs to be updated. This ensures that your campaigns are always running on the latest configurations.
One way to do this is by polling frequently to ensure that you always have the latest settings file. Not only does this increase the load on your server, but there is also a possibility that you may be using the old version of the settings file if you poll it after a long time.
For example, let’s say you have set the polling to 10 minutes and the campaign gets updated when 9 minutes are still left, in this case, the settings file will not be in sync with the VWO app.
Now, we provide another way to keep the campaign settings updated via webhooks. With webhook configured VWO will notify you whenever the changes are made to the running campaigns. Therefore, you will get to know when to fetch the settings file, that is, you don’t have to worry whether or not you are using the updated settings file. It helps you to keep the most up-to-date version of the settings file.
For example, as soon as the traffic allocation percentage of a variation is changed from the VWO app, VWO will send a call to notify about the same.
Set up a Webhook
To enable the Webhooks, go to Settings > Campaign Settings, and from the Webhooks section, select Enable Webhooks. Now enter the URL where you want to receive the notifications in case the campaign settings are changed.
Advantages of Using Webhooks
- Eliminates the need to frequently fetch the latest campaign settings file which reduces the load on your servers.
- Eliminates the possibility of using the old campaign settings file if not fetched in short intervals.
To know more about Webhooks in VWO, you can refer to this Knowledge Base Article.
NOTE: Currently, we have rolled out this feature in Node.js SDK. Soon, we will be rolling this out in other SDKs as well.