Skip to main content

Automatic Campaign Closure

Auto-termination of phishing campaigns

Updated over a month ago

This article explains how to configure automatic closure of campaigns, ensuring that results are computed consistently and without manual intervention.


1 – Objectives

  • Automate the closure of campaigns after all emails have been sent

  • Define a clear delay between the end of sending and final data computation

  • Ensure consistent analysis of data for employees, groups, and the entire organisation


2 – Prerequisites

  • Access to the Settings section of the Arsen platform

  • Admin rights to modify campaign parameters


3 – Manage automatic closure settings

3.1 – Access campaign settings

  • Click your company logo (top-right of the screen)

    Arsen dashboard with user menu expanded, showing account management options.

  • Click Campaigns Settings

    Phishing campaign settings in Arsen showing the auto-termination option and whitelisting information.

3.2 – Understand how automatic closure works

Automatic closure occurs after a defined delay, starting when a campaign enters processing (after all emails have been sent).

Table of active phishing campaigns in Arsen with one in runnnig status and one in procession status

A campaign moves to Completed only once this delay has passed.

Table of completed phishing campaigns in Arsen, showing examples such as Facebook Security Alert, Deezer Suspended Account and Microsoft Teams New Meeting.

The countdown begins as soon as the last campaign email is delivered.

3.3 – Adjust the closure delay

  • Go to Auto-Terminate Campaigns

  • Use the slider to define the delay between the end of sending and automatic closure

Auto-termination delay slider in Arsen set to 11 days.

This setting applies only to future campaigns. Campaigns already underway are not affected.

When the delay expires, Arsen performs automatic computation in the following order:

  1. the campaign

  2. each employee

  3. the entire organisation

  4. each group

⚠️ Warning

  • The default delay is 7 days.

  • This corresponds to the period after which Arsen no longer collects compromise events (clicks or credential submissions).

  • This ensures a complete and representative analysis of employee behaviour.

Did this answer your question?