Minute-by-Minute Scheduling: Limitations of Mergo's Row by Row Feature

Due to Google-imposed limitations, Mergo's ability to interact with and process information from your spreadsheet is restricted to once per hour. This constraint impacts the functionality of the Row by Row feature, leading to a potential delay in the execution of scheduled email campaigns.

Understanding Delays in Row Processing

When deploying Mergo's Row by Row functionality for your email campaigns, a noticeable gap might emerge between the time you set for each row's dispatch and when it is actually processed. The root cause of this gap is Google's restriction, allowing Mergo to check for updates in Google Sheets solely on an hourly basis. Consequently, it's possible for up to an hour to elapse from the moment you schedule a message for sending to the point Mergo is able to action it. Although not ideal for every scenario, we seek your understanding regarding these limitations dictated by the platform. For any inquiries or support in scheduling, our customer service team is at your disposal.

Minute-by-Minute Scheduling: Leverage Mergo Throttling Mechanism

If you've set up your email campaign expecting to send messages at precise, minute-by-minute intervals but then observed them being sent almost at the same time, this outcome stems from the same Google restrictions. Mergo's once-hourly access to Google Sheets means that it is better suited for scheduling emails around a specific hour rather than for exact timing within an hour.

Instead it is better to leverage Mergo throttling mechanism. This feature intelligently spaces out email deliveries, mimicking human-like sending patterns to reduce the likelihood of triggering spam filters. The throttling mechanism effectively counters the need for minute-by-minute scheduling by adjusting the dispatch rate of emails to optimize inbox placement. This strategic pacing benefits users by improving email visibility and engagement without the need for intricate scheduling configurations.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.