Triggers on target tables of any replication deserve special consideration, and Dbvisit Replicate is no exception. The concern is whether triggers defined on the target tables should fire when data changes are applied to the table. This depends on the logic in the trigger and thus has to be decided by the user.
In general, triggers carried over from source database are not intended to fire, but triggers created on apply should fire. But other criteria can be considered as well, e.g. whether other tables referenced in the trigger are replicated or not.
Dbvisit Replicate support
...
For for Oracle 10.2.0.5 and 11.2.0.2 and later:
...
On every MySQL target, you can check variable @is_dbreplicate_session (valued 0/1) to find out whether it's an apply session or not.
...