Sabil Destination
Sabil helps prevent subscription abuse and account sharing with the highest accuracy and lowest effort while keeping customer satisfaction high.
Sabil (Actions) provides the following benefit:
- Faster integration. Using the Segment integration is the fastest way to integrate Sabil to collect account sharing intelligence data.
- From the Segment web app, click Catalog, then click Destinations.
- Search for Sabil (Actions) and select it.
- Click Configure Sabil.
- Select an existing Source to connect to Sabil (Actions).
- Go to your Sabil dashboard and copy the
Client IDof your production key. - Paste the client id in the Client ID field in the Segment UI.
Your project API client ID. You can find it in your Sabil dashboard
Build your own Mappings. Combine supported triggers with the following Sabil-supported actions:
Mapping limits per destination
Individual destination instances support a maximum of 5 mappings.
Attach a device to the user.
Attach is a Web action. The default Trigger is type = "identify"
The ID of the user
Optional
A key-value object that will be stored alongside the user, device and access records. This will be available to in any webhooks or API calls. Useful if you want to remote logout a device or invalidate a session from the backend via webhook.
If a user exceeds the configured limit on your dashboard, you can enable the blocking dialog from the Sabil dashboard settings. This integration does not support callbacks, and does not call on_current_device_logout. To log devices out in real-time, implement webhooks on your server, as described in Handle webhook events in Sabil's documentation.