From 19b87ee8560547958a9ce2c7c0227ad104fe1445 Mon Sep 17 00:00:00 2001 From: Lydia Xie <lydia.xie@braze.com> Date: Wed, 26 Apr 2023 15:33:04 -0700 Subject: [PATCH] mini time audit --- .../campaigns/building_campaigns/rate-limiting.md | 4 ++-- _docs/_user_guide/engagement_tools/campaigns/faq.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md index b843e6c5589..3257202fad5 100644 --- a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md +++ b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md @@ -214,8 +214,8 @@ Consider the following campaigns and frequency capping by tag rule: **Campaigns**: -- **Campaign A** is a push campaign tagged as `promotional`. It is slated to send at 9:00 AM on Monday. -- **Campaign B** is a push campaign tagged as `promotional`. It is slated to send at 9:00 AM on Wednesday. +- **Campaign A** is a push campaign tagged as `promotional`. It is slated to send at 9 am on Monday. +- **Campaign B** is a push campaign tagged as `promotional`. It is slated to send at 9 am on Wednesday. **Frequency Capping by Tag Rule:** diff --git a/_docs/_user_guide/engagement_tools/campaigns/faq.md b/_docs/_user_guide/engagement_tools/campaigns/faq.md index 74bd37fd81a..d1d48369770 100644 --- a/_docs/_user_guide/engagement_tools/campaigns/faq.md +++ b/_docs/_user_guide/engagement_tools/campaigns/faq.md @@ -68,7 +68,7 @@ For a user to be eligible for entry, they must be eligible for both checks. For Note that the user needs to be in the segment for 24 hours prior to the launch. If the user is not eligible in the first check, then Braze will not attempt the second check. -For example, if a campaign is scheduled to be delivered at 7 PM UTC, we start queuing the campaign sends as soon as a time zone is identified (such as Samoa). This means we're getting ready to send the message, not that we send the campaign out. If users then don't match any filters when we check eligibility, they won't fall in the target audience. +For example, if a campaign is scheduled to be delivered at 7 pm UTC, we start queuing the campaign sends as soon as a time zone is identified (such as Samoa). This means we're getting ready to send the message, not that we send the campaign out. If users then don't match any filters when we check eligibility, they won't fall in the target audience. As another example, say you want to create two campaigns scheduled to send on the same day—one in the morning and one in the evening—and add a filter that users can only receive the second campaign if they've already received the first. With local time zone delivery, some users may not receive the second campaign. This is because we check eligibility when the user's time zone is identified, so if the scheduled time hasn't occurred in their time zone yet, they haven't received the first campaign. Therefore they won't be eligible for the second campaign.