Alt text

- Facebook Custom Audiences
- Pinterest Tag
- Repeater
- Sailthru
- Salesforce DMP
- Salesforce Marketing Cloud
- Trafficguard
- Tray.io
- Twitter Ads
- Vitally

Author: forstisabella

src/connections/destinations/catalog/personas-facebook-custom-audiences/index.md

@@ -96,7 +96,7 @@ Once created, the audience should be available in Facebook in ten minutes unless
 - From within Facebook Ads, go to **Business Manager > All tools > Assets > Audiences**.
 - Click the Facebook audience name that matches your Engage audience name, and check **Audience History** to see how many users were added.
 
-![](images/fb_ca_final.png)
+![A screenshot of the Audiences page in Facebook Ads.](images/fb_ca_final.png)
 
 
 ## Additional Traits Matching

src/connections/destinations/catalog/pinterest-tag/index.md

@@ -21,7 +21,7 @@ In order to access the Pinterest Tag, you will need to have a Pinterest business
 
 This will redirect to your Pinterest tags menu.
 
-![](images/conversions-page.png)
+![A screenshot of the Pinterest Ads menu, with an arrow pointing to the Conversions option.](images/conversions-page.png)
 
 ### **3. Find the Pinterest Tag ID.**
 
@@ -34,11 +34,11 @@ If you haven't yet made a Pinterest tag, then select "Create Tag." Upon naming y
 
 Log into your Segment account, and go to the Destinations Catalog in the desired workspace and select the Pinterest Tag destination (located at `https://segment.com/<Your Workspace>/destinations/catalog/pinterest-tag`).
 
-![](images/pinterest-tag-configure.png)
+![A screenshot of the Pinterest Tag menu page.](images/pinterest-tag-configure.png)
 
 From there, select "Configure Pinterest Tag" and select the desired source to activate it for, and select "Confirm Source." The selected source will be loaded, and a sidebar will appear, asking for the Pinterest Tag ID.
 
-![](images/pinterest-tag-activate.png)
+![A screenshot of the Pinterest Tag destination page in the Segment app.](images/pinterest-tag-activate.png)
 
 Select that option and put in the Pinterest Tag ID that we collected earlier. Select "Save." In addition, one can optionally bind Segment track event names to specified Pinterest Event names. Details on that are provided below. In addition, Segment Track call properties can be added to this list to also be sent to Pinterest. Once ready, select "Activate Destination." Our servers will build the latest CDN, and the Pinterest Tag will then load on the sites that use that source's Segment snippet!
 

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

@@ -22,6 +22,6 @@ Go back to the Repeater destination's settings, and add this `writeKey` to the w
 
 You can do this for as many sources as you need.
 
-![](images/write-key-settings.png)
+![A screenshot of the Write Keys field in the Repeater destination settings page.](images/write-key-settings.png)
 
 Repeater sends all events it receives to the sources you specified, identified by the write key(s) you added.

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

@@ -51,7 +51,7 @@ Segment will automatically alias users for you so if you `identify` a user who y
 
 An `identify` event will appear in Sailthru's user lookup feature if there is an email present (Sailthru only allows a user lookup up based on an email):
 
-![](images/1488751534977.png)
+![A screenshot of a user's profile as it appears in the Sailthru User Lookup page.](images/1488751534977.png)
 
 Or within the **Users > Lists** feature, based on the default list you configured in the Segment UI or passed in through the destinations object like so:
 
@@ -67,7 +67,7 @@ analytics.identify("38472034892",{
   });
 ```
 
-![](images/1488751628625.png)
+![A screenshot of a list of users on the the Manage Mailing List page in Sailthru.](images/1488751628625.png)
 
 You can also configure an `optout_email` value in the Segment UI, or pass in a value through the destinations object with one of the Sailthru expected values:
 
@@ -89,18 +89,18 @@ So if you send an `identify` call without a `traits.email` and only a `userId`,
 
 When you `track` an event, we will send that event to Sailthru as a custom event. **Important**: You must have each event mapped in Sailthru within **Communications > Lifecycle Optimizer** in order to use the custom event. Be sure that the **Status** is set to **Active**:
 
-![](images/1488218489126.png)
+![A screenshot of a Flow in Sailthru. The Lifecycle Optimizer menu item is selected from the Communications menu dropdown. ](images/1488218489126.png)
 
 Your account must have triggers or lifecycle optimizer enabled. This should be enabled when the account is setup, however, just to be sure you may need to contact your account representative to confirm it is enabled.
 
 A custom event will hit the **Sailthru Lifecycle Optimizer** feature. Navigate to **Communications > Lifecycle Optimizer** in your Sailthru dashboard:
 
-![](images/1488751128521.png)
+![A screenshot of the Lifecycle Optimizer page in Sailthru, with a list of Flows.](images/1488751128521.png)
 
 
 Configure a custom event to a new flow and trigger a follow up action to the event:
 
-![](images/1488751210325.png)
+![A screenshot of a Flow in Sailthru, with two steps in the process diagram.](images/1488751210325.png)
 
 
 For instance, in the above example notice that the `Registered` event will add the user who trigger the event to a list.
@@ -109,14 +109,14 @@ For instance, in the above example notice that the `Registered` event will add t
 
 When you `track` an event with the name `Order Completed` using the [e-commerce tracking API](/docs/connections/spec/ecommerce/v2/#order-completed), we will send the products you've listed to Sailthru's purchase log:
 
-![](images/1488752018885.png)
+![A screenshot of Sailthru, with the Purchase Log item selected from the Analytics menu.](images/1488752018885.png)
 
 In addition, it will also appear within the user view under purchase history:
 
-![](images/1488752126668.png)
+![A screenshot of the fields collected in Sailthru when users make a purchase.](images/1488752126668.png)
 
 Note that the main identifier is `email` not `id`
-![](images/1487272939423.png)
+![A screenshot of a user's purchase history in Sailthru, showing two purchases.](images/1487272939423.png)
 
 Sailthru does not allow the `extid` to be the main lookup identifier for their Purchase API. Instead, Sailthru requires an `email` as the primary identifier. Segment will make a GET request to retrieve the user's email based on their `userId`, which is their `extid` in Sailthru.
 

src/connections/destinations/catalog/salesforce-dmp/index.md

@@ -36,7 +36,7 @@ Next, configure the Destination in the Segment web app:
 4. In the **Sites** tab, locate the site you want to use as the SFDMP destination.
    If you haven't created any sites yet, click **Create Site** and go through the options to create a new site.
 
-   ![](images/salesforce-dmp-setup1.png)
+   ![A screenshot of the Manage tab in Salesforce DMP, with the Sites item selected.](images/salesforce-dmp-setup1.png)
 
 5. In the dropdown, find the site tag for the site you want to use. The string you need is under "Config" and will look something like `r0u08k4tz`.
 6. Go back to the Segment App, and navigate to the Salesforce DMP destination you're setting up. Locate the ConfigID setting, and paste the value you found in that field.

src/connections/destinations/catalog/salesforce-marketing-cloud/index.md

@@ -109,14 +109,14 @@ Before you leave this screen, copy the External Key for the Data Extension. You'
 
 The example below shows a Data Extension for Identify calls that stores Email, First Name, and Last Name traits. Note the external key in the left column.
 
-![](images/identify-dext.png)
+![A screenshot of the SFMC Contact Builder, with a Test Identify call on the Data Extensions page.](images/identify-dext.png)
 
 
 ### Configure the Salesforce Marketing Cloud Destination in Segment
 
 1. Add the Salesforce Marketing Cloud Destination to your Segment Workspace.
 2. In the **Destination Settings**, locate the **Identify Data Extension External Key** setting. Enter the External Key you copied for the Data Extension that you set up in SFMC.
-![](images/sfmc-identify-dext-key.png)
+![A screenshot of the settings page in Segment for SFMC, with an arrow pointing to the Identify Data Extension External Key field.](images/sfmc-identify-dext-key.png)
 
 
 #### Data Formatting Requirements
@@ -191,7 +191,7 @@ When you finish setting up the Data Extension, copy the External Key. You'll use
 
 The example below shows a Data Extension for `User Registered` Track calls that stores the `userId`, `timestamp`, and `plan` properties:
 
-![](images/dext-user-regd-example.png)
+![A screenshot of a User Registered call in the SFMC Data Extension tab.](images/dext-user-regd-example.png)
 
 > warning ""
 > Segment doesn't automatically send timestamps. You must add timestamps as a property in the Track Call to send timestamps to the destination.
@@ -205,7 +205,7 @@ Just as you did for the Identify Data Extension, copy and paste the External ID
 
 1. Add the Salesforce Marketing Cloud Destination to your Segment Workspace if you haven't already.
 2. In the **Destination Settings**, locate the "Conversion events" setting. Enter the External Key you copied for the Track Data Extension that you set up in SFMC.
-![](images/sfmc-conversion-events.png)
+![A screenshot of the settings page in Segment for SFMC.](images/sfmc-conversion-events.png)
 
 
 #### Configuring Primary Keys for each conversion event
@@ -224,7 +224,7 @@ If you don't want to deduplicate rows, you can check the `UUID Primary Key` to c
 
 If we return to the example of one user clicking multiple buttons, if you check the `UUID Primary Key` box then every time the user clicks a button, it creates a new record in the `Button Clicked` Data Extension.
 
-![](images/uuid-primary-key.png)
+![A screenshot of the event conversion settings page in Segment.](images/uuid-primary-key.png)
 
 
 #### Using multiple Primary Keys
@@ -288,7 +288,7 @@ When you sync to an existing Data Extension, note these additional requirements:
 - All fields in the Data Extension must be nullable (meaning optional, or not required), except the `Contact Key` field.
 - Any fields that you send with Segment, and which already exist in the Data Extension, must be of the correct data type. The standard identifiers Segment sends come from the [Context object](/docs/connections/spec/common/#context), and appear in the image below.
 
-![](images/existing-dext-data-types.png)
+![A screenshot of the Fields section on the Data Extension page in SFMC.](images/existing-dext-data-types.png)
 
 
 ### Syncing Engage Audiences to SFMC
@@ -331,7 +331,7 @@ If your SFMC instance already contains data, then when Segment sends Identify ca
 
 When you send an email or push notification, you need to choose which email address or phone number to send to. The options for selecting an email/phone in the Journey Builder look like this:
 
-![](images/journey-builder-options.png)
+![A screenshot of the Journey Builder, with the Default Email Address and Default Mobile Number options present.](images/journey-builder-options.png)
 
 If you select **Use email attribute from Entry Source** you can use an email or phone attribute included in the API Event or Data Extension that triggers the Journey. (Otherwise, you must use an email address attribute or the default phone number attribute on a Contact record.)  To use this, you must include an email address and phone number as a property or trait in every single Track/Identify call mapped to SFMC.
 

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

@@ -18,7 +18,7 @@ This destination is maintained by TrafficGuard.
 2. Search for "TrafficGuard" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. Enter the "API Key" into your Segment Settings UI which you can find in the property in the TrafficGuard dashboard.
 
-![](images/trafficguard.png)
+![A screenshot of the input settings page in TrafficGuard, with the Segment API Key field present.](images/trafficguard.png)
 
 4. Calls will now be visible in TrafficGuard dashboards in real-time.
 

src/connections/destinations/catalog/tray-io/index.md

@@ -11,7 +11,7 @@ You can target up to 10 discrete tray workflows from within Segment.
 ## Message Types
 Tray supports all message types. You can filter the message type when you configure the trigger within tray.
 
-![](images/tray-types.png)
+![A screenshot of a Tray.io workflow, with an outline around the Operation menu.](images/tray-types.png)
 
 ### Delete
 
@@ -25,4 +25,4 @@ The payload will consist of:
 
 In order to receive and process the message, we recommend starting with an "All Message Types" filter, and then removing all the default types and adding `"delete"` manually. We're working with tray to add a dedicated `"delete"` message type filter in the dropdown pictured above.
 
-![](images/tray-delete-setup.gif)
+![An animation showing someone triggering a user deletion in tray.](images/tray-delete-setup.gif)

src/connections/destinations/catalog/twitter-ads/index.md

@@ -32,11 +32,11 @@ Each time you [`track`](/docs/connections/spec/track) an event from the browser
 
 You can find your conversion pixel IDs after you create the single conversion event inside Twitter:
 
-![](images/cS23YRgfUy9.png)
+![A screenshot of a single conversion event in Twitter, with a box around the conversion pixel ID.](images/cS23YRgfUy9.png)
 
 For example, if your mapping in Segment looks like this:
 
-![twitter conversion event mapping screenshot](images/event-mapping.png)
+![Twitter conversion event mapping screenshot.](images/event-mapping.png)
 
 Then every time you make this [`track`](/docs/connections/spec/track) call (from the browser):
 

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

@@ -16,16 +16,16 @@ Enabling Vitally as a destination in Segment can be done in one click from your
 
 1. Navigate to the Segment integration page within your Vitally account. This can be found in your **Account Settings** in Vitally by navigating to the **Product Data** integrations list.
 
-  ![](images/6fztyvS.png)
+  ![A screenshot of the Vitally Product Integrations page.](images/6fztyvS.png)
 
 2. In a separate tab/window, make sure you are logged into your Segment account
 3. Configure the Segment integration using the one-click "Enable with Segment" button. Choose the primary source of product usage data in Segment and Segment will automatically create a destination for Vitally:
 
-  ![](images/uGHrIvX.gif)
+  ![An animation where a user clicks the Configure button, selects Segment, clicks Enable with Segment, and is able to connect to the Segment app.](images/uGHrIvX.gif)
 
 4. You'll now be able to see and manage your Vitally Destination directly from your Segment workspace
 
-  ![](images/2JQwIBK.png)
+  ![A screenshot of the Segment Overview page, showing a Vitally destination.](images/2JQwIBK.png)
 
 5. Once Vitally receives at least one event from Segment, you'll be able to proceed with the set up process and configure how to [create accounts from Segment](https://docs.vitally.io/managing-the-customer-lifecycle/account-hierarchy-using-vitallys-organization-object/supported-integrations-and-how-to-create-the-hierarchy#segment){:target="_blank"}