Timeline for Send throttling large list
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 29, 2021 at 14:56 | vote | accept | ac a | ||
| Jan 29, 2021 at 14:56 | vote | accept | ac a | ||
| Jan 29, 2021 at 14:56 | |||||
| Jan 29, 2021 at 13:31 | comment | added | Lukas Lunow | That’s correct @aca | |
| Jan 29, 2021 at 13:27 | comment | added | ac a | We do regularly send to same size audiences. It takes about 30 minutes indeed. @LukasLunow, if we set sending window 4 hours, will the sendout still complete around 30 mins? | |
| Jan 29, 2021 at 12:38 | comment | added | Jonas Lamberty | cool. i deleted my own answer about this, this would just have led to confusion. cheers | |
| Jan 29, 2021 at 12:24 | comment | added | Lukas Lunow | Good comment. I have updated my answer accordingly, @JonasLamberty | |
| Jan 29, 2021 at 12:16 | history | edited | Lukas Lunow | CC BY-SA 4.0 |
added 142 characters in body
|
| Jan 29, 2021 at 12:07 | comment | added | Jonas Lamberty | I agree there is never a guarantee. Suppose that similar sendouts have been done before in that account without taking HOURS to complete, say 13 mio have been observed in 30 minutes, simply not checking the "hourly threshold" option, but setting a window of, say, 4 hours, this would be a way to spread it, no? Basically, if you leave "hourly threshold" unchecked, no "cap" on the sending will be set other than performance limits, and the sending will be done as fast as possible (whatever that means for your configuration), just spread over multiple points in time, no? | |
| Jan 29, 2021 at 11:54 | history | answered | Lukas Lunow | CC BY-SA 4.0 |