-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distinguish load embedded picture and open email #332
Comments
The opened metric is a tough one. We have decided that any user that clicks on the phishing link will automatically increment the opened metric as well. We also will increment the opened metric if the user has loaded all the remote content. This really isn't an accurate metric because it all depends on the email client that people are viewing with. Some clients will automatically load remote content where some will not. So really the metric is going to be inaccurate to some extent for the most part no matter how you look at it. |
Hi, I understand this. As I work on professional phishing simulation, I think in most case, I will have a certain insurance for the mua and his configuration. Maybe some time I will recalculate the statistics directly on Apache log, so I can use appropriate rules according to my client situation. Thanks you for your answer. Regards,Fraf
|
You bring up a good point. Perhaps it makes sense to have two separate metrics. 1 for Emails Opened Explicitly, and one that is an Assumed Opened Metric using clicks to factor in the result. |
I would rather say 1 for embedded content loaded and 1 for email assumed opened. |
Hi,
The code flag an email "opened" if the embedded link is open. This is logical : to click on the link, an user must have open the email.
The same flag "opened" is used if the user loads embedded image (pixel tracking).
It would be great to distinguish the 2 actions because they not have the same meaning in analyze for a client and can drive to different messages in future sensibilisation actions.
Regards,
fraf
The text was updated successfully, but these errors were encountered: