Return to Answer

added 135 characters in body

Source Link

edited Dec 19, 2022 at 13:28

4.7k
1
12
27

In my opinion, the solution provided by Zuzanna is the way to go in your case. But I'll drop some other options just in case:

1- Use send throttlingsend throttling. Send Throttle sends emails during the hours you specify every day, starting the daywhen you send the email until all emails sendare sent. Not very suited to your use case, but it can be added as a security layer to avoid sending too many emails simultaneously.

You can use Send Throttling for these reasons:

To control inbound traffic to a website caused by the interest generated from an email. High inbound traffic can result in server crashes due to too many people visiting.

To limit the number of emails sent to a particular domain each hour.

2- Use Wait by attribute activityWait by attribute activity. In this case, you need to do the segmentation outside of Journey Builder using SQL for exampleyou need to do the segmentation outside of Journey Builder using SQL for example.

Resources:

In my opinion, the solution provided by Zuzanna is the way to go in your case. But I'll drop some other options just in case:

1- Use send throttling. Send Throttle sends emails during the hours you specify every day, starting the day you send the email until all emails send.

You can use Send Throttling for these reasons:

To control inbound traffic to a website caused by the interest generated from an email. High inbound traffic can result in server crashes due to too many people visiting.

To limit the number of emails sent to a particular domain each hour.

2- Use Wait by attribute activity. In this case, you need to do the segmentation outside of Journey Builder using SQL for example.

Resources:

In my opinion, the solution provided by Zuzanna is the way to go in your case. But I'll drop some other options just in case:

1- Use send throttling. Send Throttle emails during the hours you specify every day, starting when you send the email until all emails are sent. Not very suited to your use case, but it can be added as a security layer to avoid sending too many emails simultaneously.

You can use Send Throttling for these reasons:

To control inbound traffic to a website caused by the interest generated from an email. High inbound traffic can result in server crashes due to too many people visiting.

To limit the number of emails sent to a particular domain each hour.

2- Use Wait by attribute activity. In this case, you need to do the segmentation outside of Journey Builder using SQL for example.

Resources:

Source Link

created Dec 19, 2022 at 13:23

Rachid Mamai

4.7k
1
12
27

In my opinion, the solution provided by Zuzanna is the way to go in your case. But I'll drop some other options just in case:

1- Use send throttling. Send Throttle sends emails during the hours you specify every day, starting the day you send the email until all emails send.

You can use Send Throttling for these reasons:

To control inbound traffic to a website caused by the interest generated from an email. High inbound traffic can result in server crashes due to too many people visiting.

To limit the number of emails sent to a particular domain each hour.

2- Use Wait by attribute activity. In this case, you need to do the segmentation outside of Journey Builder using SQL for example.

Resources: