How to Build Efficient Automations at Scale

Automations in User.com are an open system: the same result can be achieved in many different ways — more or less optimally. The following guidelines will help you avoid mistakes that may cause infrastructure overload or slow down campaign execution.

Mass campaigns = single campaigns

Always use campaigns (single) for mass sending.
The system processes, for example, 500,000 contacts much faster via the Campaigns module than through automation.
For scheduled email campaigns, filters are recalculated right before sending, ensuring your audience is always up to date.

Segment instead of filter

The segment block operates on cached data (recalculated and stored every few hours) and executes in just a few milliseconds.
The filter block, especially when applied to large tables (e.g. events or product events), may take several seconds to execute.
In large-scale automations, this can lead to system overload.

Fast vs slow queue

For mass processes (onDateOnTime, e.g. drip campaigns), add a “1 minute delay” block immediately after the trigger.
This signals the system to process it in the slow queue, preventing delays in real-time communication (popups, live messages).

Filter inside the trigger

Include all possible conditions directly within the onDateOnTime trigger. Avoid the structure: onDateOnTime (initial conditions) > filter (exclusions). Such a setup makes the system process two stages for contacts that ultimately perform no action: creating unnecessary server load.

Appropriate timing

Whenever possible, use “once” or “max once per day” timings.
This prevents unnecessary automation runs — for example, when most contacts stop at a capping filter.

Questions or doubts?

Contact us via chat or reach out to your dedicated Customer Success Manager.