A page developer is responsible for setting the fireContentEvent and fireContentTypeEvent parameters for a given targeter. When these parameters are set to true and a user views the content rendered from the targeter, the site fires an event. Another component is designed to listen for the event and update the profile property.
For example, when you click a fund on the fundslist page, the system does the following:
Sets the
ElementIDto the fund’s XML file.Opens the fund page.
Passes the
ElementIDto the fund page so that it displays the text in the XML file.
The fund page opens (displaying the fund-specific text) and it fires an event (fireContentEvent and fireContentTypeEvent) that contains the ElementIdaggressiveIndex value. A listener receives the event and adds that index value to the user’s aggressiveIndex profile property.
To examine the fireContentEvent and fireContentTypeEvent parameters, open fund.jsp in <ATG2007.3dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/en. A search in this file for either parameter renders no results. The default value of these parameters is true, so a page without a value for them behaves as if they were set to true.
