---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-sabil#article
headline: Sabil Destination
url: https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-sabil
inLanguage: en
dateModified: 2026-06-09T02:36:11.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Sabil Destination

[Sabil](https://sabil.io?ref=segment) helps prevent subscription abuse and account sharing with the highest accuracy and lowest effort while keeping customer satisfaction high.

## Benefits of Sabil (Actions)

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.

## Getting started

1. From the Segment web app, click **Catalog**, then click **Destinations**.
2. Search for *Sabil (Actions)* and select it.
3. Click **Configure Sabil**.
4. Select an existing Source to connect to Sabil (Actions).
5. Go to your [Sabil dashboard](https://dashboard.sabil.io/api_keys) and copy the `Client ID` of your **production** key.
6. Paste the client id in the **Client ID** field in the Segment UI.

## Destination Settings

| Field     | Description                                                                                                   | Required | Type   |
| --------- | ------------------------------------------------------------------------------------------------------------- | -------- | ------ |
| Client ID | Your project API client ID. You can find it in your Sabil \[dashboard]\(https://dashboard.sabil.io/api\_keys) | Yes      | string |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Sabil-supported actions:

> \[!NOTE]
>
> Individual destination instances support a maximum of 5 mappings.

* [Attach](#attach)

### Attach

Attach a device to the user.

Attach is a **Web** action. The default Trigger is `type = "identify"`

| Field    | Description                                                                                                                                                                                                                                      | Required | Type   |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ------ |
| User ID  | The ID of the user                                                                                                                                                                                                                               | Yes      | STRING |
| Metadata | 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. | No       | OBJECT |

### Block over-usage

If a user exceeds the configured limit on your dashboard, you can enable the blocking dialog from the Sabil dashboard [settings](https://dashboard.sabil.io/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](https://docs.sabil.io/docs/Advanced/Handle%20webhook%20events) in Sabil's documentation.