alt text qa

Author: forstisabella

src/_includes/content/functions/settings.md

@@ -4,11 +4,11 @@ Settings allow you to pass configurable variables to your function, which is the
 
 First, add a setting in **Settings** tab in the code editor:
 
-![A screenshot of the functions settings tab](/docs/connections/functions/images/settings-tab-empty.png){:width="500"}
+![The functions settings tab](/docs/connections/functions/images/settings-tab-empty.png){:width="500"}
 
 Click **Add Setting** to add your new setting.
 
-![A screenshot of the "Add Setting" section of the functions settings tab, with apiKey settings included](/docs/connections/functions/images/add-setting-dialog.png)
+![The "Add Setting" section of the functions settings tab, with apiKey settings included](/docs/connections/functions/images/add-setting-dialog.png)
 
 You can configure the details about this setting, which change how it's displayed to anyone using your function:
 
@@ -25,4 +25,4 @@ Click **Add Setting** to save the new setting.
 
 Once you save a setting, it appears in the **Settings** tab for the function. You can edit or delete settings from this tab.
 
-![A screenshot of the functions settings tab, showing the apiKey setting](/docs/connections/functions/images/settings-tab-non-empty.png){:width="500"}
+![The functions settings tab, showing the apiKey setting](/docs/connections/functions/images/settings-tab-non-empty.png){:width="500"}

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

@@ -78,7 +78,7 @@ ActiveCampaign also supports updating a contact's custom fields with this integr
 
 For example, if you have a contact in ActiveCampaign with these custom fields:
 
-![A screenshot of the fields page in ActiveCampaign, featuring two custom fields: Shirt Size and State.](images/jda1490xo_screenshot2015-12-07at3.58.27pm.png)
+![The fields page in ActiveCampaign, featuring two custom fields: Shirt Size and State.](images/jda1490xo_screenshot2015-12-07at3.58.27pm.png)
 
 You can update those fields using this identify call:
 

src/connections/destinations/catalog/adobe-analytics/identity.md

@@ -9,14 +9,14 @@ The Identity Resolution destination settings are:
 - **Marketing Cloud ID**
 - **Drop VisitorID**, and **No Fallbacks for VisitorID:Server-Side Only** destination settings.
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Identity Resolution section selected.](images/identity-resolution.png)
+![The Adobe Analytics settings page in Segment, with the Identity Resolution section selected.](images/identity-resolution.png)
 
 The Timestamp destination settings are:
 - **Timestamp Option**
 - **Send Both Timestamp and VisitorID for Timestamp Optional Reporting Suites**
 - **Prefer VisitorID for Hybrid Timestamp Reporting**
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Timestamps section selected.](images/timestamps.png)
+![The Adobe Analytics settings page in Segment, with the Timestamps section selected.](images/timestamps.png)
 
 ## Analytics.js - Device Mode
 

src/connections/destinations/catalog/adobe-analytics/index.md

@@ -45,7 +45,7 @@ To set up Adobe Analytics as a destination for your Segment data, Segment needs
 
 - If you're using Device-mode data collection with Analytics.js, or using a server-side library, you need your Adobe Report Suite ID, and your Tracking Server URL. You'll add this information in the Destination settings in the Segment app UI so that Segment can send information to Adobe. An example tracking server is `jimsbrims.sc.omtrdc.net`. You do not  need to include the hypertext transfer protocol (ie. `http://`). For more information on  how to identify your analytics tracking server and report suites see Adobe's [documentation here](https://docs.adobe.com/content/help/en/analytics-learn/tutorials/implementation/implementation-basics/how-to-identify-your-analytics-tracking-server-and-report-suites.html).
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the General section selected, and the above tracking server URL entered in the Tracking Server URL field.](images/trackingurl-setup.png)
+![The Adobe Analytics settings page in Segment, with the General section selected.](images/trackingurl-setup.png)
 
 - If you're collecting data from mobile devices, you can download the `ADBMobileConfig.json` file instead of specifying these settings in the UI which contains that information. Follow the instructions in Adobe's documentation, [here for iOS](https://marketing.adobe.com/resources/help/en_US/mobile/ios/dev_qs.html), and [here for Android](https://marketing.adobe.com/resources/help/en_US/mobile/android/dev_qs.html).
 
@@ -84,7 +84,7 @@ Segment's Analytics.js destination loads the Adobe `visitorAPI.js` library, but
 
 To use Adobe's Marketing Cloud Visitor ID Service, enter your **Marketing Cloud Organization ID** in the **Identity Resolution** settings tab in the Segment app.
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Identity Resolution section selected and a sample Organization ID entered in the "Marketing Cloud Organization Id" field.](images/mcvid.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Identity Resolution section selected.](images/mcvid.png)
 
 ---
 

src/connections/destinations/catalog/adobe-analytics/mobile.md

@@ -73,7 +73,7 @@ Here's an example of how you might map Segment events to Adobe Analytics events
 
 <!--todo: rewrite this so that it doesn't rely on the screenshots to explain how to map events in Segment-->
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample event mapping under the "Event2 Mobile" tab.](images/eventsV2.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected.](images/eventsV2.png)
 
 Here's an example of how you would implement the same mapping in Adobe's Mobile Services Dashboard:
 
@@ -83,7 +83,7 @@ Here's an example of how you would implement the same mapping in Adobe's Mobile
 
 You can use the `Context Data Variables` settings to map Segment `properties` to any context data variable defined in your Adobe Analytics Mobile Services dashboard. This includes both Adobe `props` and `eVars`. You can see a list of the Adobe variable types in your Adobe Mobile Services dashboard.
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample event mapping under the "Context Data Variables" tab.](images/map-property-segment.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected.](images/map-property-segment.png)
 
 Here's an example of how you would implement the same mapping in Adobe's Mobile Services Dashboard:
 

src/connections/destinations/catalog/adobe-analytics/settings.md

@@ -211,9 +211,9 @@ The images below show an example of how you might map an event and the correspon
 
 <!--todo: rewrite this so that it doesn't rely on the screenshots to explain how to map events in Segment-->
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample event mapping under the "Events" tab.](images/event-mapping.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample event mapping under the Events tab.](images/event-mapping.png)
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample property mapping under the "Props" tab.](images/prop-mapping.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample property mapping under the Props tab.](images/prop-mapping.png)
 
 ![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the eVars tab.](images/eVar-mapping.png)
 
@@ -300,9 +300,9 @@ When you make a `page` call, here's what Segment does from the browser when you
 
    Given the mapping settings below:
 
-   ![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample property mapping under the "Props" tab.](images/props-page-mapping.png)
-   ![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the "eVars" tab.](images/eVar-page-mapping.png)
-   ![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample event mapping under the "Hierarchy Values" tab.](images/hier-page-mapping.png)
+   ![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample property mapping under the Props tab.](images/props-page-mapping.png)
+   ![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the eVars tab.](images/eVar-page-mapping.png)
+   ![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample event mapping under the Hierarchy Values tab.](images/hier-page-mapping.png)
 
    If you make the following page call:
 
@@ -331,7 +331,7 @@ Custom Conversion variables, also known as eVars, are how Adobe segments convers
 You must configure an eVar mapping in your Segment destination settings to send eVars to Adobe on Track and Page calls. When configuring the mapping, the list of eVars must be defined in the Adobe Analytics UI. Map your Adobe Analytics eVar names to the Segment property names you're using in your Segment events. Enter a Segment property name on the left and an Adobe Analytics eVar number on the right. You can view your Segment events and properties in your Schema.
 
 An example eVar mapping in the Segment Destination settings UI should look like this:
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the "eVars" tab.](/docs/connections/destinations/catalog/adobe-analytics/images/eVar-mapping.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the eVars tab.](/docs/connections/destinations/catalog/adobe-analytics/images/eVar-mapping.png)
 
 ## Merchandising events
 
@@ -355,7 +355,7 @@ The Segment Adobe Analytics Merchandising setting runs as follows:
 
 Let's take the following example:
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the "Merchandising" tab. Two properties from the "eVar" tab are also included in this screenshot.](images/merchandising-event.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the Merchandising tab.](images/merchandising-event.png)
 
 The configuration in the example image above configures an `Order Completed` Segment event which sends Adobe Analytics:
 - `event1` in `s.events` with the value passed from `properties.increment`.
@@ -448,11 +448,11 @@ analytics.page({
 
 Custom Traffic Variables, also known as props, allow you to correlate custom data with specific traffic-related events in Adobe. To learn more about props and how to configure them in the Adobe UI, see the documentation [here](https://docs.adobe.com/content/help/en/analytics/admin/admin-tools/traffic-variables/traffic-var.html). You can map your Segment properties in your destination settings to any of your Adobe props.
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample property mapping under the "Props" tab.](images/prop-mapping.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample property mapping under the Props tab.](images/prop-mapping.png)
 
 You can either send the property value as a string (ie. `'brady'`) or as an array (`['brady', 'edelman', 'blount']`). If you choose to send them as an array, Segment defaults to join it so that it is a pipe (`|`) delimited string before sending to Adobe (ie. `'brady|edelman|blount'`). See the [documentation on setting a custom delimiter](#custom-delimiter) to learn more.
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample properties mapped under the "Props" tab. The second property has an optional delimiter selected.](images/prop-custom-delimiter.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample properties mapped under the Props tab.](images/prop-custom-delimiter.png)
 
 ## List Variables - lVars
 
@@ -467,7 +467,7 @@ For list variables and props you can either send the property value as a comma d
 **Note:** You must configure the custom delimiter in _both_ the Adobe Analytics dashboard, and in the Segment Adobe Analytics destination settings, for each list variable and prop. Do this in the Adobe Analytics dashboard before setting up this mapping in the Segment destination settings.
 
 The example below shows how to configure the Segment custom delimiter mapping for a List Variable.
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample property with delimiter under the "List Variables" tab.](images/list-var-delimiter.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample property with delimiter under the List Variables tab.](images/list-var-delimiter.png)
 
 When you send an event:
 ```javascript
@@ -488,7 +488,7 @@ Hierarchy variables mirror how customers can track “breadcrumbs” or “bread
 
 Map your Adobe Analytics hVars to the property names you use in your Segment Page calls. Enter a Segment property name on the left, and an Adobe Analytics hVar number on the right. You can view your Segment page calls and properties in your Schema.
 
-![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample hierarchy variable mapping under the "Hierarchy Variables" tab.](images/hier-mapping.png)
+![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and a sample hierarchy variable mapping under the Hierarchy Variables tab.](images/hier-mapping.png)
 
 ## Context Data Variables
 Context data variables let you define custom variables on each page that processing rules can read. See  the Adobe documentation to learn more about [how to use Adobe Analytics `contextData` and use processing rules](https://docs.adobe.com/content/help/en/analytics/implementation/vars/page-vars/contextdata.html) to populate analytics variables from that data.

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

@@ -13,7 +13,7 @@ id: 54521fd525e721e32a72ee8e
 2. Search for "Adroll" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. Locate both your AdRoll Advertiser ID and Pixel ID in AdRoll's "Audience" tab, "AdRoll Pixel" section. Click on "View Pixel". Your Advertiser ID will be listed beside `adroll_adv_id` and your AdRoll Pixel will be listed beside `adroll_pix_id`.
 
-    ![A screenshot of the Adroll Audience page, with Site Audiences selected. An arrow points to the Adroll Pixel "View Pixel" button.](images/adroll-pixel.png)
+    ![A screenshot of the Adroll Audience page, with Site Audiences selected.](images/adroll-pixel.png)
 
 4. Add both your Advertiser ID and Pixel ID to your Segment Destination Settings.
 
@@ -54,7 +54,7 @@ We'll fire the correct pixel accordingly to put the user into that "segment" whe
 
 Then, inside AdRoll you can create a "segment" of all users doing any of those events by adding a `+` to the segment name and adding it in the URL field, like this:
 
-   ![A screenshot of the  New User Segment page in Adroll, with a specified name, url pattern, and duration.](images/adroll-mapping.png)
+   ![A screenshot of the New User Segment page in Adroll, with a specified name, url pattern, and duration.](images/adroll-mapping.png)
 
 ### Conversion Value
 

src/connections/destinations/catalog/amazon-lambda/index.md

@@ -31,7 +31,7 @@ To build a Lambda function:
 1. Go to the Lambda service page in your AWS account.
 2. Click **Create a function** to create a new function.
 
-    ![A screenshot of the AWS Lambda service page, with a box around the "Create a function" button.](images/LambdaDashboard.png)
+    ![A screenshot of the AWS Lambda service page, with a box around the Create a function button.](images/LambdaDashboard.png)
 
 3. Select **Author from scratch** since Segment will be providing the source code for the function.
 4. Enter a name for your function and select your preferred runtime.
@@ -63,11 +63,11 @@ Using CloudFormation minimizes the setup steps needed, and is Segment's recommen
 2. Create the CloudFormation stack.
    1. Within the AWS Console, navigate to **CloudFormation > Stacks**.
 
-      ![A screenshot of the CloudFormation dropdown in AWS, with "Stacks" selected.](images/CloudFormationStackNav.png)
+      ![A screenshot of the CloudFormation dropdown in AWS, with Stacks selected.](images/CloudFormationStackNav.png)
 
    2. Click **Create Stack**.
 
-      ![A screenshot of the CloudFormation Stacks page in AWS, with the "Create Stack" button visible.](images/CloudFormationCreateStack.png)
+      ![A screenshot of the CloudFormation Stacks page in AWS, with the Create Stack button present.](images/CloudFormationCreateStack.png)
 
    3. On the **Select Template** page, select **Upload a template to Amazon S3**. Using **Choose File**, select the SegmentLambdaDestinationCFTemplate you downloaded in the previous step.
 
@@ -80,18 +80,18 @@ Using CloudFormation minimizes the setup steps needed, and is Segment's recommen
       * **NOTE:** For security purposes, Segment will set your Workspace ID as your External ID. If you're currently using an External ID different from your Workspace ID, reach out to our support team so they can change it and make your account more secure.
    7. The **LambdaARN** parameter corresponds to the **Lambda** setting in your Segment Lambda destination settings.
 
-      ![A screenshot of the Specify Details page in the AWS Cloud Formation setup, with the LambdaARN value visible.](images/CloudFormationStackDetails.png)
+      ![A screenshot of the Specify Details page in the AWS Cloud Formation setup, with the LambdaARN value present.](images/CloudFormationStackDetails.png)
 
    8. You can leave the next page as is, no changes needed.
    9. On the last page, review your template details and click **Create**.
    10. You will now see your new Stack listed in the Stacks page.
 
-        ![A screenshot of the Stacks page, with a Stack named SegmentLambdaRoleTest visible.](images/CloudFormationCreateInProgress.png)
+        ![A screenshot of the Stacks page, with a Stack named SegmentLambdaRoleTest present.](images/CloudFormationCreateInProgress.png)
 
    11. Once the status is **CREATE_COMPLETE**, click on the name of your Stack.
    12. On the Stack Detail page under the **Resources** section, you will see a policy and role listed.
 
-        ![A screenshot of the Resources section of the Stack Detail page, with a invokeLambdaPolicy and an invokeLambdaRole visible.](images/CloudFormationLambdaRole.png)
+        ![A screenshot of the Resources section of the Stack Detail page, with a invokeLambdaPolicy and an invokeLambdaRole present.](images/CloudFormationLambdaRole.png)
 
    13. Click the **Physical ID** of the role. You will be redirected to the summary page for the role within the IAM console.
    14. Copy the **Role ARN** and copy it into the **Role Address** setting in your Segment Lambda destination settings.