alt text for amazon personalize, azure function, braze

Author: forstisabella

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

@@ -579,31 +579,31 @@ To create a personalize dataset group:
 
 14. Find the location of the CSV file you generated in the earlier steps. This needs to be configured in the **Data Location** field on this screen.
 
-    ![](images/PersonalizeImportJob.png)
+    ![A screenshot of the Import user-item interaction data, with the Data Location field visible](images/PersonalizeImportJob.png)
 
 15. After clicking the **Finish** button at the bottom of the page, you'll return to the Personalize Dashboard where you can monitor the progress of your interaction dataset as it is being created.
 
 Be patient as this process can take a long time to complete.
 
-![](images/PersonalizeInteractionDatasetCreating.png)
+![A screenshot of the Dataset groups dashboard, with a red box around the status of the dataset upload (Create in progress)](images/PersonalizeInteractionDatasetCreating.png)
 
 ### Create Personalize Solution
 
 Once Segment's event CSV is finished importing into a user-item interaction dataset, Segment can create a Personalize Solution. To do this:
 
 1. From the Dashboard page for the dataset group created above, click **Start** in the **Create solutions** column.
 
-    ![](images/PersonalizeCreateSolution.png)
+    ![A screenshot of the Dataset groups dashboard, with a red box around the Start button in the Create solutions column](images/PersonalizeCreateSolution.png)
 
 2. On the **Create solution** page, enter a **Solution name**.
   * For a discussion on the different recipes you can use with Personalize, see [here](https://docs.aws.amazon.com/personalize/latest/dg/working-with-predefined-recipes.html){:target="_blank"}.
 
-    ![](images/PersonalizeSolutionConfig.png)
+    ![A screenshot of the Create solution page, with a solution name entered in the Solution name field.](images/PersonalizeSolutionConfig.png)
 
 
 3. Click **Finish** to create your Solution. This process can take several minutes to several hours to complete.
 
-    ![](images/PersonalizeSolutionInProgress.png)
+    ![A screenshot of the Dataset groups dashboard, with a red box around the status of the solution creation (Create in progress)](images/PersonalizeSolutionInProgress.png)
 
 ### Create Personalize Campaign
 
@@ -613,16 +613,16 @@ To create a Personalize campaign:
 
 1. From the Dataset Group Dashboard, click **Create new campaign**.
 
-    ![](images/PersonalizeCreateCampaignDash.png)
+    ![A screenshot of the Dataset Group Dashboard, with a red box around the Create new campaign button in the Launch Campaigns column](images/PersonalizeCreateCampaignDash.png)
 
 2. Enter the name for your campaign.
 3. Select the solution you created above and click **Create campaign**.
 
-    ![](images/PersonalizeCreateCampaign.png)
+    ![A screenshot of the Create new campaign page, with a campaign name entered and a solution selected (the solution created above)](images/PersonalizeCreateCampaign.png)
 
 4. Personalize will start creating your new campaign. This process can take several minutes.
 
-    ![](images/PersonalizeCampaignCreating.png)
+    ![A screenshot of the overview page for the campaign created in the previous step, with a blue banner reading "Campaign creation in progress..."](images/PersonalizeCampaignCreating.png)
 
 
 In the next section, Segment will build a real-time clickstream ingestion pipeline that accepts events from Segment and can query the solution you just deployed.
@@ -675,7 +675,7 @@ To create an IAM role:
 4. Search for and click on your new roles from the [IAM home](https://console.aws.amazon.com/iam/home#/home){:target="_blank"}.
 5. Select the **Trust Relationships** tab, then click **Edit trust relationship**.
 
-    ![](images/LambdaTrustRelationship.png)
+    ![A screenshot of the Trust Relationships tab, with the Edit trust relationship button visible](images/LambdaTrustRelationship.png)
 
 6. Copy and paste the following into your trust relationship. You should replace `<your-source-id>` with either the Source ID of the attached Segment source (the default) or the custom external ID you set in your Amazon Lambda destination settings.
 
@@ -722,7 +722,7 @@ To build a Lambda function to process Segment events:
 1. Go to the Lambda service page in your AWS account.
 2. Click **Create a function** to create a new function.
 
-    ![](images/LambdaDashboard.png)
+    ![A screenshot of the Lambda service page in AWS, with a red 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.
 
@@ -733,7 +733,7 @@ To build a Lambda function to process Segment events:
 
 7. Click **Create function**.
 
-    ![](images/LambdaCreateFunction.png)
+    ![A screenshot of the Create a function settings, with a function name, runtime, permissions, and role name entered](images/LambdaCreateFunction.png)
 
 
 **Lambda Function Source Code**
@@ -745,7 +745,7 @@ To build a Lambda function to process Segment events:
 
 You should now be able to see the code (and associate folders) in the code editor.
 
-![](images/LambdaFunctionCode.png)
+![A screenshot of the Lambda code editor](images/LambdaFunctionCode.png)
 
 Segment will call your lambda once per event.  The provided code maps Segment event fields from the Segment event it gets, and sends them to your Personalize Tracker. It then calls Personalize to get a recommendation for the userId in the event, and pushes that recommendation back as a user trait into Segment, using the `identify` call.
 
@@ -803,11 +803,11 @@ You need to modify the IAM Role & Policy originally created with this Lambda to
 
 1. From the **Execution role** section of your Lambda function, click the **View the <your-role-name>** link.
 
-    ![](images/ExecutionRoleIAM.png)
+    ![A screenshot of the execution role settings section on your Lambda](images/ExecutionRoleIAM.png)
 
 2. Click the arrow next to your policy in this role, then **Edit Policy**.
 
-    ![](images/EditPolicy.png)
+    ![A screenshot of the permissions policies settings section on your Lambda](images/EditPolicy.png)
 
 3. Add the code below to the existing permissions from within the JSON editor.
 4. Click **Review Policy** and **Save Changes**.
@@ -856,7 +856,7 @@ You need to create a Personalize Event Tracker for the Dataset Group you created
 
 3. Click **Create event tracker** button.
 
-    ![](images/PersonalizeCreateTracker.png)
+    ![A screenshot of the Event trackers settings page, with a red box around the Create event tracker button](images/PersonalizeCreateTracker.png)
 
 4. Enter a name for your Event Tracker.
 
@@ -938,16 +938,16 @@ You need to create a Personalize Event Tracker for the Dataset Group you created
           }
       ```
 
-      ![](images/PersonalizeEventTrackerConfig.png)
+      ![A screenshot of the Configure tracker setup page](images/PersonalizeEventTrackerConfig.png)
 
 
 6. The Event Tracker's tracking ID is displayed on the following page and is also available on the Event Tracker's detail page. Copy this value to your clipboard.
 
-    ![](images/PersonalizeEventTrackerCreating.png)
+    ![A screenshot of the Install the SDK page, with a red box around the Tracking Id value](images/PersonalizeEventTrackerCreating.png)
 
 7. Returning to the Lambda function, paste the Event Tracker's tracking ID into an Environment variable for the function with the key `personalize_tracking_id`.
 
-    ![](images/LambdaEnvVariable.png)
+    ![A screenshot of the key/value pairs under the Environment variables page, with the key personalize_tracking_id visible](images/LambdaEnvVariable.png)
 
 8. Add environment variables for Segment and for the function to tell it the Personalize Campaign to call for retrieving recommendations.
 
@@ -957,26 +957,26 @@ You need to create a Personalize Event Tracker for the Dataset Group you created
 
 11. Click on the campaign you created earlier and copy the **Campaign ARN** to your clipboard.
 
-    ![](images/PersonalizeCampaignArn.png)
+    ![A screenshot of the campaign overview page, with a red box around Campaigns in the side navigation](images/PersonalizeCampaignArn.png)
 
 
 12. Return to your Lambda function and scroll down to the **Environment variables** panel.
 
 13. Add an environment variable with the key `personalize_campaign_arn` and value of the Campaign ARN in your clipboard.
 14. Scroll to the top of the page and click **Save** to save your changes.
 
-    ![](images/LambdaRecCampaignArn.png)
+    ![A screenshot of the environmental variables panel, with a key/value pair of "personalize_campaign_arn" included](images/LambdaRecCampaignArn.png)
 
 15. You need a key for the Segment source that will get Segment's update events. Go back to your Segment workspace tab or window, and click on the source which will receive events from your Lambda, and copy the write key from the **Overview** tab.
 
-  ![](images/SegmentWriteKey.png)
+  ![A screenshot of a Source's overview panel in Segment, with a green arrow pointing to the Write Key field](images/SegmentWriteKey.png)
 
 
 16. Go back to your Lambda tab or window, and paste the key under a property called `connections_source_api_key`.
 
 _Make sure to click **Save**_ here or you will need to do this again.
 
-![](images/LambdaRecCampaignArn.png)
+![A screenshot of the environmental variables panel, with a key/value pair of "connections_source_api_key" included](images/LambdaRecCampaignArn.png)
 
 
 Your lambda is now ready to receive events from Segment.  Next, you will need to enable your Segment Personalize Destination.

src/connections/destinations/catalog/azure-function/index.md

@@ -24,42 +24,42 @@ To process events from Segment, first create a Azure Function that can handle yo
 
 
 1. Go to https://portal.azure.com, and click **Functions App**.
-   ![](images/azure1.png)
+   ![A screenshot of the Azure services dashboard, with an orange box around the Function Apps buttons](images/azure1.png)
 
 2. Click **+Add** to create your Function App.
-   ![](images/azure2.png)
+   ![A screenshot of the Function Apps dashboard, with an orange box around the "Add" button](images/azure2.png)
 
 3. Enter a name for your app in the **App name** field, and configure any other fields as needed own flavor.
 4. Click **Create**. Azure creates your new function app.
-   ![](images/azure3.png)
+   ![A screenshot of the Function App settings page, with blurbs point to the App Name field and the Create button](images/azure3.png)
 
 #### Create a new Azure function
 
 
 1. Click the new function app's name. (You might need to click the **Refresh** button if the new function doesn't appear.)
-   ![](images/azure4.png)
+   ![A screenshot of the Function App dashboard, with an orange box around the app you created above](images/azure4.png)
 
 2. On the left pane, click **Functions**.
-   ![](images/azure5.png)
+   ![A screenshot of the function dashboard, with an orange box around the Functions dropdown](images/azure5.png)
 
 3. In the main frame, click **New function**.
-   ![](images/azure6.png)
+   ![A screenshot of the function panel, with an orange box around the New function button](images/azure6.png)
 
 
 4. Choose **HTTP trigger**.
-   ![](images/azure7.png)
+   ![A screenshot of the new function setup page, with an orange box around the HTTP trigger box](images/azure7.png)
 
 5. Enter a name for your function, and choose `Function` for the **Authorization level** field.
-   ![](images/azure8.png)
+   ![A screenshot of the HTTP trigger setup panel, with a name entered in the Name field, Function chosen as the Authorization level, and an orange box around the Create button](images/azure8.png)
 6. Click `Create`.
 
 11. Set up your function code.
 12. In the created function screen, click on `</> Get function URL`.
-    ![](images/azure9.png)
+    ![A screenshot of the function panel, with an orange box around the "</> Get function URL" button](images/azure9.png)
 
 13. In the **Key** field, choose `default (Function key)`.
 14. Click **Copy** to the right of the URL. You'll use this URL to tell Segment where to connect to use this Azure Function.
-   ![](images/azure10.png)
+   ![A screenshot of the Get function URL popup, with an orange box around the "Copy" button](images/azure10.png)
 
 ## Configure Azure Function Destination
 

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

@@ -531,27 +531,27 @@ You can send computed traits created in Engage as `identify` calls to create cus
 
 For example, if you have a computed trait for “Last Product Viewed Item,” that would be named `last_product_viewed_item` in the user's Engage profile.
 
-![](images/last_viewed-user.png)
+![A screenshot of a user's Engage profile with the Computed Traits button selected](images/last_viewed-user.png)
 
 If the “Last Product Viewed Item” trait is connected to Braze to send `identify` calls, as in this example:
 
-![](images/last_viewed-identify.png)
+![A screenshot of the Last Product Viewed Item tab, with the Settings button selected](images/last_viewed-identify.png)
 
 The following custom attribute, “last_product_viewed_item” appears in Braze on the user's profile:
 
-![](images/last_viewed-id-braze.png)
+![A screenshot of the "last_product_viewed_item" attribute in Braze](images/last_viewed-id-braze.png)
 
 #### Computed Traits using Track calls
 
 You can also send computed traits created in Engage as `track` calls to create custom events in Braze. When Engage calculates a computed trait for a user, it sends a `Trait Computed` event to Braze.
 
 Using the same example as above, if a user has a computed trait for “Last Product Viewed Item” and the trait is connected to Braze and configured to send `track` calls:
 
-![](images/last_viewed-track.png)
+![A screenshot of the Braze settings tab in Segment, with the Send Track setting enabled and a Trait Computed value in the Compute Event field](images/last_viewed-track.png)
 
 The following custom event appears in Braze on the user's profile:
 
-![](images/last_viewed-track-braze.png)
+![A screenshot of a user's profile in Braze, with a Trait Computed event present](images/last_viewed-track-braze.png)
 
 > info "Tip"
 > You can change the name of the “computed trait” event that Braze receives in the Destination Settings accessed through Engage.
@@ -571,15 +571,15 @@ You can send audiences created in Engage as `identify` calls to create custom at
 
 For example, if a user is in a “Dormant Shoppers” audience:
 
-![](images/dormant-user.png)
+![A screenshot of a user's profile in Engage, with the Audiences tab selected and the "Dormant Shoppers" trait present](images/dormant-user.png)
 
 And the “Dormant Shoppers” audience is connected to Braze to send `identify` calls:
 
-![](images/dormant-identify.png)
+![A screenshot of the Braze settings tab in Segment, with the Send Identify setting enabled](images/dormant-identify.png)
 
 The “dormant_shoppers” custom attribute appears in Braze on the user's profile:
 
-![](images/dormant-identify-braze.png)
+![A screenshot of a user's profile in Braze, with a Trait Computed event present](images/dormant-identify-braze.png)
 
 
 #### Audiences using Track calls
@@ -588,11 +588,11 @@ You can also send audiences created in Engage as `track` calls to create custom
 
 Using the same example as above, if a user is in a “Dormant Shoppers” audience and the audience is connected to Braze to send `track` calls, Engage sends the following “Audience Entered” and “Audience Exited” events. (You can edit the names of these events from this screen.)
 
-![](images/dormant-track.png)
+![A screenshot of the Braze settings tab in Segment, with the Send Track setting enabled, Enter Event and Exit Event fields configured](images/dormant-track.png)
 
 The following custom event appears in Braze on the user's profile when they enter the audience:
 
-![](images/dormant-track-braze.png)
+![A screenshot of a user's profile in Braze, with an Audience Entered trait present](images/dormant-track-braze.png)
 
 > info "Tip"
 > You can change the name of the “Audience Entered” event that Braze receives in the Destination Settings accessed through Engage.
@@ -631,7 +631,7 @@ If you use the Braze destination in either [cloud or device mode](/docs/connecti
 
 By default, Engage data is sent to Braze by matching the `userId`. The Segment `userId` maps to Braze's External ID. If the user is anonymous and does not have a `userId`, you can also choose to send data using the `braze_id` auto-generated by Braze. To use `braze_id`, you must pass the `braze_id` to Segment as a [Segment externalId](/docs/unify/identity-resolution/externalids/) in the `context.integrations.Braze.braze_id` object. If `braze_id` is sent as an `externalId` **and** `userId` is missing, Engage matches on `braze_id` when sending to Braze. You can check the **Identities** tab on a user's Engage profile to confirm that `braze_id` was successfully picked up as an `externalId`.
 
-![](images/braze-anonid.png)
+![A screenshot of an anonymous user in Segment, with the Identities tab selected and a braze_id identity present](images/braze-anonid.png)
 
 You can find the `braze_id` in the Braze UI or by using Braze's [Users by Identifier API Endpoint](https://www.braze.com/docs/api/endpoints/export/user_data/post_users_identifier/){:target="_blank"}.