Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mini time audit #5319

Merged
merged 1 commit into from
Apr 27, 2023
Merged

Mini time audit #5319

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:**

Expand Down
2 changes: 1 addition & 1 deletion _docs/_user_guide/engagement_tools/campaigns/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down