The table below provides some information on supplying parameters for specific ATG Outreach events.
Event | Configuration |
|---|---|
A Form Is Submitted | Can be configured to fire when any form is submitted, or when a specified form is submitted. To specify a form, type the name of the form as it appears in the JSP page. Example: |
An Email Is Received | Can be configured to fire when any e-mail is received, or when an e-mail with specific properties is received. If appropriate, select the properties of the e-mail that you want to trigger the event. Example: |
Logs In | No parameters. This event is triggered when a registered user logs into the site. |
Logs Out | No parameters. This event is triggered when a registered user logs out. |
Profile Property Updated by User | Can be configured to fire when any profile property is changed, or when a specified property is changed. Note that you cannot specify the value to which the property is changed, only that the property has a different value. For example, you can create an event that is fired when a user changes her Receive Email property, but you cannot specify that the event should be fired only when the property is changed to No. |
Registers | No parameters. This event is triggered when a user registers at your site (typically by completing a registration form). |
Switches Site Context | This event is triggered when a customer navigates from one Web site to another, usually by following a link. Note that the event is designed only for use with sites supported by a multisite ATG installation (sites registered and deployed through Site Administration). This event is available only for site-specific campaigns. |
User Opted Out | This event is triggered when a customer chooses to opt out of all e-mails (global opt-out). In technical terms, global opt-out occurs when a customer submits a form that changes his or her Receive Email profile property from Yes to No. |
Views (an item on a page) | Can be configured to fire when any repository item is viewed; when any item from a given repository is viewed; or when a specific item is viewed. Examples: In the example, Claimable is the name of the repository. |
Visits (a page) | Can be configured to fire when any page is displayed; when any page in a given folder is displayed; or when a specific page is displayed. For more information, see Adding a Visits (Page) Event. |
For information on Commerce events, refer to the ATG Commerce Guide to Setting Up a Store.
A Note about Promotion Events: If you use the ACC to view the scenario that is generated for a campaign containing a Promotion Offered or Promotion Revoked event, and the event contains a specific promotion ID, the scenario appears to be incomplete -- specifically, the element that represents the promotion event appears in red with the text “Promotion offered\revoked and product named (no product specified)”. This behavior occurs because the event picker code required to configure this event in the Business Control Center does not exist in the older ACC. Despite the apparent error, however, the campaign works as designed.
