Merge pull request #4618 from segmentio/alt-text-v2

Adding alt-text [2/2]

Author: forstisabella

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

@@ -13,14 +13,14 @@ id: 57c4996480412f644ff29f78
 1. Navigate to your Zapier dashboard and select "Make A Zap" - you'll need at least one Zap so you can tell Segment where to route data later on.
 2. Search "Webhooks", then select "Catch Raw Hook" (Segment POSTs raw data to Zapier using our destination).
 
-    ![](images/webhooks-by-zapier.png)
-    ![](images/zapier-catch-raw-hook.gif)
+    ![Screenshot of the Make a Zap setup flow in Zapier.](images/webhooks-by-zapier.png)
+    ![Animation showing someone select the Catch Raw Hook option on the Select Webhooks by Zapier Trigger page. ](images/zapier-catch-raw-hook.gif)
 
 3. Complete the remaining Webhook set up steps, and Zapier will present you with a custom Webhook URL.
 4. Repeat step 3 to create as many Webhook URLs as you like.
 5. Remember that each Zapier "trigger" should be connected to an "Action" - i.e. posting the Webhook data to another downstream tool, such as Slack.
 
-    ![](images/zapier-choose-action.png)
+    ![Screenshot of the Zapier sidebar.](images/zapier-choose-action.png)
 
 6. From your Segment UI's Destinations page click on "Add Destination".
 7. Search for "Zapier" in the Catalog, select it, and choose which of your sources to connect the destination to.

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

@@ -29,7 +29,7 @@ Now you will be guided through three easy steps outlined below.
 
 * Click **Add** and a pop-up will appear.
     * From the pop-up, click on Authorize to allow this integration to access information about your calls in Aircall.
-![](images/XETcl1A.png)
+![Screenshot of the Aircall Authorize popup.](images/XETcl1A.png)
 
 If the integration is successful, you will see a message that says "Authentication for Aircall successfully created." Once you see this, click on Next.
 
@@ -43,17 +43,17 @@ Click on **Connect to Segment**
     * Login to your Segment account.
     * Go to Source from the left sidebar menu.
     * Click on Add Source and scroll to select HTTP API
-![](images/3edwOj6.png)
+![Screenshot of the Sources Catalog in Segment, with the HTTP API source selected.](images/3edwOj6.png)
 
     * Click on **Connect**
 
     * When creating a new Source setup, you will need to choose a name. We recommend that you choose an identifiable name such as "Aircall" for recognition. Then you may choose the warehouses or destination(s) where you'd like your data to be synced.
-![](images/eiXPdaW.png)
+![A screenshot of the Source setup page in Segment, with two warehouses connected.](images/eiXPdaW.png)
 
 
     * Once your source has been created, a **Write Key** will be generated. **Copy** this key and return to the configuration steps in Aircall to paste the key in the field as shown below.
-![](images/cUPCM42.png)
-![](images/uLu70VP.png)
+![Screenshot of the Aircall overview page in Segment, with the Write Key highlighted.](images/cUPCM42.png)
+![Screenshot of the Add Authentication popup in Aircall.](images/uLu70VP.png)
 
         - Note: if you see a field to input a **Engage Key**, this field is not required and you can leave this field blank.
 
@@ -66,7 +66,7 @@ If the integration is successful, you will see a message that says "Authenticati
 - There are up to [26 Aircall events](https://developer.aircall.io/api-references/#events) that can be pushed to Segment. As such, you will see a list of 26 possible events pre-populated for you as the default setting is for all and every Aircall event to be pushed to Segment.
 
 - **If there are events that you do not want to be sent to Segment**, delete the default value(s) shown in the list of 26 events (or write "null") if you determine that certain events should not be a source for Segment.
-![](images/qgbkbvA.png)
+![Screenshot of the Segment menu in Aircall with Segment event names entered in all of the event fields.](images/qgbkbvA.png)
 
 - Click on **Finish**.
 

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

@@ -18,7 +18,7 @@ In your favorite BI or analytics tool, you'll be able to analyze your email camp
 4. The next page ("Overview") will surface your Segment write key for Blueshift. Copy this write key.
 5. To finish the setup, you'll have to go into your Blueshift account and enter this Segment write key in their destinations settings. Find the right place in Blueshift by clicking Account > Webhooks:
 
-![](images/39c3955d4ea74e0a8ff07ef6651d4b30.png)
+![Screenshot of the Blueshift Account settings page, with the Segmentio Write Key and Webhook events highlighted.](images/39c3955d4ea74e0a8ff07ef6651d4b30.png)
 
 6. Click Save.
 7. Now when you go back to Segment, click into your Blueshift Source and you'll be able to add other downstream Destinations where you want to see email events.

src/connections/sources/catalog/cloud-apps/customer-io/index.md

@@ -27,7 +27,7 @@ If you previously sent email events using the Customer.io destination during our
 
 5. To finish the set up, go to your Customer.io account, go to **Data & Integrations > Integrations > Segment**, and enter the Segment write key.
 
-   ![](images/customerio_streaming_data_out.png)
+   ![Screenshot of the Segment Source settings page in Customer.io.](images/customerio_streaming_data_out.png)
 
 6. Click **Connect Segment**.
 

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

@@ -26,7 +26,7 @@ If you have previously enabled sending email events using the Drip destination d
 
 5. To finish the setup, you'll have to go into your Drip account and enter this Segment write key in their integrations settings. Find the right place in Drip by clicking Settings > Integrations > Segment.
 
-![](images/drip.png)
+![Screenshot of the Integrations page in Drip, with the Segment tab selected.](images/drip.png)
 
 6. Click **Save**.
 

src/connections/sources/catalog/cloud-apps/facebook-ads/index.md

@@ -16,13 +16,13 @@ Facebook is one of the most efficient ways to advertise online. Take your compan
 3. Give the source a nickname.
    The nickname is a label used in the Segment interface, and Segment creates a related schema name which you query against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself, like `Facebook Ads` or `Facebook Ads Prod`.
 
-   ![](images/setup.png)
+   ![Screenshot of the Facebook Ads setup flow in the Segment app.](images/setup.png)
 
 4. Click **Create And Continue** then **Connect** to OAuth into Facebook.
 
 5. Select which accounts you would like to sync (you may change this selection later).
 
-  ![](images/choose_account.png)
+  ![The second step in the Facebook Ads setup flow in the Segment app.](images/choose_account.png)
 
 6. Click **Finish**.
 

src/connections/sources/catalog/cloud-apps/google-ads/index.md

@@ -21,15 +21,15 @@ id: cQ8NOxeApJ
 
 2. Choose Google Ads and click `Connect`.
 
-   ![](images/connect.png)
+   ![Screenshot of the Google Ads source in the Segment app.](images/connect.png)
 
 3. Click `Authenticate Google Ads` and go through the authentication flow.
 
 4. Select a Google Ads account to sync and click `Next`
 
 5. Choose a schema name. This will be the namespace you will be querying against in your warehouse. Segment recommends that you choose a name that reflects the source itself, like `google_ads`, or `google_ads_usa`.
 
-   ![](images/schema.png)
+   ![Screenshot of the second step of the Google Ads setup flow in the Segment app.](images/schema.png)
 
 
 ### Permissions
@@ -42,7 +42,7 @@ By default, the primary Google Ads account connected to your Google account sync
 ### I'm getting an Internal Server Error!
 
 If you're getting the error pictured below, try disabling any ad block extensions in your browser and attempting again. 
-![](images/connection_failed.png)
+![Screenshot of an Internal Server Error message in the Segment app.](images/connection_failed.png)
 
 
 ## Sync Component

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

@@ -16,16 +16,16 @@ Take your company's email analysis to the next level by **adding Intercom as a S
 2. Choose Intercom and press **connect**.
 
 3. OAuth into Intercom
-![](images/intercom_source_qnsoxh.png)
+![Screenshot of the Connect to Intercom screen in the Intercom setup flow.](images/intercom_source_qnsoxh.png)
 
 4. We will verify all the required permissions
-![](images/image_1_Intercom.png)
+![Screenshot of the Permissions Verified screen in the Intercom setup flow.](images/image_1_Intercom.png)
 
 5. Configure the name for the Intercom schema in your warehouse
-![](images/image_2_Intercom.png)
+![Screenshot of the SQL Schema Name screen in the Intercom setup flow.](images/image_2_Intercom.png)
 
 6. Add a warehouse or connect Intercom to an already existing warehouse in your workspace
-![](images/image_3_Intercom.png)
+![Screenshot of the Add Warehouse screen in the Intercom setup flow.](images/image_3_Intercom.png)
 
 Voila! We'll begin syncing your Intercom data into Segment momentarily, and it will be written to your warehouse at your next Warehouse run.
 

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

@@ -14,9 +14,9 @@ id: acd1bc21d
    **Note**: You can add multiple instances if you have multiple Mailchimp accounts. That's why we allow you to customize the source's nickname and schema name!
 4. Next, provide credentials to an account with API permissions to access your Mailchimp data. It is recommended that you create a brand new api key for the Segment source. MailChimp restricts each api key to a maximum of 10 concurrent requests, so creating a dedicated one for Segment will ensure maximum throughput. You can find your API key in **Account > Extras > API Keys**. You can read more about API keys on [MailChimp's docs](http://kb.mailchimp.com/integrations/api-integrations/about-api-keys).
 
-   ![](images/3027189_API+Keys.png)
+   ![Screenshot of the Overview page in Mailchimp, with the Extras menu selected.](images/3027189_API+Keys.png)
 
-   ![](images/3032880_ChimpKey.png)
+   ![Screenshot of the API keys settings page in Mailchimp.](images/3032880_ChimpKey.png)
 
 
 5. Back in Segment, go to the MailChimp source and paste key into the MailChimp API Key field.

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

@@ -20,7 +20,7 @@ Take your company's email analysis to the next level by **adding Mandrill as a S
 4. Copy the auto-generated Webhook URL.
 5. In Mandrill, go to **Settings > Webhook** and paste the URL in the Event Notification settings pane.
 
-   ![](images/795640_mandrill-settings.png)
+   ![Screenshot of the Mandril Webhooks page.](images/795640_mandrill-settings.png)
 
    Once you enable the webhook, you're good to go! Segment automatically creates your collections based on which triggers you select. If any seem unnecessary for your analysis, feel free to leave them unchecked.