Merge pull request #4346 from segmentio/DOC-654-IG

High Cardinality Source Schema Export (Public Beta)

Author: forstisabella

src/connections/destination-data-control.md

@@ -31,51 +31,73 @@ Destination flags are **case sensitive** and match [the Destination's name in th
 
 If you're on Segment's Business plan, you can filter track calls right from the Segment UI on your Source Schema page by clicking on the field in the "Integrations" column and then adjusting the toggle for each tool. Segment recommends using the UI if possible since it's a much simpler way of managing your filters and can be updated with no code changes on your side.
 
-![](images/destination-control.png)
+![A screenshot of the source schema page. The user is hovered over the integrations column, and a popup showing the three integrations connected to the event appears.](images/destination-control.png)
 
 ## How do I block or disable specific events and properties from being sent to all Destinations?
 
 If you no longer want to track an event, you can either remove it from your code or, if you're on the Business plan, you can block track calls right from the Segment UI on your Source Schema page by adjusting the toggle for each event.
 
-![](/docs/protocols/images/event-filters.png)
+![A screenshot of the source schema page. The toggles in the integrations column are all enabled.](/docs/protocols/images/event-filters.png)
 
 Once you block an event in Segment, Segment stops forwarding it to all of your Destinations, including your warehouses. You can remove it from your code at your leisure. In addition to blocking track calls, Business plan customers can block all Page and Screen calls, as well as Identify traits and Group properties. 
 
 ## Export your Source Schema
 
-Segment allows you to download your Source Schema as a CSV file, maximizing portability and access to event data. You can download a copy of your schema by visiting the Source Schema page. Track, Identify, and Group events support Source Schema export.
+Segment allows users with Source Read-only permissions to download Source Schemas as a CSV file, maximizing portability and access to event data. You can download a copy of your schema by visiting the Source Schema page.
 
-![](images/export-source-schema.png)
+> success ""
+> You can export Track, Identify, and Group Source Schemas.
 
-You can choose to include properties with the Track events in the modal.
+### Download a CSV
+You can only download one Source Schema CSV schema type (Track, Identify, or Group) per source at the same time.
 
-![](images/export-source-schema-including-props.png)
+To download a Source Schema CSV file: 
+1. Sign into Segment and select a source.
+2. Click the **Schema** tab in the source header.
+3. On the Source Schema page, select a schema type (Track, Identify, or Group) and a timeframe (7 days or 30 days.)
+4. Click the **Download CSV** button. <br/> 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."* 
+5. Open the Download History page by clicking the link in the toast or following the instructions in the [view download history](#view-download-history) section.
+6. Once the file status column indicates that the download was successful, click the **Download CSV** link to download your CSV to your computer. If the file status column shows that the download has failed, return to the Source Schema page and try the download again.<br/> The Source Schema CSV name has the following format:<br/>`workspaceSlug-sourceSlug-schemaType--yyyy-mm-dd--hh-mm-utc`
 
-CSV files generate based on the current view of your Source Schema. Any search parameters or filters you apply to the current Source Schema view also apply to the CSV.
+> note "All events and properties are now included in the CSV file"
+> When you export a Source Schema, all events and properties are included in the CSV file regardless of the filters or search parameters currently applied to the Source Schema view. 
 
+### View download history
+
+You can view the last 14 days' worth of Source Schema exports on the Download History page. 
+
+To access the Download History page:
+1. Sign into Segment and select a source.
+2. Click the **Schema** tab in the source header.
+3. Click the **View Download History** link.
+
+### Track event CSV format
 The Track event CSV file contains the following columns:
 - Event Name
-- Property Name (if properties are included in the export dialog)
-- Last Seen (UTC)
-  - If greater than 30 days, the value is "more than 30 days ago"
-- Allowed Count
-- Blocked Count
-- Total Count
+- Last Seen At (UTC)
+  - If greater than your selected timeframe (7 days or 30 days,) the value is "more than 7 days ago" or "more than 30 days ago"
+- Property Name
+- Allowed
+- Blocked
+- Total
 - Planned (available for Protocols customers with a connected Tracking Plan)
   - Values are "planned" or "unplanned"
 
-The Identify & Group CSV file contains the following columns:
+> note "Labels in your exported CSV"
+> If you use [labels](/docs/protocols/tracking-plan/create/#add-a-label), they appear as columns in your CSV. The column headers are keys, and the column data contains values.
+
+### Identity and Group event CSV format
+The Identify and Group CSV files contain the following columns:
 - Trait Name
-- Last Seen (UTC)
-- Allowed Count
-- Blocked Count
-- Total Count
+- Last Seen At (UTC)
+  - If greater than your selected timeframe (7 days or 30 days,) the value is "more than 7 days ago" or "more than 30 days ago"
+- Allowed
+- Blocked
+- Total
 - Planned (available for Protocols customers with a connected Tracking Plan)
   - Values are "planned" or "unplanned"
 
 > info ""
-> The export schema doesn't include actual values (for example, personal data) for the events, properties, and traits you are tracking for a specific source.
-
-
+> The exported schema doesn't include actual values (for example, personal data) for the events, properties, and traits you are tracking for a specific source.
 
 See the [Segment Schema Limits](/docs/connections/schema-unique-limits/) for more information on how to manage the Source Schema.