alttext

- Cliff
- Facebook Offline Conversions
- Freshmarketer
- Freshsales
- Gainsight PX
- Google Ads (Classic)
- Gtag
- Hubspot

Author: forstisabella

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

@@ -16,10 +16,10 @@ This destination is maintained by Cliff.ai. For any issues with the destination,
 3. Name your integration and click **Authorise Segment**.
 4. Select your Workspace and Source and click **Allow**.
 5. [Create a Data Stream on Cliff](https://app.cliff.ai/apps/anomaly-detection/data-streams/create-streams). Choose which Segment events and dimensions to start monitoring. Enter the name of the event and click the blue **+** button. Repeat to add dimensions. Click **Continue**.
-   ![](images/cliff1.png)
+   ![A screenshot of the Cliff data stream configuration page](images/cliff1.png)
    **Note**: Cliff ingests _only_ the events you select in this screen.
 6.  Select how often Cliff should batch the data that Segment sends.
-![](images/cliff2.png)
+![A screenshot of the CLiff scheduling page](images/cliff2.png)
 
 
 ## Track

src/connections/destinations/catalog/facebook-offline-conversions/index.md

@@ -31,23 +31,23 @@ This page is about the **Facebook Offline Conversions**. For documentation on ot
 
 3. Authorize Segment to send data on your behalf by connecting through OAuth:
 
-![](images/8acf724eb5cf484f29f4dd278ccbd118.png)
+![A screenshot of the Facebook Offline Conversions page in the Segment app, with an orange arrow pointing to the Connect to Facebook Offline Conversions button](images/8acf724eb5cf484f29f4dd278ccbd118.png)
 
 By doing so, we will ask for `ads_management` and `public_profile` access scopes which will allow Segment to have proper permissions to send offline events to your Event Sets. You can read more about Facebook's [access and authentication](https://developers.facebook.com/docs/marketing-api/access) if you would like to know exactly what these scopes allow.
 
 **IMPORTANT**: Note that the Segment user that is OAuthing **MUST** have admin access in your company's Facebook Business Manager account. Otherwise, the authorization will fail.
 
 Once you complete the OAuth flow, you should be connected.
 
-![](images/24d08a8543ebba566cc2b694108239eb.png)
+![A screenshot of the Connection Settings page in Segment, showing that the Facebook OfflineConversions app is connected and authorized](images/24d08a8543ebba566cc2b694108239eb.png)
 
 _Note_: Once we retrieve your access token, they should not expire. However, if for whatever reason you are not seeing conversions come through you should check your destination settings and you should reauthorize.
 
 4.  You **MUST** map the name of every Segment `track` event that you'd like to send and the corresponding ID of the Event Set where you want to send the conversions to. This is to avoid sending unwanted `track` events as conversions.
 
 You can find Facebook Offline Event Set ID by going to your **Offline Events** page in your Facebook **Business Manager** account and clicking the desired Offline Event Set here:
 
-![](images/wSeG1P9SSI.gif)
+![An animation showing the process of finding your Facebook Offline Event Set ID, as outlined in the above paragraph](images/wSeG1P9SSI.gif)
 
 ## Track
 
@@ -68,15 +68,15 @@ There are 3 places you can map your Segment `track` events:
 
 1) Map `track` events to Facebook's `CompleteRegistration` conversions:
 
-![](images/32b565e6457f9c2949af26f4c859afc9.png)
+![A screenshot of the settings tab for the Facebook Offline Conversions destination, with a "Signed Up" event mapped to a Facebook Offline Event Set](images/32b565e6457f9c2949af26f4c859afc9.png)
 
 2) Map `track` events to Facebook's `Lead` conversions:
 
-![](images/1a188c55dd892543e2b8b6602459130f.png)
+![A screenshot of the settings tab for the Facebook Offline Conversions destination, with a "Lead Generated" event mapped to a Facebook Offline Event Set](images/1a188c55dd892543e2b8b6602459130f.png)
 
 3) Map all other custom or ecommerce `track` events to any Event Set ID:
 
-![](images/86f8c50165a726e8168d652c8052c2a0.png)
+![A screenshot of the settings tab for the Facebook Offline Conversions destination, with a "Lead Generated" event mapped to a Facebook Offline Event Set](images/86f8c50165a726e8168d652c8052c2a0.png)
 
 The following table shows how we map Segment's [semantic ecommerce](/docs/connections/spec/ecommerce/v2) or custom event names to Facebook's semantic conversion event names:
 

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

@@ -57,12 +57,12 @@ You can find default list of field names in Settings - > Custom fields for field
 
 All attributes that are a part of traits should correspond to the field Label of those fields in Freshmarketer. Attributes that are not mapped with their corresponding fields are ignored.
 
-![](images/contact-fields.png)
+![A screenshot of the Contact fields page in Freshmarketer, with an "Edit Field" sidebar present](images/contact-fields.png)
 
 ### Custom Traits
 
 As part of traits, you can a Field Label to send custom fields created in Freshmarketer. Also, custom fields will not be automatically created. You have to create them with the exact name and type to map to your field in Freshmarketer before proceeding to send data from Segment.
 
 Below is the Custom Field created in Freshmarketer product(Settings > Contact fields). You can drag and drop a field to create a new one.
 
-![](images/custom-fields.png)
+![A screenshot of the Contact fields page in Freshmarketer, with an "Edit Field" sidebar showing a custom field](images/custom-fields.png)

src/connections/destinations/catalog/freshsales-suite-crm/index.md

@@ -71,7 +71,7 @@ However, Segment makes an exception for two attributes: `title` and `phone`, whi
 As part of traits, you can send custom fields created in Freshsales by using their internal names in camel case. You can find internal names in the corresponding field settings page. 
 
 Custom fields won't automatically create. You have to create them in Freshsales before proceeding to send data from Segment. [Learn more](https://crmsupport.freshworks.com/en/support/solutions/articles/50000002389-how-to-create-custom-fields-for-contacts-accounts-and-deals-){:target="_blank"} about creating custom fields in Freshsales.
-![](images/custom-traits.png)
+![A screenshot of the Freshsales edit field popup, with a custom field, Alternate Number, present](images/custom-traits.png)
 
 
 #### Objects

src/connections/destinations/catalog/gainsight-px/index.md

@@ -16,7 +16,7 @@ Our Gainsight PX destination code is open sourced on GitHub, feel free to check
 2. Search for "Gainsight PX" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. To find your Gainsight PX key, log into Gainsight PX and navigate to Settings > Products > Web App. If you have not already entered the URL for your web application, do that and click the Generate button. The Tag Key is the value to the right of the URL value. Use the "Copy" button to copy the value to your clipboard.
 
-   ![](images/TagKey.png)
+   ![A screenshot of the Gainsight PX Products tab, with a callout that says "Copy the value from your Aptrinsic Settings Screen"](images/TagKey.png)
 
 4. Paste the Gainsight PX Tag Key into the Segment connection settings API Key field.
 

src/connections/destinations/catalog/google-ads-classic/index.md

@@ -113,7 +113,7 @@ Authorization between an Google Ads (Classic) account and a third-party-applicat
 
 Once this step is complete, you should see a screen that looks like this showing the new Link Id:
 
-![](images/link-id-process.png)
+![A screenshot of Google Ads (Classic) showing Segment as an App analytics provider](images/link-id-process.png)
 
 #### Add your Link ID as an Integration Setting
 

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

@@ -95,11 +95,11 @@ To configure a custom dimension:
 
     In Segment:
 
-    ![](images/segment-dimension.png)
+    ![A screenshot of the Segment Custom Dimensions page, with Gender mapped to dimension 1 and User Type mapped to dimension 2](images/segment-dimension.png)
 
     In Google:
 
-    ![](images/ga-dimension.png)
+    ![A screenshot of the Google Custom Dimensions page, with Gender mapped to index 1 and User Type mapped to dimension 2](images/ga-dimension.png)
 
 
 > note ""
@@ -206,7 +206,7 @@ For all events that include product details you must pass either `name` or `prod
 
 To take full advantage of all the features of Enhanced Ecommerce, you'll want to take advantage of some specific events. The biggest differentiator between ecommerce and Enhanced Ecommerce is support for checkout steps. To take advantage of tracking your checkout funnel and measuring metrics like cart abandonment, you'll first need to configure your checkout funnel in the Google Analytics admin interface, giving readable labels to the numeric checkout steps:
 
-![](images/ga-checkout-steps.png)
+![A screenshot of the Google Enhanced Ecommerce setup flow, showing that Ecommerce is enabled and showing the four configured Ecommerce checkout-funnel steps](images/ga-checkout-steps.png)
 
 
 Then you'll instrument your checkout flow with `Viewed Checkout Step` and `Completed Checkout Step` events for each step of the funnel you configured in the Google Analytics admin interface, passing the step number and step-specific options through as a property of those events:
@@ -490,7 +490,7 @@ To populate the Site Search report in Google Analytics, complete the following s
 1. When someone searches on your site, you must add the search term they used to the URL query, like this: `domain.com?s=coconuts`. The key ("s" in this case) can be any letter or string of letters.
 2. In your Segment source destinations catalog open the Gtag settings, scroll down to the Page Call settings and make sure to check the box for **Include Query String**.
 3. Inside Google Analytics, go to the **Admin** section, then click **View Settings** for the view you want to add Site Search to. Turn on **Site search Tracking** and enter the string from #1 into the Query parameter field. In this example it'd look like this:
-![](images/ga-search-query.png)
+![A screenshot of Google Analytics' Site Search Settings, with site search tracking enabled and the Query parameter field displaying a parameter, "s"](images/ga-search-query.png)
 
 
 ### Webmaster tools

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

@@ -269,23 +269,23 @@ Engage sends **Account-Level data** to HubSpot using **Identify** calls to add a
 
 1. Create your audience criteria and preview the audience in Segment. Click Select Destinations.
 
-   ![](images/hubspot-personas01.png)
+   ![A screenshot of the Segment Configure and Preview Your Audience page, showing an audience created for all users who opened at least one email over the last 30 days](images/hubspot-personas01.png)
 
 2. Next, select HubSpot as a destination for the audience in Segment. Use the default settings, which send an Identify call to mark users as members of an audience or when they have a specific trait. <!-- some clarifying changes coming here in a future update, per Dadson.-->
 
-   ![](images/hubspot-personas02.png)
+   ![A screenshot of the Hubspot destination page in Segment, with the Send Identify setting selected](images/hubspot-personas02.png)
 
 3. Enter a name for the audience, and a description.
    Write down the **Audience key** (you'll need this to configure HubSpot in the next step), but don't click **Create Audience** yet.
-   ![](images/hubspot-personas03.png)
+   ![A screenshot of the last step in the Configure and Preview Your Audience setup flow, with a red arrow pointing to the audience key](images/hubspot-personas03.png)
 
 
 4. Go to your HubSpot Settings.
 5. Create a new `property` in HubSpot for each audience you want HubSpot to receive from Engage.
    This is required because HubSpot's schema is explicitly defined.
    You must do this *before* you send any Engage data from Segment to HubSpot.
 
-   ![](images/hubspot-personas04.png)
+   ![A screenshot of the Settings page in Hubspot, with a green arrow pointing to the "Create a property" button](images/hubspot-personas04.png)
 
 
 6. Set the object type.
@@ -298,14 +298,14 @@ Engage sends **Account-Level data** to HubSpot using **Identify** calls to add a
 > The audience label's “internal name” in HubSpot *must exactly match* the Segment  `audience key`. You can check this by clicking the `</>` icon to the right of the Label field, and making corrections.
 
 
-   ![](images/hubspot-personas05.png)
+   ![A screenshot of the "Create a new property" setup flow in Hubspot, with a green arrow pointing to the code icon next to the Label field](images/hubspot-personas05.png)
 
 8. On the next screen, set the **Field type** for audiences to `Single Checkbox`. (This represents a boolean value that indicates audience membership.)
    (For computed traits, depending on whether the output is a string or number, select `Single-line text` or `Number`.)
 
    Click **Create** to finish adding the audience contact property.
 
-   ![](images/hubspot-personas06.png)
+   ![A screenshot of the final step in the "Create a new property" setup flow in Hubspot, with the field type set to Single checkbox](images/hubspot-personas06.png)
 
 
 9. Back in the Engage Audience builder, click **Create Audience**. Engage sends any users that meet the audience criteria to HubSpot immediately.
@@ -315,15 +315,15 @@ Engage sends **Account-Level data** to HubSpot using **Identify** calls to add a
 
 You can use the [Profiles Debugger](/docs/unify/debugger) to see the calls sent to HubSpot.
 
-![](images/hubspot-personas07.png)
+![A screenshot of the Profiles Debugger with a sample profile](images/hubspot-personas07.png)
 
 You can check back in HubSpot to see the audience boolean as a contact property. For the audience created in the example above, you could check individual contact profiles and see a contact property called  `Email Opened 30 Days` = `Yes`.
 
-![](images/hubspot-personas08.png)
+![A screenshot of the Hubspot Managed Properties settings page, with a green arrow pointing to the custom field "Email Opened 30 days" ](images/hubspot-personas08.png)
 
 You can also see this in the contact property history for each user record.
 
-![](images/hubspot-personas09.png)
+![A screenshot of the Property history for the profile present in the Profiles debugger, with the custom property "Email Opened 30 days" present](images/hubspot-personas09.png)