Automation
Re-engagement planning for inactive users without damaging sender reputation.
Sync Users8 imports
Main users database
https://be-admin.myloves.com/api/all-users
Last sync
12 May 2026, 18:20 · next planned 13 May 2026, 00:20
Latest Imports8 runs
| Started | Status | Imported | Error |
|---|---|---|---|
| 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 | — |
| 11 May 2026, 14:02 | completed | 106,913 / 113,105 | — |
| 11 May 2026, 13:37 | failed | 91,302 / 92,360 | Sync failed page 4619: 502 Bad Gateway |
| 11 May 2026, 13:27 | completed | 19,654 / 20,000 | — |
| 11 May 2026, 13:26 | failed | 0 / 0 | Sync failed page 1: 401 Unauthorized |
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.