You can import actions into an existing, completed test on Portal by following the instructions in this user guide. It is important that you understand the limitations to importing data into the Portal, outlined at the end of this article.
- Formatting the CSV File
- Creating a Shell Campaign to Import Testing Data
- Importing into an Existing Test
Formatting the CSV File
This section shows how to properly format a CSV file containing actions.
The action fields you can import are email address, action type, IP address, user agent, and the date and time of the action. into a test. Of these fields, only the email address and the type of action are required fields. User agent, IP address, and the timestamp are not required.
In order for certain actions to properly map to actions as they are stored on the Portal platform, the actions will need to be entered in a specific way in the CSV file. The below table shows the proper mappings between what you enter in the CSV file and how the action will appear on Portal.
|If you want this action to show up on reports...||...then place this action (case-sensitive!) in the CSV File...|
|Clicked Link in Email||page-load|
|Viewed Landing Page||Viewed Landing Page|
|Viewed Training Page||Viewed Training Page|
|Completed Training Page Material||Completed Training Page Material|
An example file with actions is attached at the end of this article.
The acceptable timestamps formats are mm/dd/yyyy hh:mm:ss (example: 07/04/2017 08:06 or 07/04/2017 08:06:21) and mm/dd/yyyy hh:mm (example: 7/4/2017 8:06:22 or 7/4/2017 8:06:32). You may include or exclude seconds from the timestamp. If the timestamp is empty, then the sending time for the message in Portal will be used as the action time (you must import the data into an existing, completed test that the targets in your CSV file were part of, more on this in the next section).
Creating a Shell Campaign to Import Testing Data
Before you begin importing actions into an existing test, you must have a completed test inside the Portal. The best way to import actions from a previous provider is to create a shell campaign. Once you've chosen your group, choose the "-- Create a Shell Campaign to Import the Data Into --" option from the tests drop-down. Then, give your campaign a name.
On the next page you will need to choose which fields map to which columns in the CSV file.
A description of each column in the dropdowns is given below.
|Column in Import Wizard||Description|
(Required) The email address of the target that performed the action.
(Required) The action that the target performed.
Example: Viewed Landing Page
(Optional) The IP address from which the action occurred.
(Optional) The user agent from which the action came.
Example: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1
(Optional) The timestamp of the action. If this is not provided, then it will default to the send time of the email.
Example: 5/28/2021 8:01
Once you have mapped the fields from your CSV file to the fields to be stored in Portal, you may click "Import Now". At the end of the import process, if any of the actions could not be imported, an error file will be displayed that will allow you to view the reason the action(s) couldn't be added to the test.
NOTE: Actions cannot be updated. Once an action has been imported, you cannot later go back and change the data. So it is important that you are very careful to properly map the fields in the CSV file.
Importing into an Existing Test
Importing actions into a pre-existing test is similar to importing into a shell campaign, the only difference being that you choose the test to import your actions into instead of choosing the "-- Create a Shell Campaign to Import the Data Into --" option from the drop-down.
The actions you import into Portal will be matched to one one message sent in a phishing test per target. For this reason it is best that you only import actions into tests that have a one-to-one mapping between targets and emails sent (i.e. we recommend only importing actions into tests in which each target received just one email).
Targets must be both active in the group you are testing and active at the target level.