Timing & Frequency in Automation

How fast should your "auto-pilot" fly? This section covers the importance of delays in your automation. Sending 5 emails in 1 day is annoying. Sending 5 emails over 2 weeks is nurturing. It's about giving the passenger time to read the last dispatch.

15 questions in this topic

How does timing affect deliverability? What’s the best time to trigger an automated email? How do you avoid sending multiple automations at once? How can triggers create frequency conflicts? How do throttling rules affect automated sends? What is a “frequency cap”? How does “send-time optimization” work in automation? What’s the difference between fixed delays and smart delays? How to avoid over-triggering after major events (purchases, unsubscribes)? How can time zones affect trigger performance? What’s “temporal engagement decay”? How can you detect automation loops or duplicates? Should automated emails be sent based on the user's time zone? How do I manage sending cadence within an automation workflow? Can users be in multiple automation workflows at once? How do I manage that?

Questions about Timing & Frequency in Automation