Merge pull request #8301 from braze-inc/bd-3589

BD-3589 Update frequency capping screenshot and add ALT text to others

_docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md

@@ -40,15 +40,15 @@ Let's say we've created a segment named "Retargeting Filter Showcase" with a fil
 
 If you have other more targeted segments receiving notifications recently, you may not want your users to be targeted by more generic campaigns directed at this segment. Appending the "Last Received Push Campaign" filter to this segment, the user has ensured that if they've received another notification in the past 24 hours, they will slide out of this segment for the next 24 hours. If they still meet the other criteria of the segment 24 hours later and haven't received any more notifications they will slide back into the segment.
 
-![][1]
+![Segment Details section with the "Last Received Any Message" segment filter highlighted.][1]
 
 Appending this filter to all segments targeted by campaigns would cause your users to receive a maximum of one push every 24 hours. You could then prioritize your messaging by ensuring that your most important messages are delivered before less important messages.
 
 #### Setting a maximum user cap
 
 In the **Target Users** step of your campaign composition, you can also limit the total number of users that will receive your message. This serves as a check that's independent of your campaign filters, allowing you to freely segment users without worrying about over-spamming.
 
-![][2]
+![Audience Summary with a selected checkbox for limiting the number of people who receive the campaign.][2]
 
 By selecting the maximum user limit, you can limit the rate at which your users receive notifications on a per-channel basis or globally across all message types.
 
@@ -80,7 +80,7 @@ When targeting users during campaign creation, you can navigate to **Target Audi
 
 Note that non-rate-limited campaigns may exceed these delivery limits. However, be aware that messages will be aborted if they’re delayed 72 hours or more due to a low rate limit. If the rate limit is too low, the creator of the campaign will receive alerts in the dashboard and by email.
 
-![][3]
+![Audience Summary with a selected checkbox for limiting the rate at which the campaign will end, and rate being 500,000 per minute.][3]
 
 As another example, if you are trying to send out 75,000 messages with a 10,000-per-minute rate limit, the delivery will be spread out over 8 minutes. Your campaign will deliver no more than 10,000 messages for each of the first seven minutes, and 5,000 over the last minute. 
 
@@ -152,7 +152,7 @@ This time frame can be measured in minutes, days, weeks (seven days), or months,
 
 Each line of frequency caps will be connected using the `AND` operator, and you can add up to 10 rules per workspace. In addition, you may include multiple caps for the same message types. For instance, you can cap users to no more than one push per day and no more than three pushes per week.
 
-![][14]
+![Frequency capping section with lists of campaigns and Canvases that rules will and will not apply to.][14]
 
 ### Delivery rules
 
@@ -168,7 +168,7 @@ By default, new campaigns and Canvases that do not obey frequency caps will also
 This behavior changes the default behavior when you turn off frequency capping for a campaign or Canvas. The changes are backward compatible and do not impact messages that are currently live.
 {% endalert %}
 
-![][18]
+![Delivery Controls section with Frequency Capping turned on.][18]
 
 Different channels within a multichannel campaign will individually count  the frequency cap. For instance, if you create a multichannel campaign with both push and email and have frequency capping set up for both of those channels, then the push will count toward one push campaign and the email message will count toward one email message campaign. The campaign will also count toward one "campaign of any type." If users are capped to one push and one email campaign per day and a user receives this multichannel campaign, then they will no longer be eligible for push or email campaigns for the rest of the day (unless a campaign ignores frequency capping rules).
 
@@ -197,7 +197,7 @@ This scenario uses the following frequency capping rules:
 - A user triggers the same campaign, `Campaign ABC` three times over the course of a week.
 - This user triggers `Campaign ABC` once on Monday, once on Wednesday, and once on Thursday.
 
-![]({% image_buster /assets/img/standard_rules_fnfn.png %})
+![Frequency Capping section with the rule of sending no more than 2 push notification campaigns/Canvas steps from all campaigns/Canvas steps to a user every 1 week.]({% image_buster /assets/img/standard_rules_fnfn.png %})
 
 **Then, the expected behavior is that:**
 
@@ -218,7 +218,7 @@ You can also combine regular frequency capping with frequency capping by tags. C
 1. No more than three push notification campaigns or Canvas components per week from all campaign and Canvas steps. <br>**AND**
 2. No more than two push notification campaign or Canvas components per week with the tag `promotional`.
 
-![][12]
+![Frequency Capping section with two rules limiting how many push notification campaigns/Canvases can be sent to a user every 1 week.][12]
 
 As a result, your users will receive no more than three campaign sends per week over all campaigns and Canvas steps and no more than two push notification campaigns or Canvas components with the tag `promotional`.
 
@@ -233,7 +233,7 @@ When rules conflict, the most restrictive, applicable frequency capping rule wil
 1. No more than one push notification campaign or Canvas component per week from all campaign and Canvas components. <br>**AND**
 2. No more than three push notification campaigns or Canvas components per week with the tag `promotional`.
 
-![][11]
+![Frequency Capping section with conflicting rules to limit how many push notification campaigns/Canvas steps are sent to a user every 1 week.][11]
 
 In this example, your user will not receive more than one push notification campaign or Canvas components with the tag "promotional" in a given week, because you've specified that users should not receive more than one push notification campaign or Canvas component from all campaigns and Canvas components. In other words, the most restrictive applicable frequency rule is the rule that will be applied to a given user.