Skip to content

Commit c14ac43

Browse files
Merge pull request #4754 from segmentio/develop
one-off release
2 parents f503981 + c0b5fe7 commit c14ac43

File tree

3 files changed

+14
-2
lines changed

3 files changed

+14
-2
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This source is maintained by OneTrust. For any issues with the source, [contact
1414

1515
1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog) click **Add Source**.
1616

17-
2. Search for “OneTrust” in the Sources Catalog, select MoEOneTrustngage, and click **Add Source**.
17+
2. Search for “OneTrust” in the Sources Catalog, select OneTrust, and click **Add Source**.
1818

1919
3. On the next screen, give the Source **a nickname** configure any other settings.
2020
- The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (like `OneTrust_Prod`, `OneTrust_Staging`, or `OneTrust_Dev`).

src/privacy/portal.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,8 @@ This is where you can create your very own matchers to tell Segment what to scan
186186
for in your workspace. You can use this feature to detect properties that are
187187
unique to your company or region, or that aren't already handled by the default
188188
matchers above. You can have up to 100 custom matchers per workspace. Custom
189-
Matchers detect data in your Web, Mobile, Server, and Cloud Event Sources, and
189+
Matchers detect data in your Web, Mobile, Server, and Cloud Event Sources for
190+
fields under `contexts`, `traits` and `properties` objects, and
190191
the data they detect appears in the Inbox.
191192

192193
For example, if you have a restricted data point at your company called "SIN"

src/protocols/tracking-plan/create.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,17 @@ To create a copy of an existing Tracking Plan:
3535
2. On the row of the Tracking Plan you want to copy, open the contextual menu(...), and select Duplicate Tracking Plan.
3636
3. Enter a name for the new Tracking Plan instance, and click Duplicate.
3737

38+
39+
## Download a Tracking Plan
40+
41+
To download a Tracking Plan:
42+
43+
1. Click **Protocols** in the left navigation bar.
44+
2. On the row of the Tracking Plan you want to download, open the contextual menu(...), and select **Download Tracking Plan**.
45+
3. A toast pops up on the top of the page, with the message _"Your file is processing. When your file is ready it will be available to download from the Download History page."_
46+
4. Open the Download History page by clicking the link in the toast or clicking the **Download History** tab in the top navigation bar.
47+
5. Once the file status column indicates that the download was successful, click the link in the File column to download your CSV to your computer. If the file status column shows the download has failed, return to the Tracking Plan Overview page or the Tracking Plan page and try the download again.<br/> The Tracking Plan CSV name has the following format:<br/>`workspaceSlug-trackingPlanName--yyyy-mm-dd--hh-mm-utc`
48+
3849
### Tracking Plan Columns
3950
The Tracking Plan editor is organized as a spreadsheet to help you add new events and properties, and edit the relevant fields for each. Like a spreadsheet, you can navigate across cells in a single event with your arrow keys and press enter to edit a cell.
4051

0 commit comments

Comments
 (0)