Most of the events described above can be turned on or off by the developers working on your site. For example, the Visits event is triggered by (“fired by”) the targeted servlet beans that developers insert into content pages (JHTML or JSP files). If a developer turns off event firing for a targeted servlet bean on a specific page, and a site visitor displays that page, any Visits events you have set up for that page will not be triggered, and the visitor will not progress to the next scenario element as you had planned.
If you find that an event does not seem to work, check that event firing is turned on for that event. Refer to Using Scenario Events in the ATG Personalization Programming Guide for more information.
