The value of assigned users in campaigns with random sending is updated progressively as the sends are executed. Currently, this progress can be viewed directly in the campaign audit.
How is the Assigned Value Calculated?
In simulation campaigns (phishing or ransomware) with random sending, user assignment is not done at a single moment.
Instead:
Users are assigned progressively
Assignment occurs as the different sending batches are executed
This is because:
Sends are distributed at different times of the day
They take place within a defined time range
They can even extend over more than one day
Specifically, sending occurs in the first half of the configured date range (between the start date and the expiration date), within the hours of 9:00 AM to 6:00 PM.
How is it Currently Displayed?
The assignment progress can be checked from the campaign audit.
To view it:
Go to Campaigns > Calendar / Campaign List
Find the campaign and access the audit under "View campaign details"
Go to the tab "Information and actions"
There the progress is shown in the format:
Assigned X of Y (Z%)
For example, if the campaign was sent to 10 users and half of the users have already been sent in the sum of the batches, it will display: Assigned 5 of 10 (50%)
This allows you to know in real time:
How many users have already been assigned
How many remain pending
The percentage progress of the campaign
Difference with Campaigns Without Random Sending
In campaigns without random sending:
Assignment is done at a single moment (campaign start)
The assigned value is final from that moment
On the other hand, in campaigns with random sending:
The assigned value evolves over time
It depends on the execution of each sending batch
Considerations
The assigned value can vary during the execution of the campaign
Progress will depend on the scheduling of the sends
This behavior is expected and is part of the random sending logic
💡 Best Practices
Check progress from the "Information and actions" tab to monitor the campaign
Consider the time range and dates when analyzing assignment progress
Avoid directly comparing random campaigns with immediate send campaigns