batch of alt text

Author: forstisabella

src/connections/destinations/catalog/ibm-ubx/index.md

@@ -46,14 +46,14 @@ endpoint from Segment's support team._
    to "Endpoints", then "Register a new endpoint" and select "Segment". Then
    click "Register" to proceed.
 
-    ![](images/ubx-register-endpoint.png)
+    ![A screenshot of the UBX dashboard, with a green arrow pointing to the Segment endpoint.](images/ubx-register-endpoint.png)
 
 5. Once registered, the new endpoint's status will remain "Pending" in the
    "Endpoints" tab until it has been activated. To activate an endpoint,
    include your UBX account's API URL and your endpoint authentication key in an
    email to Segment using our [tech support form](https://segment.com/help/contact/).
 
-    ![](images/endpoint-details.png)
+    ![A screenshot of the UBX Endpoints tab showing a Segment endpoint with a status of Active.](images/endpoint-details.png)
 
 6. Segment will activate your endpoint within 24 hours, at which time its status
    will update to "Active" in the UBX dashboard. Now, you can grab your endpoint
@@ -102,7 +102,7 @@ Beware, however - UBX event destinations will only receive events to which they
 are subscribed. To subscribe a UBX destination to events from the Segment
 publisher, navigate to the "Events" tab and select "Subscribe to events".
 
-![](images/subscribe-to-events.png)
+![A screenshot of the UBX Events tab, with the Segment endpoint selected.](images/subscribe-to-events.png)
 
 Make sure that you subscribe your UBX event subscriber endpoints to the events
 you'd like them to consume from the Segment publisher.

src/connections/destinations/catalog/iterable/index.md

@@ -119,7 +119,7 @@ Iterable supports sending [email events](/docs/connections/spec/email/) to other
 
 To enable this feature, go to Destinations, Third Party, and select Segment in the Add Destinations button. Then, enter your API key.
 
-![Send email events from Iterable](images/Iterable1.png)
+![Send email events from Iterable.](images/Iterable1.png)
 
 ## Sending Push Notification Data from Iterable
 
@@ -143,61 +143,61 @@ Iterable is a marketing platform that can accept Engage information. You can sen
 You can send Computed Traits created in Engage as `identify` calls to create user properties in Iterable.
 
 
-![](images/pers-computed-traits.png)
+![A screenshot of a profile in Segment, with the Traits tab selected.](images/pers-computed-traits.png)
 
 
 From the Iterable UI, you can check a specific user profile for Computed Traits by going to **Audience → Contact Lookup**. Engage  updates user profiles that contain an `email` or `userId`.
 
-![](images/pers-iterable-profile-computed.png)
+![A screenshot of a user profile in Iterable, with the two computed traits outlined in green.](images/pers-iterable-profile-computed.png)
 
 
 
 Computed traits without a lookback window search across all historical events and update in real time.
 
 Computed traits with a lookback window only search across events that occurred within the specified timeframe. Computed traits *with* a lookback window are updated hourly.
 
-![](images/pers-lookback-2.png)
+![A screenshot of the Segment Configure and Preview Your Trait screen, with the lookback window outlined in green.](images/pers-lookback-2.png)
 
 ### Using Audiences with Iterable
 
 You can send Engage Audiences to Iterable as `identify` or `track` calls. You can choose the type of call to send when you add Iterable as a destination for an audience. Engage sends updates to Iterable for users who have a known `email` or `userId`.
 
-![](images/pers-iterable-audiences.png)
+![A screenshot of the Iterable settings page in Segment, with a defined Enter Event and Exit Event.](images/pers-iterable-audiences.png)
 
 #### Audiences using Identify Calls
 
 When you send Audiences as `identify` calls, Engage adds a trait matching the name of the audience to the user's profile, with a boolean value to indicate if the user is in the audience. For example, when a user first completes an order in the last 30 days, Engage sends an `identify` call with the property `order_completed_last_30days:` `true`. When the user no longer satisfies these criteria (for example when their last purchase was more than 30 days ago) Engage sets that value to `false`.
 
-![](images/pers-audience-id.png)
+![A screenshot of the Audience tab in Segment, with a user profile selected and the trait "Order Completed Last 30 days" on the user's profile.](images/pers-audience-id.png)
 
 You can check a specific user profile for Audience membership in the Iterable UI by going to **Audience → Contact Lookup**.
 
-![](images/pers-iterable-profile-audience.png)
+![A screenshot of the Contact Lookup page in Iterable, with a box around the "Order Completed Last 30 days" audience.](images/pers-iterable-profile-audience.png)
 
 When you first create an audience, Engage sends an  `identify` call for every user in the audience. Later syncs only send updates for users who were added or removed from the audience since the last sync.
 
 #### Audiences using Track Calls
 
 When you use `track` calls, Segment sends an Audience Entered event when the user enters the audience, with the audience name as a property of the event. When the user exists the audience, Engage sends an Audience Exited event with the same property.
 
-![](images/pers-audience-track.png)
+![A screenshot of Segment's Audience Explorer with an Audience Entered event.](images/pers-audience-track.png)
 
 You can check a specific user profile for an Audience event in the Iterable UI by going to **Audience → Contact Lookup→ Event History** tab.
 
-![](images/pers-iterable-profile-events.png)
+![A user profile in Iterable with the Event History tab selected.](images/pers-iterable-profile-events.png)
 
 Audiences without a lookback window search across all historical events, and update in real time.
 
 Audiences with a lookback window only searches across events that occurred within the specified timeframe. Audiences *with* a lookback window are updated hourly.
 
-![](images/pers-lookback.png)
+![A screenshot of the Segment audience builder, with a box around the lookback window.](images/pers-lookback.png)
 
 ## Setting Up Engage and Iterable
 
 To send computed traits or audiences to Iterable, you first must connect it to your Engage space. Once it's set up, you can select Iterable as a destination for Engage data when you create computed traits or audiences.
 
 1. In your Segment workspace, click Engage in the left navigation bar, and select your Space.
-2. Click **Engage Settomgs** and select the **Destinations** tab.
+2. Click **Engage Settings** and select the **Destinations** tab.
 3. Click **Add Destination**.
 2. Search for **Iterable** and add the destination to your Space.
 3. On the set up screen, enter in your API Key for the Iterable.

src/connections/destinations/catalog/kenshoo-infinity/index.md

@@ -10,7 +10,7 @@ In order to track conversions, you want to make sure you insert your **Subdomain
 
 Next thing you need to do is to map the Segment `.track()` event names to the `conversionType` of the Kenshoo Infinity Pixel. The default value of this will be `'conv'`.
 
-![](images/e7ffbbc58004b02ad61a95d136c98769.png)
+![A screenshot of the Segment Events Mapper.](images/e7ffbbc58004b02ad61a95d136c98769.png)
 
 For each mapped `.track()` event, we will send `properties.revenue` (default to `'0'`), `properties.currency` (default to `'USD'`) and `properties.orderId` (capped at 64 chars). You can also map to Kenshoo's semantic `promoCode` property by passing in a destination-specific option:
 

src/connections/destinations/catalog/kubit/index.md

@@ -12,7 +12,7 @@ This destination is maintained by Kubit. For any issues with the destination, [c
 {% include content/connection-modes.md %}
 
 1. On Kubit's [Welcome Page](https://segment.kubit.ai/segment), click on “**Connect to Segment**”.
-   ![](images/oauth.png)
+   ![A screenshot of the Kubit "Segment Configuration" page.](images/oauth.png)
 2. In Segment, select the Source to connect to the Kubit destination.
 3. Click **Allow**.
 

src/connections/destinations/catalog/linkedin-insight-tag/index.md

@@ -23,13 +23,13 @@ Click the account name for which you'd like to set up website retargeting, conve
 
 ### **2. [Create an Ad Account](https://www.linkedin.com/ad/accounts).**
 
-![](images/w53Sm6Jpg3.png)
+![A screenshot of the Linkedin Campaign manager accounts page.](images/w53Sm6Jpg3.png)
 
 Next, create an Ad Account in order to access the LinkedIn Insight Tag. It will ask for some currency information, but no payment is currently required to access the Insight Tag. Once the Ad Account is created, it's time to find the tag.
 
-### **3. Get the LinkedIn Data Parter ID.**
+### **3. Get the LinkedIn Data Partner ID.**
 
-![](images/K5HEnmgvse.png)
+![A screenshot of the LinkedIn Campaign Manager page, with the Account Assets dropdown selected.](images/K5HEnmgvse.png)
 
 From the Campaign Manager for the account, open the **Account Assets** dropdown menu. From there, select **Insight Tag** and move on to the specific tag.
 
@@ -39,17 +39,17 @@ Click **I will use a tag manager**.
 
 Your partner ID appears in a box below. Click the box to copy your partner ID to your clipboard.
 
-![](images/will-use-tag-manger.png)
+![A screenshot of LinkedIn's See Tag section, with an outline around the partner ID.](images/will-use-tag-manger.png)
 
 
 ### **4. Activate the LinkedIn Insight Tag destination in Segment.**
 
 Log into your Segment account, go to the Destinations Catalog in the desired workspace, and select the LinkedIn Insight Tag destination (located at `https://segment.com/<Your Workspace>/destinations/catalog/linkedin-insight-tag`).
 
-![](images/kyTVBLjRyI.png)
+![A screenshot of the LinkedIn destination page in the Segment catalog.](images/kyTVBLjRyI.png)
 
 From there, click **Configure LinkedIn Insight Tag** and select the source for which you want to activate it. Click **Confirm Source**. The selected source loads, and a sidebar appears, asking for the LinkedIn Data Partner ID.
 
-![](images/Nmad4zYvWy.png)
+![A screenshot of the Settings page for the LinkedIn Insight Tag destination.](images/Nmad4zYvWy.png)
 
 Select that option and paste in the LinkedIn Data Partner ID that you copied earlier. Click **Save**, then click **Activate Destination**. Our servers build the latest CDN for that source, and the LinkedIn Insight Tag loads on the sites that use that source's Segment snippet!

src/connections/destinations/catalog/mammoth/index.md

@@ -35,11 +35,11 @@ Mammoth Segment destination requires that you have a dataset on Mammoth's side.
 3. The add dataset dialog opens. Make sure the option selected is *Webhooks*.
 4. Give your dataset a name, and click **Done**. A new dataset appears in the data library.
 
-   ![](images/A8mLIPZ.png)
+   ![A screenshot of the Mammoth webhook dataset creation screen.](images/A8mLIPZ.png)
 
    The dataset you created shows an API KEY which you need to connect to Segment.
 
-   ![](images/JsTuMCy.png)
+   ![A screenshot of a dataset in Mammoth, with a box around the API Key.](images/JsTuMCy.png)
 
 5. Click the new dataset you created in the previous step.
 6. From the preview panel, click **copy** to copy the API key to your clipboard.

src/connections/destinations/catalog/marketo-static-lists/index.md

@@ -48,11 +48,11 @@ In this step, you'll create an API-Only Marketo user with both Access API and Le
 
 1. You can use an existing role with these permissions, or create a new role that has both Access API and Access Lead Database permissions. (Do this in Marketo by going to **Admin**→ **Users & Roles** → **Roles**).
 
-   ![](images/marketosl-create-new-role.png)
+   ![A screenshot of the Marketo "Create New Role" popup.](images/marketosl-create-new-role.png)
 
 2. Go to **Admin**→ **Users & Roles** → **Users** → **Invite New User** and create a new **API Only user** with the role that has both Access API and Lead Database permissions. **Be sure to check the API Only box.**
 
-   ![](images/marketosl-perms.png)
+   ![A screenshot of the Marketo "Invite New User" page, with the roles "Marketo Static List" and "API only" selected.](images/marketosl-perms.png)
 
 
 ### Step 2: Create a Marketo Launchpoint Service for Engage
@@ -61,7 +61,7 @@ In this step, you'll create an API-Only Marketo user with both Access API and Le
 2. Create a new service. In the Service field, select `Custom`, and in the **API Only User** field, select the user you created in step 1.
 3. Write down the **Client Id** and **Client Secret** for this service, as you will need it in Step 4.
 
-![](images/marketosl-newservice.png)
+![A screenshot of the New Service popup in Marketo.](images/marketosl-newservice.png)
 
 
 
@@ -70,7 +70,7 @@ In this step, you'll create an API-Only Marketo user with both Access API and Le
 1. Go to your Marketo Lead Database and create a new folder under Group Lists. Once connected, each Engage audience shows up as a list in this folder.
 
 
-   ![](images/marketosl-newfolder.png)
+   ![A screnshot of the Marketo Lead Database, with a New Folder menu item selected.](images/marketosl-newfolder.png)
 
 2. Before you continue to the next step, in Marketo, go to **Admin → Web Services**, and copy or write down the REST API Endpoint. **Be sure to copy the REST endpoint and not the SOAP endpoint.** You'll need that in the next step.
 
@@ -92,7 +92,7 @@ In this step, you'll create an API-Only Marketo user with both Access API and Le
 > info ""
 > Only users with an email address appear in the list in Marketo. Users with multiple email addresses as external ids appear in the list once for each email address.
 
-![](images/marketosl-leads.png)
+![A screenshot of the Marketo Lead Database Audience page.](images/marketosl-leads.png)
 
 You can view the audience in Marketo by going to **Lead Database→ Group Lists→Name of folder you created in Step 3 → Audience name**
 
@@ -114,6 +114,6 @@ Only users in the audience who also have an email address are uploaded to the li
 
 You might need to adjust your query to filter out users without an email so you can get a better estimate of how many users will appear on the list. In the example below, we added an AND condition where users have a Custom trait of `email` which `exists`.
 
-![](images/personas-add-emailtrait.png)
+![A screenshot of the Audiences page in Segment, with a box outlining the custom trait discussed above.](images/personas-add-emailtrait.png)
 
 If a user has multiple email addresses, each address appears once in the Marketo lists.