Skip to main content
These events come from AutoPhish. Phishing campaigns you build yourself under Phishing campaigns don’t send webhook events. Every event arrives in the same envelope. This page describes data for each type. The examples are spread over several lines to make them readable. The Cimento SDKs have a type for each event’s data: see the payload types in the Go reference, or narrow on event.type in TypeScript.

Simulation outcomes

One event for each thing that happens to a simulation Cimento sent to an employee. All five share the same data. Activity that Cimento attributes to a mail scanner or bot, and not to the employee, doesn’t send an event.

phishing.simulation.delivered

The mail provider accepted a simulation for an employee’s mailbox.
Delivered means the mail provider accepted the message. It does not confirm the message reached the inbox.

phishing.simulation.opened

An employee opened a simulation: their mailbox shows the message as read. Sent at most once for each simulation. Cimento learns about an open by checking the mailbox, so this event can arrive some time after the employee read the message.

phishing.simulation.clicked

An employee clicked the link in a simulation. You can receive more than one of these for the same sendId, so count simulations or people, not events.

phishing.simulation.reported

An employee reported a simulation as phishing.

phishing.simulation.no_action

Seven days passed after a simulation was delivered with no click and no report.
This event arrives seven days after the simulation, not when it is sent. An employee who only opened the message still gets it. If they click after the seven days, you receive a clicked event as well.

Training after a click

phishing.remediation.completed

An employee finished the training they were given after a simulation.

The program

phishing.program.enabled

An admin turned phishing simulations on.

phishing.program.disabled

An admin turned phishing simulations off.

phishing.program.reset

An admin reset the phishing program to its setup state. data has the same fields as phishing.program.disabled.

Rounds

A round is one batch of simulations. period names the week or month it covers: 2026-W46 for a weekly round, 2026-11 for a monthly one. A round for new joiners has a period such as joiners-2026-11-12.

phishing.round.started

A round of simulations was planned and began sending.

phishing.round.skipped

An admin skipped a round of simulations.
A round that simply reaches the end of its period sends no event.

Exclusions

An excluded employee gets no simulations.
An exclusion with an end date that simply runs out sends no event. phishing.exclusion.removed is sent only when an admin removes an exclusion.

phishing.exclusion.added

An employee was excluded from phishing simulations, by an admin or by Cimento.
Excluding someone who is already excluded, or changing how long their exclusion lasts, sends no event.

phishing.exclusion.removed

An admin removed an employee’s exclusion from phishing simulations.