Automation
Re-engagement planning for inactive users without damaging sender reputation.
Sync Users10 imports
Main users database
https://be-admin.myloves.com/api/all-users
Last sync
14 May 2026, 05:02 · next planned 14 May 2026, 11:02
Latest Imports10 runs
| Started | Status | Imported | Error |
|---|---|---|---|
| 14 May 2026, 11:03 | running | 68,454 / 69,500 | — |
| 14 May 2026, 04:08 | completed | 198,745 / 206,006 | — |
| 13 May 2026, 21:13 | completed | 198,713 / 205,974 | — |
| 13 May 2026, 14:16 | completed | 198,533 / 205,793 | — |
| 13 May 2026, 07:16 | completed | 198,507 / 205,762 | — |
| 13 May 2026, 00:21 | completed | 198,494 / 205,749 | — |
| 12 May 2026, 17:25 | completed | 198,467 / 205,723 | — |
| 12 May 2026, 10:30 | completed | 198,286 / 205,536 | — |
| 12 May 2026, 03:35 | completed | 198,268 / 205,519 | — |
| 11 May 2026, 20:38 | completed | 198,244 / 205,494 | — |
Automation Flow & Safe Rollout Guideflow active
Automation Re-Engagement
Route: /api/send/automation
Template
Automation Hot Members
Routing
Auto provider · Auto sender
Do not blast 100k
Start with 0.25% or max 500/day, whichever is lower. Pause when bounce/complaint hints rise.
Use dedicated automation provider
Create a separate SES provider/sender for automation so old inactive users do not damage transactional sending.
Segment by domain
Send Gmail, Yahoo and Microsoft separately. Use Provider excluded domains if one domain starts failing.