# Segment

## Requirements

<table><thead><tr><th width="152.25390625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>API Key</strong></td><td>Segment Bearer Token. Used in the Authorization header. Must have permissions to use the Deletion and Suppression API.</td></tr></tbody></table>

### Integrating with Segment

To integrate Teleskope with Segment

1. Navigate to **Data Subject Rights** → **Third Party Integrations** and pick Segment
2. Enter the required fields for the integration and click **Save**.

### Supported Endpoints & Identifiers

| Endpoint | Default Identifier |
| -------- | ------------------ |
| **User** | USER\_ID           |

*Segment users are matched using your system’s internal User ID. Deletion requests require providing this identifier.*

### Parameter Defaults

Teleskope’s Segment integration enforces the following default behavior:

<table><thead><tr><th>Parameter Name</th><th width="238.3203125">Default Value</th><th>Notes</th></tr></thead><tbody><tr><td><strong>regulationType</strong></td><td>SUPPRESS_WITH_DELETE_INTERNAL</td><td>Hard-coded. Instructs Segment to delete and suppress all user data.</td></tr><tr><td><strong>subjectType</strong></td><td>USER_ID</td><td>Required. Only USER_ID is supported as the subject type.</td></tr></tbody></table>

The integration always uses these values when creating regulation jobs.