alt-text

Author: forstisabella

src/partners/conceptual-model.md

@@ -30,7 +30,7 @@ Apps represent a unit of functionality that Segment users can add to their works
 - Within Destinations, we have Streaming Destinations, Batch Destinations, and Warehouse Destinations, all of which receive different data, using different processes, at different intervals and with varying degrees of control and flexibility.
 - On the Sources side, integrations are categorized based on whether they send Objects or Events, whether they are "Push" or "Pull," and whether they are built and hosted by Segment or by Partners.
 
-![](images/product-model.svg)
+![Diagram showing how events are processed in Segment.](images/product-model.svg)
 
 These smaller pieces that support the source and destination model are called "Components".
 

src/partners/streams.md

@@ -18,7 +18,7 @@ To complete the source set up flow, the customer will need to input the Segment
 
 Customers can find their write key in the source settings and regenerate it as needed.
 
-![](images/s_8E933880F61B29168308B8A8203AE878319289A26E8E2054D0824C7A53E43DD4_1479162638952_file.png)
+![Screenshot of a Source's settings page, with the write key present.](images/s_8E933880F61B29168308B8A8203AE878319289A26E8E2054D0824C7A53E43DD4_1479162638952_file.png)
 
 > warning ""
 > Segment working on an OAuth solution to reduce friction for customers. Partner Streams submitted through the developer center *will* be required to support this OAuth as it comes available.

src/partners/subscriptions/build-functions.md

@@ -27,7 +27,7 @@ Review the steps outlined in the [Developer Center Overview](/docs/partners). Th
 
 Begin by selecting the _Subscription_ card in your Developer Center UI after creating an App and selecting _I want Segment to run functions I write_. Next, you will see the code editor where you can take full control of your Subscriptions's logic. Segment provides boilerplate functions that make it simple to send data to your API Endpoint. You can delete the example code and implement your own functions.
 
-![](/docs/partners/images/developer_center_customcode_page.png)
+![Screenshot of the Build tab in the Developer Center.](/docs/partners/images/developer_center_customcode_page.png)
 
 For every event you send to Segment, Segment invokes a function you provide for the event type. So you must define functions named after every type in the [Segment Spec](/docs/connections/spec/) that you support:
 
@@ -186,7 +186,7 @@ When testing your integration, proceed through two separate flows:
 
 Test your code directly from the Developer Center UI. Use the `Send Test Event` button and review the test event to make sure your function works as expected.
 
-![](/docs/partners/images/developer_center_customcode_test.png)
+![Screenshot of the Build tab in the Developer Center, with a View Output button selected in the test event panel.](/docs/partners/images/developer_center_customcode_test.png)
 
 In the debugger panel, check the two outputs. The **Callback Return** and the **Log Output**.
 
@@ -195,7 +195,7 @@ In the debugger panel, check the two outputs. The **Callback Return** and the **
 
 When your code is working with one event you can test it with a suite of more Segment events. Click `Save and Next: Test`, fill in an `API Key` and click `Test`. You will see the results of additional types of Segment data.
 
-![](/docs/partners/images/developer_center_test_suite.png)
+![Screenshot of the Test tab in the Developer Center, which shows the results for each Segment Spec method.](/docs/partners/images/developer_center_test_suite.png)
 
 ### The User Flow
 
@@ -211,7 +211,7 @@ Now you can use the JavaScript SDK in a browser to generate real analytics event
 
 Finally you should verify the data in your service.
 
-![](/docs/partners/images/test-destination.gif)
+![Animation showing someone configure a custom app, enable the app, and test three events.](/docs/partners/images/test-destination.gif)
 
 
 ## Handling deletions

src/partners/subscriptions/build-webhook.md

@@ -51,7 +51,7 @@ See the [headers](#headers) section for more details.
 #### Custom Settings
 All subscriptions have an API key setting by default, which Segment will send in the Authorization Header. To add more custom settings, go to the `Settings Builder` page under `App Info`.
 
-![](/docs/partners/images/developer_center_settings_builder.png)
+![Screenshot of the Settings Builder page.](/docs/partners/images/developer_center_settings_builder.png)
 
 Any custom settings you add will be sent in the custom header `X-Segment-Settings` (See the [headers](#headers) section for more details.)
 
@@ -159,7 +159,7 @@ When testing your integration, proceed through two separate flows:
 
 Test your code directly from the Developer Center UI. Use the `Send Test Event` button and review the test event to make sure your function works as expected.
 
-![](/docs/partners/images/developer_center_customcode_test.png)
+![Screenshot of the Build tab in the Developer Center, with a View Output button selected in the test event panel.](/docs/partners/images/developer_center_customcode_test.png)
 
 In the debugger panel, check the two outputs. The **Callback Return** and the **Log Output**.
 
@@ -168,7 +168,7 @@ In the debugger panel, check the two outputs. The **Callback Return** and the **
 
 When your code is working with one event you can test it with a suite of more Segment events. Click `Save and Next: Test`, fill in an `API Key` and click `Test`. You will see the results of additional types of Segment data.
 
-![](/docs/partners/images/developer_center_test_suite.png)
+![Screenshot of the Test tab in the Developer Center, which shows the results for each Segment Spec method.](/docs/partners/images/developer_center_test_suite.png)
 
 ### The User Flow
 
@@ -184,7 +184,7 @@ Now you can use the JavaScript SDK in a browser to generate real analytics event
 
 Finally you should verify the data in your service.
 
-![](/docs/partners/images/test-destination.gif)
+![Animation showing someone configure a custom app, enable the app, and test three events.](/docs/partners/images/test-destination.gif)
 
 ## Next Steps
 

src/privacy/data-controls.md

@@ -35,7 +35,7 @@ other tools you might prefer for events and notifications. We recommend setting
 up alerts to help you ensure your Inventory is always up to date.
 
 
-![](images/privacy-alerts.png)
+![Screenshot of the Privacy Portal settings page in the Segment app.](images/privacy-alerts.png)
 
 
 **To set up a Slack Alert:**

src/privacy/portal.md

@@ -35,7 +35,7 @@ You can click a row in the Inbox to learn more about a field and where it was co
 - an example code snippet containing a payload that the field appears in
 
 
-![](images/privacy-inbox.gif)
+![Animation of a user selecting a row in the Privacy Portal and clicking on the expanded view.](images/privacy-inbox.gif)
 
 
 To streamline the classification process, Segment pre-classifies the data in the
@@ -56,7 +56,7 @@ dropdown menu to change. For example, you might manually change a field that
 does not contain personal information in your implementation from a "Yellow"
 classification to "Green."
 
-![](images/privacy-inbox-change-color.gif)
+![Animation of a user selecting the color dropdown menu and changing the phone field from a Yellow field to a Green field.](images/privacy-inbox-change-color.gif)
 
 
 When you're satisfied that the fields have been classified appropriately, you
@@ -86,7 +86,7 @@ The Inventory is a central repository of all of the properties _you_ classified
 
 Once you've classified the fields as Red, Yellow, and Green in the Inbox, the classified fields appear in the Inventory. You can use the filter at the top left to filter down to specific categories of data (for example, Red data, data from a production environment, data from specific sources).
 
-![](images/privacy-inventory-filtering.gif)
+![Animation of a user filtering the data inventory to only show red fields in their production environment that came from Clearbrain.](images/privacy-inventory-filtering.gif)
 
 Click into a field (for example, `ip`) in the Inventory to open the Inventory
 details. The details sheet displays how many times a specific field has been
@@ -100,7 +100,7 @@ connected to the Source that contains the field. The Access tab displays a list
 of who within your organization has access to this field.
 
 
-![](images/privacy-inventory-overview.png)
+![Screenshot of the product_id Inventory details page in the Privacy Portal.](images/privacy-inventory-overview.png)
 
 
 Finally, workspace owners can use the **Download CSV** button to export a CSV of
@@ -207,10 +207,10 @@ treat that property whenever it is appears in data Segment processes.
    - **Similar to** matches a **Key** that is similar to a term within a fuzzy string distance (for example "email" and "e-mail"). We built fuzzy matching using [this public GitHub repository](https://github.com/imjasonmiller/godice). If the score is > 0.7, then we say it's a match.
 
 
-![](images/privacy-add-new-matcher.gif)
+![Animation of a user creating a new matcher, SIN, with the exact matching setting selected.](images/privacy-add-new-matcher.gif)
 
 
-![](images/privacy-edit-matcher.png)
+![Screenshot of the Edit Matcher popup.](images/privacy-edit-matcher.png)
 
 
 Unless the field value pattern is unique, we recommend matching on the Key. For

src/protocols/apis-and-extensions/anomaly_detection.md

@@ -29,7 +29,7 @@ Regardless of the solution you choose, we recommend that you create a new Segmen
 
 Next, set up [Violation forwarding](/docs/protocols/validate/forward-violations/) for each Tracking Plan connected to the Source. Once connected, your sources will look like:
 
-![](images/protocols_meta_source_setup.png)
+![Diagram showing how violations and production events are routed to their respective destinations.](images/protocols_meta_source_setup.png)
 
 **Note: When you enable violation forwarding, it counts as 1 MTU toward your monthly MTU limit. If you are on an API plan, all forwarded violations count against your API limit. Violations might also generate costs in downstream destinations and data warehouses.**
 
@@ -49,13 +49,13 @@ Source: {% raw %}`{{properties.sourceName}}` \nEvent: `{{properties.eventName}}`
 ```
 When you're done, it'll look like the screenshot below.
 
-![](images/slack_violation_generated_setup.png)
+![Screenshot of a Slack destination settings page with Segment Event Name and Event Template fields filled out. The Event Template follows the convention outlined above.](images/slack_violation_generated_setup.png)
 
 
 ### Create customized Anomaly Detection dashboards in a BI tool
 Custom dashboards are a great way to focus your teams around the metrics and events that matter most to your business. With a few simple queries you can build a dashboard to share with teams, so everyone can understand how well they're doing against your data quality objectives. Here's an example dashboard that combines [forwarded Violations](/docs/protocols/validate/forward-violations/) with production event data to track data quality. See below for detailed SQL queries!
 
-![](images/anomaly_detection_dashboard.png)
+![Graphic with five bar charts created with sample data, showing different comparisons of violations across events and sources.](images/anomaly_detection_dashboard.png)
 
 Note: For all queries below, replace `protocols_audit_source` with whatever schema name you set for your forwarded violations source.
 

src/protocols/starter.md

@@ -25,13 +25,13 @@ You can add the Tracking Plan Read Only role to workspace members, or to groups
 To see your Tracking Plan, click **Protocols** in the left navigation. The first time you visit this section, the Segment App shows an explanation of tracking plans, which you can dismiss. Click **Create Tracking Plan** to get started.
 
 
-![](images/starter-tp-intro.png)
+![Screenshot of the Protocols page in the Segment app.](images/starter-tp-intro.png)
 
 
 From the screen that appears, click **Add Events** to add your first event to the tracking plan.
 
 
-![](images/starter-tp-empty.png)
+![Screenshot of the Tracking Plan setup page in the Segment app.](images/starter-tp-empty.png)
 
 
 
@@ -45,15 +45,15 @@ On the next page, you'll select the events that you need from the Segment Standa
 3. Click **Next** to review properties on the events.
 
 
-![](images/starter-tp-add-events.png)
+![Screenshot of the Select Events page on the Add events from templates popup, with Button Clicked, Demo Request Button Clicked, and Demo Requested selected.](images/starter-tp-add-events.png)
 
 
 
 The next screen shows the Events you chose and their properties. Properties are how you enrich the raw event data with useful context, which allows you to perform useful analysis and alerting. These standard events have a minimum set of properties based on what we know about the event type, and how it is usually used. You can add extra custom properties in the next step.
 
 Expand each event to view its properties. If you decide you want to add or remove Events, click **Previous** to go back to the event list. When you're satisfied that you've selected Standard Events for all of the activities on your site, click **Add**.
 
-![](images/starter-tp-review-props.png)
+![Screenshot of the Review Properties page on the Add events from templates popup, with all event properties selected.](images/starter-tp-review-props.png)
 
 
 
@@ -65,15 +65,15 @@ You might want to add extra properties to the Segment standard events, for examp
 
 To add a custom property, click the **plus** icon next to the event that the property should be attached to.
 
-![](images/starter-tp-view-event-details.png)
+![Screenshot of the Tracking Plan page, with the plus icon next to the Demo Requested event highlighted.](images/starter-tp-view-event-details.png)
 
 
 In the dialog that appears, enter the name and type of the property, and add a description.
 
 You can click **Save and add more** to add more than one property, or click **Save and exit** when you're satisfied that you've added all the properties you'll need.
 
 
-![](images/starter-tp-add-prop.png)
+![Screenshot of the Add property popup.](images/starter-tp-add-prop.png)
 
 
 
@@ -83,7 +83,7 @@ The Tracking Plan page shows an overview of the data that is arriving to your Se
 
 You can click each event in the table to expand it, view the event description, and view its properties and their descriptions. Property descriptions include the expected data type for each property.
 
-![](images/starter-tp-seen.png)
+![Screenshot of the Tracking Plan page, with the Sources Seen icon selected.](images/starter-tp-seen.png)
 
 The **Sending** column shows the number of Events Segment has seen with that description and format. You can expand this to see how many of the events Segment saw for Dev, Test, and Production sources. If you see a 0 in this column for all sources, this usually means that the event has not been implemented yet, or has not been implemented correctly.
 

src/protocols/tracking-plan/libraries.md

@@ -19,7 +19,7 @@ To create a new Library:
 2. Click **Libraries** in the top navigation bar
 3. Click **New Library** and follow the steps to create an event or property library
 
-![](../images/property_library_example.png)
+![Screenshot of the Ecommerce Properties Library.](../images/property_library_example.png)
 
 ### Tracking Plan Event Libraries
 
@@ -33,7 +33,7 @@ Tracking Plan property Libraries support Track event property groups. Property L
 
 You can import event and property libraries into a Tracking Plan. Enter the Draft mode for a Tracking Plan and click the **Import from Event or Property Library** dropdown. A wizard will appear allowing you to either add the events to a tracking plan, or add properties to selected events already in the tracking plan. After adding your events or properties, remember to merge your changes!
 
-![](../images/import_library_to_tracking_plan.gif)
+![Animation of a user importing events into their Tracking Plan using a Tracking Plan library.](../images/import_library_to_tracking_plan.gif)
 
 ### Library syncing
 
@@ -47,5 +47,5 @@ Syncing a Library makes events and properties un-editable, and bypasses the Trac
 > warning ""
 > All changes made to a synced library pass through to the Tracking Plans and may impact data deliverability
 
-![](../images/unsync_library.png)
+![Screenshot of the Synced Libraries page, with the overflow menu selected and the Unsync from Tracking setting visible.](../images/unsync_library.png)
 

src/protocols/validate/connect-sources.md

@@ -8,7 +8,7 @@ redirect_from: '/protocols/validate/'
 
 With your Tracking Plan is complete, it's time to apply the Tracking Plan to one or more Sources. Select **Connect Source** from the right hand menu for your specific Tracking Plan.
 
-![](../images/5763308453_Screen+Shot+2018-08-31+at+5.54.18+PM.png)
+![Screenshot of the Tracking Plans page, with the overflow menu selected.](../images/5763308453_Screen+Shot+2018-08-31+at+5.54.18+PM.png)
 
 
 From this menu, you will be redirected to a workflow to select a Source from your workspace. Note that a Source can only have one tracking plan applied to it. You *can't* select a Source that already has a Tracking Plan connected to it, but you *can* apply a Tracking Plan to multiple sources.
@@ -17,10 +17,10 @@ After selecting a Source, you will be shown the consequences of connecting your
 
 **IMPORTANT: Make sure to read through the consequences of connecting a source!**
 
-![](../images/5763823424_Image+2018-08-31+at+6.02.54+PM.png)
+![Screenshot of the Review Consequences page, with one type and consequence detail present on the page.](../images/5763823424_Image+2018-08-31+at+6.02.54+PM.png)
 
 ## Disconnect Source from Tracking Plan
 
 To disconnect the Source from the Tracking Plan, go to the Tracking Plan overview page, locate the column for the tracking plan you want to disconnect, then click the icon under the **Connected Sources**. In the settings that appear, click **Disconnect** next to the Source you want to disconnect.
 
-![](../images/protocols_disconnect_source.gif)
+![Animation of a user clicking on one of the sources attached to a tracking plan, clicking the disconnect button, and then confirming on a Disconnect source popup.](../images/protocols_disconnect_source.gif)