Skip to content

Commit 18eed1d

Browse files
Apply suggestions from code review
Co-authored-by: forstisabella <[email protected]>
1 parent a944e62 commit 18eed1d

File tree

1 file changed

+5
-5
lines changed
  • src/connections/sources/catalog/cloud-apps/transcend

1 file changed

+5
-5
lines changed

src/connections/sources/catalog/cloud-apps/transcend/index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This integration is maintained by Transcend. For support, please [contact the Tr
1414
1. Navigate to the Segment workspace you want to integrate with Transcend.
1515
3. Find the unique workspace identifier, or subdomain, in your URL. For example, if your workspace URL is `https://app.segment.com/your-workspace-subdomain/home`, then `your-workspace-subdomain` is your subdomain. Remember this value or copy it to a safe place, as you will need it to set up your Transcend integration.
1616

17-
### Create an API Key
17+
### Create an API key
1818
1. Open your Segment workspace and navigate to **Settings** at the bottom of the left navigation bar.
1919
2. Under **Workspace Settings**, select **Access Management**.
2020
3. In the **User Access Management** pane, switch from **User** to **Tokens** view.
@@ -29,13 +29,13 @@ This integration is maintained by Transcend. For support, please [contact the Tr
2929
1. In Transcend, add the Segment integration from the Transcend catalog.
3030
2. Enter your Segment subdomain and API key in the provided input fields.
3131
3. Connect the integration.
32-
4. Configure data points if using the integration for privacy requests (e.g., erasure and tracking opt-out for Segment data are enabled by default).
32+
4. Configure data points if using the integration for privacy requests. Erasure and tracking opt-out for Segment data are enabled by default.
3333
5. If needed, enable the **Data Silo Discovery** plugin in the **Configuration** tab.
3434

35-
## Privacy Requests
35+
## Privacy requests
3636
Transcend facilitates privacy requests using Segment's API, including erasure and tracking opt-out for Segment users. Note that this integration only manages requests within Segment. To delete data from upstream systems, you should connect those systems directly to Transcend.
3737

38-
### Note on Erasure Requests
38+
### Erasure requests
3939
Transcend will:
4040
- Use the provided Segment `userID` to delete historical data.
4141
- Send a `SUPPRESS_ONLY` regulation request to Segment. *For more information about Segment's regulation requests, see the [User Deletion and Suppression](/docs/privacy/user-deletion-and-suppression/) documentation.*
@@ -46,7 +46,7 @@ Segment's dashboard currently does not display `DELETE_INTERNAL` regulations: th
4646
### Enrichment
4747
Transcend can identify Segment users based on a defined `userId`. Configure identifiers in Transcend to track users within Segment.
4848

49-
### Data Mapping
49+
### Data mapping
5050
The Segment integration includes a **Data Silo Discovery** plugin to identify additional services your company uses. This helps build a comprehensive data map. Enabling silo discovery allows Transcend to scan Segment’s sources and destinations, identifying app names and domains.
5151

5252
Note: If you are only using Data Mapping, the Transcend integration does not need access to employee or customer personal data.

0 commit comments

Comments
 (0)