-
Notifications
You must be signed in to change notification settings - Fork 393
Add transcend api integration docs #7217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+67
−0
Merged
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
9e58616
add transcned api integration docs
b6506bd
Apply suggestions from code review
tcgilbert eca9030
clarify setup instructions
2d859b6
pull from remote
a944e62
resolve conflicts
18eed1d
Apply suggestions from code review
tcgilbert File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
52 changes: 52 additions & 0 deletions
52
src/connections/sources/catalog/cloud-apps/transcend/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
title: Transcend Integration | ||
--- | ||
|
||
[Transcend](https://transcend.io/){:target="_blank"} is a next-generation data privacy platform that helps companies reduce risk, increase operational efficiency, enable business innovation, and build customer trust by embedding privacy directly into their business systems. | ||
|
||
Integrating with Transcend makes it easy to locate and orchestrate personal data across Segment without custom code. Transcend allows businesses to automatically manage data in compliance with privacy regulations like GDPR and CCPA, helping with tasks like locating, deleting, or opting out of data sharing. | ||
|
||
This integration is maintained by Transcend. For support, please [contact the Transcend Support team](mailto:[email protected]). | ||
|
||
## Prerequisites | ||
|
||
### Identify your Segment subdomain | ||
1. Navigate to the Segment workspace you want to integrate with Transcend. | ||
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. | ||
|
||
### Create an API Key | ||
1. Open your Segment workspace and navigate to **Settings** at the bottom of the left navigation bar. | ||
2. Under **Workspace Settings**, select **Access Management**. | ||
3. In the **User Access Management** pane, switch from **User** to **Tokens** view. | ||
4. Click **Create Token** and select the **Public API** token type. | ||
5. Assign the Public API token the following permissions: | ||
|
||
- **Privacy Permissions**: Workspace Owner level permissions for handling erasure requests. | ||
- **Data Silo Discovery Permissions**: Workspace Member level permissions with "function read-only" access for all functions. | ||
|
||
## Connect with Transcend | ||
|
||
1. In Transcend, add the Segment integration from the Transcend catalog. | ||
2. Enter your Segment subdomain and API key in the provided input fields. | ||
3. Connect the integration. | ||
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). | ||
tcgilbert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
5. If needed, enable the **Data Silo Discovery** plugin in the **Configuration** tab. | ||
|
||
## Privacy Requests | ||
tcgilbert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
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. | ||
|
||
### Note on Erasure Requests | ||
tcgilbert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
Transcend will: | ||
- Use the provided Segment `userID` to delete historical data. | ||
- 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.* | ||
- Follow up with a `DELETE_INTERNAL` regulation request and poll until completion. *For more information about Segment's regulation requests, see the [User Deletion and Suppression](/docs/privacy/user-deletion-and-suppression/) documentation.* | ||
|
||
Segment's dashboard currently does not display `DELETE_INTERNAL` regulations: they are only accessible through Segment's API. | ||
|
||
### Enrichment | ||
Transcend can identify Segment users based on a defined `userId`. Configure identifiers in Transcend to track users within Segment. | ||
|
||
### Data Mapping | ||
tcgilbert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
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. | ||
|
||
Note: If you are only using Data Mapping, the Transcend integration does not need access to employee or customer personal data. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.