Quincy Funds Demo Documentation - Oracle · PDF fileOracle and Java are registered ... transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by

Version 10.1.2

Quincy Funds Demo Documentation

Oracle ATG

One Main Street

Cambridge, MA 02142

USA

ATG Quincy Funds Demo Documentation

Product version: 10.1.2

Release date: 12-17-12

Document identifier: QuincyFundsDemo1404301402

Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are

trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or

registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are

protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy,

reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any

means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please

report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the

following notice is applicable:

U.S. GOVERNMENT END USERS:

Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation,

delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and

agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any

operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and

license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended

for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or

hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures

to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in

dangerous applications.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties.

Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party

content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to

your access to or use of third-party content, products, or services.

The software is based in part on the work of the Independent JPEG Group.

ATG Quincy Funds Demo Documentation iii

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Exploring the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3. Touring Quincy Funds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Entering as a Guest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Registering as an Investor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Changing Your Profile and Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Changing Your Language Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Browsing as a Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Targeted E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Further Exploration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4. Tracking Visitor Interests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Exploring Tracking Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

How Tracking Affects a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Tracking for Page Developers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Tracking and Repositories for Programmers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5. Targeting Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Previewing a Page as Different Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Examining Targeting Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Targeting for Page Developers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Targeting for Programmers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6. Managing Visitors through Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Demonstrating a Simple Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Inspecting the PromoteSpecialSituations Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Demonstrating a Complex Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Inspecting the PromoteGrowthFund Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Scenarios Sharing Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Scenarios for Page Developers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Scenarios and Slots for Programmers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7. Repository Structure in the Quincy Funds Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Content Repository Loaders in the Quincy Funds Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Serving SQL Repository Items as org.w3c.Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

atg.xml.FileToDOMPropertyDescriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

atg.xml.PropertyToDOMPropertyDescriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

A. Additional Scenario Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Converting Members into Frequent Visitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Sending a Monthly Newsletter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Using Scenario Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Advertising a Seminar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

iv ATG Quincy Funds Demo Documentation

1 Introduction 1

1 Introduction

The Quincy Funds demo is designed to display the powerful Web site capabilities of Oracle ATG Web Commerce,

specifically the personalization and scenarios features of the ATG platform. The demo is a Web site for a

financial services company called Quincy Funds, whose marketing strategies include the presentation of highly

personalized site content that encourages visitors to invest in mutual funds.

The Quincy Funds site is designed to accommodate three types of visitors:

• Investors – registered customers of Quincy Funds

• Brokers -- fund managers who serve the customers

• Guests -- casual visitors who as yet have no formal connection with Quincy Funds

The primary goal of the Quincy Funds Web site is to convert guest visitors into registered investors. Ideally, these

investors will develop a long-term relationship with the company, visiting the site regularly and investing in a

variety of funds. Brokers support this effort by posting finance-related articles and monitoring investor activities.

In order to be successful, the Quincy Funds Web site needs to take into account the actual and perceived

benefits it can offer investors. Also, the site needs to accommodate customers with varying investment

strategies -- aggressive, moderate, and conservative -- and it needs to tailor initiatives for each type of investor.

Furthermore, it needs to adapt to the changing requirements of its visitors.

When you browse the Quincy Funds demo, you can view pages as different visitors in order to test how a profile

affects the content you see. As you visit different parts of the site, Oracle ATG Web Commerce obtains data

about you and adjusts your home page on the fly to display promotions that may interest you. Some of your

navigation patterns will be recorded and compiled into a chart; some may be tracked in your profile.

Oracle ATG Web Commerce provides these key components for managing visitor interactions:

• Real-time profiling features provide the ability to changes a visitor’s profile information on the fly according

to his or her site activities (see Tracking Visitor Interests (page 15))

• User segmentation allows business managers to group similar visitors together according to profile

information

• Content targeting allows designers to display personalized content to visitors who match specified criteria

(see Targeting Content (page 19))

• Scenarios give business managers a graphical tool for building sophisticated marketing campaigns that

initiate contact with customers (for example, e-mail campaigns) and respond to their behavior (see Managing

Visitors through Scenarios (page 25))

2 1 Introduction

About this Document

This document discusses the features of the Quincy Funds Web site and the Oracle ATG Web Commerce tools

used to implement them. Each chapter builds on the information in previous chapters, so it is recommended

that you read the chapters in order. The document includes the following chapters and appendix:

Getting Started (page 3)

Explains how to start the Quincy Funds demo.

Touring Quincy Funds (page 5)

Leads you through the Web site as a guest, an investor, and a broker.

Tracking Visitor Interests (page 15)

Describes how to configure a scenario to change an investor’s profile based on the pages he

or she browses.

Targeting Content (page 19)

Provides instructions for displaying an image to only those visitors who match specified

criteria.

Managing Visitors through Scenarios (page 25)

Demonstrates how scenarios in conjunction with slots can implement a marketing strategy.

Appendix A, Additional Scenario Examples (page 37)

Includes sample scenarios intended to improve member retention and satisfaction.

Audience

The primary audience of this document is business users, although it also discusses the roles of page developers

and programmers in building a personalized Web site.

• Business users define the goals for the Web site, determining the content it provides, and the visitor behavior

that must be tracked, and creating scenarios that implement marketing strategies. Business users also create

and analyze reports generated from site data.

• Page developers create the content pages, integrating the scenario elements created by business users

and the code elements created by programmers. Page developers are also responsible for overall Web site

appearance.

• Programmers create the code elements that allow the system to provide dynamic, personalized site content.

They also configure repositories and perform database administration duties.

This demonstration is by no means a complete application, but it does illustrate on a smaller scale nearly all the

techniques that a fully functional personalized site employs. Before running this demonstration, you may want

to familiarize yourself with the core concepts of the Personalization module and the Scenarios module. These

concepts are described in the ATG Personalization Guide for Business Users.

2 Getting Started 3

2 Getting Started

The Quincy Funds demo application is provided with any Oracle ATG Web Commerce distribution that includes

the ATG platform. Note that you must select Quincy Funds as an option when you run the product installer; it is

not installed by default.

Before you can use the Quincy Funds demo, you must configure Oracle ATG Web Commerce and a supported

database. It is highly recommended that you use the Configuration and Installation Manager (CIM) to perform

post-installation setup tasks. CIM includes an option to configure the Quincy Funds demo and include it in your

application.

When setup is complete, start your database. Then run Oracle ATG Web Commerce by starting your

application server with the application you assembled through CIM. For detailed instructions, refer to Installing

Demonstration Applications in the ATG Installation and Configuration Guide.

When Oracle ATG Web Commerce is running, point your browser to the appropriate URL:

• Oracle WebLogic Server:

http://localhost:7001/QuincyFunds

• JBoss Application Server:


• IBM WebSphere Application Server:


If necessary, supply the machine name where Oracle ATG Web Commerce is running in place of the default

localhost.

For additional information about startup options, refer to the ATG Installation and Configuration Guide.

Exploring the Demo

To explore the demo fully, you need to start the ATG Control Center, which is a graphical interface to many of the

development and maintenance tasks involved in building Web sites with the ATG product suite. For example,

you can use the ATG Control Center to create and preview content pages, manage visitor profiles, and set up the

business rules that determine how you will personalize content for each visitor.

The way in which you start the ATG Control Center depends on how you installed your ATG components. To start

an ATG Control Center that is installed on the same machine as the rest of the product suite:

4 2 Getting Started

1. Point your browser to the ATG Dynamo Admin Server interface (http://localhost:port/dyn/admin,

where the default port numbers on JBoss, Oracle WebLogic, and IBM WebSphere are 8080, 7001, and 9080 ,

respectively. For more information, see the ATG Installation and Configuration Guide).

The default user name and password are admin/admin. If you are the first person to enter the default user

name, you are prompted to select a new password. Otherwise, ask your system administrator for the values to

enter.

2. Click the appropriate start button.

• Use Start ACC in Server VM if you want to run the ATG Control Center on the same machine that runs the

server and you want to conserve memory.

• Use Start ACC in Separate VM if you want to run the ATG Control Center and server stack on separate

machines or you want quicker startup loading.

3. When the ATG Control Center starts, you are prompted for a user name and password. Enter the information

you supplied in step 1.

Alternatively, you can install a standalone copy of the ATG Control Center on your local machine and run it from

that location.

1. Start the local copy of the ATG Control Center.

2. Enter the username and password (initially admin/admin).

3. In the Host Name field, enter the name of the server where Quincy Funds is running.

4. Enter the port number for the ATG Control Center, by default 8860.

For more information on starting the ATG Control Center, refer to the ATG Installation and Configuration Guide.

3 Touring Quincy Funds 5

3 Touring Quincy Funds

Each visitor is represented by a user profile, which is a set of properties that describes and maintains information

about a site visitor. When a visitor enters the Quincy Funds site, the type property in the profile identifies him or

her as an investor, a broker, or a guest, and the content on the home page is customized to the visitor’s interests.

Guest profiles contain basic information such as the type of browser that is used to access the site. Profiles for

investors and brokers maintain detailed information such as preferences and contact information.

In addition to having a specific profile type, visitors are segmented into profile groups according to information

in their profiles. At Quincy Funds, investors are segmented according to their investment strategy; they can

belong to one of three profile groups: aggressive, conservative, or moderate.

All profiles contain a locale property that identifies the appropriate language (English, French, German, or

Japanese) in which to display the navigation bar and feature articles.

For detailed information on profiles, see Setting Up Visitor Profiles in the ATG Personalization Guide for Business

Users.

On each user’s home page, he or she can view the feature and new articles tailored to his or her interests. The

following functions are available to investors only:

• Browse the funds offered by Quincy Funds. Investors who view funds may receive prospectuses by mail.

• Manage investment goals. Each investor has an “Aggressiveness” index (a profile property) that tracks the

number of risky funds he or she shows interest in. The site adjusts this index as the user looks at various funds.

For example, displaying information about an aggressive fund causes this index to increase.

• View the portfolio. The demonstration does not include functionality for maintaining the portfolio; it

demonstrates only that investors have portfolios, while brokers and guests do not.

Brokers can do the following:

• View the list of clients for each broker and use sales tools.

• Send targeted e-mail to investors.

The remaining sections of this chapter walk you through the various features of the site as a guest, an investor,

and a broker. Note that many of the links are non-functional (or else take you to the list of funds) since this is

only a demonstration application.

6 3 Touring Quincy Funds

Entering as a Guest

All site visitors are guests until they register or log in (at which point they become investors or brokers). When

you start the demo for the first time, you are logged into the home page as a guest. The browser window title

should read “Quincy Funds - guest home.”

Guests can view only news items, features, and the funds that Quincy offers. Each news item, feature, and fund

is a content item in one of the application’s content repositories. Guests can choose the language they prefer

by using the menu at the bottom of the home page. In this demo, the site translates only the features and the

navigation bar.


A primary goal of Quincy Funds is to turn guests into investors. Not only is there an obvious link from the

navigation bar that reads Sign Up Now! (or, for example, Inscrivez-vous ici for French guests), but there is also a

clever “hook”: if visitors request the prospectus for a fund, they see a login/registration page that encourages

them to sign up. An image at the bottom left of the home page also encourages guests to sign up. This image is

driven by a customer acquisition scenario that will be discussed later. All these features focus on turning visitors

into members.

Registering as an Investor

Since guests have limited access to Quincy Funds, they need to register as investors if they want to use

additional features. On the guest home page, click the Sign-up Now! link, which takes you to a registration form.

When asked, enter a user name and password.

After you log in, supply personal contact and profile information. Select Jack Smith as your broker. When you

save your entries, the site stores your profile properties in the database. Later, you will see how you can change

these profile properties and how these properties affect the content you see. After submitting this form, you’re

returned to the home page as a registered investor. The title of the page showing in your browser should be

“Quincy Funds - investor home.”

Now that you are an investor, your home page shows a (non-functional) portfolio and your investment goals.

Your home page also displays feature articles and news links, as well as a modified navigation bar:


To change your profile properties:

1. Click on the Change My Investment Goals link.

The investment goal page opens and identifies your goals as conservative and long-term.

2. Change your investment goals from Conservative to Aggressive, and click Change My Goals.

3. Return to your home page.

Note the new content: a promotion for an aggressive fund, Quincy Venture fund, at the bottom of the page.


Changing your investment goals can also affect the feature articles displayed on your home page so that they

fit your new investment style. This is an example of tracking. See Tracking Visitor Interests (page 15) for more

examples.

Changing Your Profile and Preferences

To edit your personal profile, select the My Profile link in the navigation bar. This brings up a form that lets you

edit the values of your profile properties.

Notice that the profile has a property called the “Aggressive Index.” This property tracks your investment style

by taking note of the funds you view. For example, if you look at the Quincy Venture fund, your Aggressiveness

index will increase by two. Test this by clicking QUIVF in the My Holdings section on your home page. This is an

example of an implicit property, because the property’s value is inferred through your actions rather than your

explicit input. Inspect your profile to see your changed Aggressive Index.

When you look at a fund and request a prospectus, the site pulls your address from the profile information

you entered while registering. The demo application won’t actually send e-mail to confirm the shipment of a

prospectus.

Another form that affects the home page is your preferences. Select the My Preferences link from the

navigation bar. This lets you change the feature and news topics that you want to see, and also adjust the

number of articles that you want displayed on your home page. In this demo application, the repositories

contain few news articles, so setting these numbers high will have no effect. There are only three feature articles

in the demo repository for each investment style.

The “My Preferences” page also lets you select a preferred language. If you change your language preference,

only certain items will appear in your chosen language. Once finished, log out.

Changing Your Language Preference

The Quincy Funds application can display content in English, French, German, and Japanese. When you modify

your language preference, the navigation bar and the feature links change to the selected language. Any dates,

times, percentages, and currencies on each page also adhere to that language selection.

As a guest, you can adjust your language preference on your home page. As a registered member, you can

specify a language preference, which is carried across site visits. At any time, you can change your language

through the My Preferences page.

About Locales (for Programmers)

A locale is a code that represents a language/country combination. The locales supported in Quincy Funds are

as follows:

Language / Country Locale

English / United States en_US

French / France fr_FR

German / Germany de_DE

Japanese / Japan ja_JP


Oracle ATG Web Commerce determines a visitor’s locale by scanning these parameters in this order and

implementing the first that contains a valid value:

• The locale property in a visitor’s profile

• The Accept–Language HTTP header, which can be set on the visitor’s browser

• The default visitor locale

• The server locale

For example, to display a guest visitor’s home page in the correct language, Oracle ATG Web Commerce first

looks to the guest’s profile for the locale property, which is always null. Then it refers to the visitor’s browser for

the Accept–Language HTTP setting. If none exists, the system pulls the locale information from the default

visitor locale. Finally, if none of these settings are configured, it uses the server locale.

Locales at Work

In the Quincy Funds application, a directory is set up for each of the site’s locales. The locale-specific files are in

the following directories:

• <ATG10dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/en

• <ATG10dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/fr

• <ATG10dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/de

• <ATG10dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/ja

A separate Features repository contains feature articles in each supported locale.

When a visitor opens the Quincy Funds home page, the index page is displayed. This page contains a Switch

servlet bean that finds the visitor’s locale (through the process outlined above) and displays the home

page in the corresponding language directory. This is an example of content rendered dynamically through

components.

For more information on the Switch servlet bean, see the ATG Page Developer's Guide.

Displaying Japanese Characters

If you are running a Western operating system, you need to configure your computer to accept double-byte,

non-Latin characters. If you have not installed the Japanese character set on your machine, refer to your

operating system instructions on how to do so. Then configure your preferred browser by modifying the font

settings.

To configure Internet Explorer:

1. Launch Internet Explorer. Select Tools > Internet Options.

2. Click Languages. Click Add, and select Japanese. Click OK.

3. Click Fonts, select Japanese, then click OK.

4. Click OK to save your changes and close the dialog box.

5. Close and relaunch the browser.

6. Select View > Encoding > More > Japanese (Auto-Select). Each time you open the browser, you need to

enter this setting.


To change your browser back to your default language, return to the language settings and move your preferred

language to the top of the list.

You may also need to configure the ATG Control Center to allow you to view Japanese files. For more

information, see the ATG Platform Programming Guide.

Browsing as a Broker

Log in as a broker called jack/jack (user name and password). After you log in, you see the broker view of the

Quincy Funds home page, with a Broker Connection banner and a browser page title that reads “Quincy Funds

- broker home.” The home page no longer displays a portfolio, but it still shows news articles and features

directed specifically at brokers. The home page also shows a list of your clients and some demo sales tools:


Click the name of one of your clients. The Quincy Funds demo displays the client’s profile, stock holdings, and

latest activities on the Quincy Funds site. The My Clients link in the navigation bar opens a page that lets you

sort your clients according to their properties:

• Investment strategy is aggressive

• Investment strategy is conservative

• Actual portfolio doesn’t match their ideal portfolio

Targeted E-Mail

Click the E-mail link in the navigation bar to view the Targeted E-mail feature. This feature lets brokers create,

edit, and review e-mail that is targeted to investors whose profiles match the message and who have indicated

that they want to be contacted by e-mail.

Before you can test Targeted E-mail, you need to set the emailHandlerHostName property as described below:

1. In the ATG Control Center, open the Pages and Components > Components By Path screen.

2. Expand atg/dynamo/service.

3. Double-click SMPTEmail to open it in a Component Editor.

4. In the Properties tab, locate the emailHandlerHostName property.

5. Change both Configured Value and Live Value to the name of your e-mail host. (A standard name is

mailhost.<companyname>.com.)

To create a targeted e-mail:

1. Click the Create new mailing link to open the new mailing page.

2. Select investors as your mailing audience.

3. Enter a fictitious Subject, Sender’s Address, and Mailing name.

4. Select a mailing template.

5. Click Send Mail.

Once you’re returned to the Targeted E-mail page, you can view all mailings you’ve sent. Click the Summary of

sent mailings link. Your summary should have one entry. Return to the Targeted E-mail page.

The Edit content heading lists the e-mail templates in the making. Click a template to see the three variable

fields that a broker can edit:

• Text for conservative investors

• Text for aggressive investors

• Signature

When the site sends e-mail, investors identified as aggressive receive the text written for them, and conservative

investors receive the text relevant to their investment style. You can create targeted e-mail templates with a

variety of customizable fields. Return to the broker home page.


Logging Out

When you have finished using the application, click Log-Out from the navigation bar. After logging out, your

session disconnects from your profile and reverts back to guest status. Your session is anchored to your profile,

not your IP address, to protect it from another visitor who might log in from your workstation.

Further Exploration

In addition to browsing the demo as different visitors, you can also explore it as someone who works on the

Quincy Funds Web site development team. The remaining chapters in this guide show how business users,

page developers, and programmers use the ATG platform’s personalization and scenario features to implement

customer relationship strategies in Quincy Funds.


4 Tracking Visitor Interests 15

4 Tracking Visitor Interests

Tracking is the ability to update a user profile on the fly based on the Web pages he or she views. Tracking, used

in conjunction with targeting, lets you personalize Web site content that accommodates the changing interests

of site visitors.

This chapter shows how a visitor’s navigation habits change the values stored in his or her profile. You log in

as an investor and browse some funds. Based on the number of high-risk funds you view, your Aggressiveness

index increases or decreases. In this way, Quincy Funds determines a visitor’s investment strategy, which the site

uses in combination with targeting to advertise only those funds of interest to the visitor.

To investigate tracking for aggressive investors:

1. Log in as mary (user name and password).

The “Quincy Funds – investor home” page opens.

2. Click the My Profile link in the navigation bar to view Mary’s profile information.

The Aggressiveness index is six. This index measures how many risky funds you view and for which you

request information. For every aggressive fund, your index increases; for conservative funds, it decreases.

3. Click the Funds link.

4. Click the Quincy Venture Fund - QUIVF link.

5. Click the Send me the application and prospectus link to request sign up information and verify Mary’s

mailing address. Click OK.

6. Return to your profile page; the aggressive index has increased to 10. Go to the Funds page.

7. Click the Quincy Venture Fund - QUIVF link again and then return to your profile page immediately.

8. View your profile: your index has increased to 12 because you viewed only the fund and didn’t request

additional information. Return to the Funds page.

9. Click the Quincy Money Market Fund - QUISB link and then return to your profile. The Aggressiveness index

has decreased by one to 11.

10.Log out.

Every fund and visitor profile is assigned a property called aggressivenessIndex. A fund’s

aggressivenessIndex is a fixed number. A profile’s aggressivenessIndex accumulates the values supplied

by the aggressivenessIndex of the funds viewed by a visitor. The profile gathers an index value through

implicit or hidden means. You could also alter a profile’s aggressivenessIndex explicitly by opening the “My

Profile” page and modifying the provided value.

16 4 Tracking Visitor Interests

Tracking is most powerful when combined with targeting. You can determine which investors prefer aggressive

strategies (tracking) and tailor the images, articles, and fund information they view to their interests (targeting).

See Targeting Content (page 19) for an example.

Exploring Tracking Scenarios

To track a visitor’s investment aggressiveness, a business user builds a scenario that can analyze a visitor’s

navigation habits and interpret that behavior as different levels of aggressiveness. For this scenario to work, the

Aggressive index property must be configured with an appropriate numeric value for each fund.

To view this tracking scenario:

1. In the ATG Control Center, open the Scenarios > Scenarios screen.

2. Navigate to QuincyFunds/InvestorTracking/TrackFundsViewed:

According to this scenario, once a visitor views a fund (which is an item), that visitor’s aggressiveness index

accrues the fund’s index value. The visitor’s profile stores the aggressiveness tally as well as a list of all funds the

visitor browses: the third element instructs the system to add the fund’s name to the visitor’s profile.

For a discussion of scenarios, see Managing Visitors through Scenarios (page 25). For details on scenario

elements and building scenarios, see the Creating Scenarios chapter in the ATG Personalization Guide for Business

Users.

How Tracking Affects a Profile

Take a look at Mary’s profile to see how the site updated her properties based on your actions:

1. In the ATG Control Center, open the People and Organizations > Users screen.

2. Click List to see all profiles.

3. Select View > Refresh.

4. Select Mary to examine how your recent activities in Quincy Funds affect the visitor profile.

The profile in the ATG Control Center consists of user-entered explicit information such as name, password, and

gender, as well as implicit information – date of last session and broker ID. The aggressivenessIndex equals

11 in the ATG Control Center profile just as it did in the Quincy Funds Profile Web page. The fundsViewed

property lists Quincy Venture fund (QUIVF) and Quincy Money Market fund (QUISB), which are the funds you

viewed in the previous section. This information is funneled back to an investor’s broker.

4 Tracking Visitor Interests 17

To examine how the site uses the fundsViewed property:

1. Log in to the Quincy Funds demonstration as jack (user name and password).

The “Quincy Funds - broker home” opens.

2. From the My Clients list, click the Mary Hammond link.

Beneath the Recently Viewed Funds label are the two funds, Quincy Venture fund and Quincy Money Market

fund, traced from the ATG Control Center profile fundsViewed property.

3. Browse the Holdings list.

4. Log out.

Jack can use this information as an indicator that Mary’s investment style is changing. She’s invested in an

aggressive fund, but she seems to be interested in a very conservative fund. Jack can send her a mix of e-mail

targeted to aggressive and conservative investors, and once her interests become clear, he can add her to that

group.

Tracking for Page Developers

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:

1. Sets the ElementID to the fund’s XML file.

2. Opens the fund page.

3. Passes the ElementID to 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 ElementId aggressiveIndex 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

<ATG10dir>/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.

Tracking and Repositories for Programmers

For programmers, the task of tracking visitor activity and interests involves defining the repositories that store

the profile and content information for the Web site.

18 4 Tracking Visitor Interests

The Quincy Funds demo contains the following repositories, with each one representing a collection of items or

information that shares subject matter and requires the same set of properties:

• Investment Tips - Contains brief messages. The Quincy Funds home page is configured to display a random

tip each Tuesday to investors.

• Funds - Contains information on all funds offered by Quincy Funds, with properties that categorize each fund

according to securities type and aggressiveness rating.

• Offers – Contains all fund promotions or offers focused towards prospective fund subscribers.

• Features - Contains all feature articles available for display. The Quincy Funds home page displays selections

from the list according to the visitor’s investment goals and language preference or locale.

• Images - Contains all images used in the demonstration. Each content item does not contain the actual image

data, but instead contains the image URL and properties that are available for targeters.

• Profile – Contains all profiles for registered visitors. A profile is made up of implicit information derived from

visitor activities or explicit information entered by the visitor.

• News - Contains the list of news articles available for display. The Quincy Funds home page displays selections

from this list according to the visitor’s interests.

• E-mail – Contains templates available to the Targeted E-mail feature.

Each repository has one or more item types, which are specified in the repository template definition file

that describes the relationship between the repository and the database. For a detailed discussion about

repositories, see the ATG Repository Guide.

The tracking example outlined in the previous sections requires a programmer to define aggressiveIndex and

fundsViewed properties in the Profile repository, and an aggressiveIndex property in the Funds repository.

For more information on the repository implementations used in Quincy Funds, please refer to Repository

Structure in the Quincy Funds Demo (page 33).

5 Targeting Content 19

5 Targeting Content

Targeters display certain content on a page based on a set of rules. For example, when an investor looks at the

investor home page, the site invokes ten separate targeters to produce that page.

• Four targeters select and display the images that represent the visitor’s investment goals.

• One targeter shows feature articles.

• One targeter shows news articles.

• One targeter shows a promotion to aggressive investors.

• One targeter displays a randomly selected investment tip each Tuesday.

• One targeter is tied to a slot that advertises funds that aren’t in the investor’s portfolio.

• One displays a warning if the investor has selected Japanese preference but hasn’t loaded the Japanese

character set.

20 5 Targeting Content

The asterisks in the image above indicate page components that use targeters.

Note: The image above does not demonstrate the Japanese language support targeter or the fund

advertisement targeter.

To use a targeter, you need to define the rule set that determines who should view a piece of content and insert

the targeter servlet bean to anchor that rule set to a particular page. The term targeter refers to the rule set.

This chapter shows how a targeter determines the features to display on an investor home page.

To demonstrate how this targeter affects what you see:


1. Log in as an investor called sandy (name and password). Notice the Feature articles that appear on the home

page:

• Is Your Money Safe?

• Playing it Safe

• Saving for a Car

2. Click the My Preferences Link. Change the Display features number to two. Click Save to return to the home

page.

3. Click the Change My Investment Goals link. Change your investment style to aggressive. Click Save.

4. Return to the home page. Your Features should now include:

• High Risk Hedge Funds

• Quincy Bullish on International Markets

To implement this, a business user configured rules that decide when to show each feature to a given broker.

The page developer embedded the targeter servlet bean in the Broker home page.

Previewing a Page as Different Users

Another way to view the Quincy Funds site personalized for Sandy is through the preview feature in the ATG

Control Center.

To preview Quincy Funds as Sandy:

1. In the ATG Control Center, open the Targeting > Preview screen.

2. Enter the following information:

• Login name: sandy

• Password: sandy

• User type: investor

• Strategy: aggressive

• Number of feature items: 2

3. Click Step 3 Choose the page you want to view.

• From the All Document Roots list, select DSSJ2EEDemo.

J2EEApps > QuincyFunds > Quincy Funds J2EE DAF Demo (QuincyFunds). The list of pages

below changes to show the pages for the application you just specified (<ATG10dir>\DSSJ2EEDemo

\j2ee-apps\QuincyFunds\web-app\).

• Select \en\index.jsp.

4. Click File > Preview to open Sandy’s home page.


Examining Targeting Rules

Targeting rules determine when content appears to a set of visitors. You build a targeting rule by identifying a

piece of content and defining who can see it, when it will be displayed, and what will happen if the who and

when parameters aren’t met. A rule is a member of a rule set, which begins with a “show” or “hide” statement

and ends with a separator.

To inspect the targeting rules for an item in the Features repository:

1. In the ATG Control Center, open the Targeting > Content Targeters screen.

2. From the list of folders, select Features.

3. In the right pane, select Features.

This targeter consists of three rule sets. Each rule set contains one rule. You can confirm this by selecting one line

in the rule set and the Edit > Select Entire Rule command. The entire rule set is selected. For this example you

need only examine the first rule:

Show this content:Items whose Target Audience includes Person's StrategyAnd whose Language starts with Locale's localeStringTo these people:people whose Usertype is investor

Each rule is based on a piece of content and begins with a content-related phrase. This phrase describes what

item the page should display. An item, in this example, is a file in the Features repository called a feature. In

short, this rule states that all items in the Features repository that meet both criteria will display on an investor’s

home page. Each criterion is based on a property value held by a feature.

Items whose Target Audience includes Person's Strategy

All items in the Features repository maintain a property called Target Audience that has the same possible

values as the Person's Strategy on a user profile. When you selected the investment style “aggressive,”

you updated this profile property. In this way, investors only see the features they’re likely to be interested in.

And whose Language starts with Locale's localeString

Because items in the Features repository are offered in English, French, German, and Japanese, each item has a

property called Language that contain its locale. Similarly, each user profile contains locale settings in a Locale

property. This portion of the rule ensures that the features appear on a home page in an investor’s language of

choice, by comparing the profile value against the feature value.

Features that meet both criteria are presented to investors. The Usertype property on a user profile determines

whether visitors are recognized as a guest, an investor, or a broker.


Targeting for Page Developers

The business user builds the targeter rules; the page developer inserts the targeter servlet bean into the investor

home page. There are several kinds of targeter beans: each one governs the order in which targeted items

display differently. The bean in this example, TargetingRange, is used when several items are available for

display, because there may be multiple features that meet these criteria.

Examine the TargetingRange bean in the investor home page. In short, this code executes the targeter

rules, returns the number of items desired by the logged in visitor, and sorts them alphabetically by title. Then

the system displays the article name and image and provides a link to the feature text in full. If no items are

returned, it displays “No Features Today” notice.

To see how these tags appear on a page:

1. Open investorhome.jsp in <ATG10dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/en.

2. Find the first instance of the TargetingRange bean, which is used to locate items in the Features repository.

<dsp:droplet name="/atg/targeting/TargetingRange"> <dsp:param bean="/atg/registry/RepositoryTargeters/Features/Features" name="targeter"/> <dsp:param bean="Profile.numberfeatureitems" name="howMany"/> <dsp:param name="sortProperties" value="+title"/> <dsp:param name="fireContentEvent" value="false"/> <dsp:param name="fireContentTypeEvent" value="false"/> <dsp:oparam name="outputStart"> </dsp:oparam> <dsp:oparam name="output"> <tr valign=top> <td><dsp:a href="feature.jsp"> <dsp:param name="ElementId" param="element.repositoryId"/> <img height="73" vspace="2" border="0" hspace="8" width="73" src="<dsp:valueof param="element.SmallImageURL">images/features/noimage.gif</dsp:valueof>"> </dsp:a></td> <td><dsp:a href="feature.jsp"> <dsp:param name="ElementId" param="element.repositoryId"/> <b><dsp:valueof param="element.title"/></b></dsp:a><br> <dsp:valueof param="element.headline"></font></dsp:valueof> </td> </tr> </dsp:oparam> <dsp:oparam name="empty"> <tr> <td colspan=2>No Features today.</td> </tr> </dsp:oparam> </dsp:droplet>

<dsp:droplet name="/atg/targeting/

TargetingRange">

Invokes the TargetingRange servlet bean. For

more information on TargetingRange, see the

ATG Page Developer's Guide.


<dsp:param bean="/atg/registry/Repository

Targeters/Features/Features"

name="targeter"/>

Instructs the servlet bean to run the Features

targeter against the items in the Features

repository.

<dsp:param

bean="Profile.numberfeatureitems"

name="howMany"/>

Sets the servlet bean’s howMany input parameter

to the visitor’s numberoffeatureitems property.

A visitor can change this property value through

the Preferences page.

<dsp:param name="sortProperties"

value="+title"/>

Alphabetizes the located features by title.

Additional sorting mechanisms are available, see

the ATG Page Developer's Guide.

<dsp:oparam name="output">….</dsp:oparam> Renders the located items as output.

<dsp:a href="feature.jsp">

<dsp:param name="ElementId"

param="element.repositoryId"/>

<dsp:valueof

param="element.SmallImageURL">images/

features/noimage.gif</dsp:valueof>">

</dsp:a>

Sets the ElementID parameter to the feature’s

ID. Displays the image stored in the feature’s

smallImageURL property, which is also a link

to the feature’s text. When the image is clicked,

feature.jsp uses the ElementId to display the

text stored in the offer’s relativePath property

<dsp:a href="feature.jsp">



<dsp:valueof param="element.title"/></

dsp:a>

Sets the ElementID parameter to the feature’s ID.

Displays the feature’s title as a link to the feature’s

text. When the title is clicked, the page passes the

ElementID to Feature.jsp, which inserts the

text fragment appropriate for that feature article.

<dsp:valueof param="element.headline">

</dsp:valueof>

Displays the feature’s headline.

<dsp:oparam name="empty">

<td colspan=2>No Features today.</td></

dsp:oparam>

Displays “No Features today” if no features are

returned by the TargetingRange bean.

Targeting for Programmers

It’s the programmer’s job to create the Features repository and to configure properties for the items it contains.

Then, a business user adds feature articles and defines property values. Business users use properties such as

Language and Targeting Audience in targeting rules.

To see items that are part of the Features repository:

1. Open the Content > Features screen.

2. Click List.

6 Managing Visitors through Scenarios 25

6 Managing Visitors through

Scenarios

This chapter shows how scenarios can tailor your promotional campaign to encourage investors to subscribe to

funds. Quincy Funds’ primary goal is to attract guests to become investors and persuade investors to buy funds.

Using scenarios, Quincy Funds promotes new funds by sending e-mail and displaying images on the home page

of prospective buyers. This chapter provides two sample scenarios:

Demonstrating a Simple Scenario (page 25)

Demonstrating a Complex Scenario (page 26)

You can think of scenarios as a flowchart for Web site interactions. A scenario is based on a particular visitor-

initiated action or event, such as visiting the Quincy Funds Web site, and it provides a predetermined response

to that action. Business users build scenarios to accomplish marketing campaigns. For a comprehensive

discussion of scenarios, see the Creating Scenarios chapter in the ATG Personalization Guide for Business Users.

Demonstrating a Simple Scenario

In this example, you log in as a user who has not subscribed to the Quincy Special Situations fund. The content

that is displayed encourages you to read about this fund:

1. Log in as mary (user name and password).

2. Notice the image above the My Portfolio section:

3. Log out.

This image displays for all visitors who do not own the Quincy Special Situations fund. The next section shows

how the scenario that implements this behavior is designed.

26 6 Managing Visitors through Scenarios

Inspecting the PromoteSpecialSituations Scenario

Look at the Promote Special Situations scenario and see how each event acts as a scenario building block:


2. Navigate to QuincyFunds/InvestorPromotions/PromoteSpecialSituations:

This scenario is made up of one segment or string of actions called Portfolio Based Promotion. According to

this scenario, once a visitor logs in, if that visitor does not have the Quincy Special Situation fund in his or her

portfolio, the Special Situations Offer image will display on his or her home page.

Demonstrating a Complex Scenario

This example shows how Quincy Funds promotes the Quincy Growth fund, among others, to eligible investors.

To see how Quincy Funds’ promotional campaign advertises funds to qualifying users:

1. Sign up as a new member. Set your zip code to 02471. Log out.

2. Log in as the user you just created.

3. On the home page, view the image just above My Portfolio.

4. Log out and log in again.

The image changes.


The image changes again.


The image changes again.

7. Continue until you are returned to the Quincy Growth fund promotion. Click the image:


The site displays an article promoting the fund. This article provides a link to fund statistics. From there, you

can request an application and prospectus, and then register to invest in the fund.

These images advertise a product or service available to you that you haven’t bought. You’re qualified to view

these advertisements based on your profile.

Inspecting the PromoteGrowthFund Scenario

The site displays these advertisements to potential customers through a series of scenarios. These scenarios

ensure that only the investors who don’t own the Quincy Growth fund, for example, see the promotional Quincy

Growth fund image. Review the scenario that caused the Quincy Growth fund image to display.

To review the scenario that caused the Quincy Growth fund image to display:


2. Navigate to Quincy Funds/Investor Promotions/PromoteGrowthFund:

(Note that both segments contain more elements than an appear in this image. Fork elements for each locale

have been removed to allow the image to display.)

This scenario consists of two segments or strings of actions. By grouping related segments in the same scenario,

you can manage them as a unit: when you want to cancel the Quincy Growth fund promotional campaign, you

can stop both segments by disabling the scenario.

The E-mail Fund Promotion Segment

This segment dictates that on May 1st 2000 at 12:00 am, all visitors who indicated they’d like to receive e-

mail communication and haven’t already invested in Quincy Growth fund will receive the Quincy Growth


fund promotion mailing. The segment syntax identifies those visitors who are investors and have their

receiveEmail property set to yes.

This scenario is triggered by a time/date element: 12 am on May 1, 2000.

Only investors are included in this scenario.

Only those investors who indicated they’d like to receive e-mail are included in

this scenario.

A fork separates this condition from the next two, which means that if this

condition isn’t met, the following two will be.

This element identifies those user profiles that contain growth.xml in their Fund

List.

This element works in conjunction with the next element. Only those who don’t

own Quincy Growth fund will be affected by the next element.

An e-mail advertising Quincy Growth fund is sent to those who meet the people

conditions. View the e-mail through the Pages and Components > Pages

screen, by following the supplied path. Use the View > Preview option to see

how it will appear to recipients.

The scenario ends.

All investor profiles contain a property called Fund List, which lists their holdings. Of the identified investors,

some have invested in the Quincy Growth fund, and, therefore their Fund List property contains the value /

repositories/Funds/en_US/growth.xml. The remaining investors will receive the promotional e-mail.

The Show Promotion Segment

The second segment, Show Promotion, implements the image behavior you viewed previously: to present a

Quincy Growth fund image to potential investors. This segment begins with a time element, ensuring that the

image serves as a Quincy Growth fund reminder, because the image displays on the site only after the e-mail has

been sent. All visitors who register or log in and haven’t invested in the Quincy Growth fund will see an image

advertising it on their home page.

This scenario is triggered by a date element: the days between May 1st and

December 31st 2000.

A fork allows for several different actions to be included in this scenario. Any

visitor who logs in is affected by this scenario.

Also, any visitor who registers is affected by this scenario.


Another fork divides the scenario into two courses of actions.

If the visitor’s profile contains the Quincy Growth fund in the fund list, the

scenario jumps to the final element.

This element works in conjunction with the proceeding element. Only those who

don’t own Quincy Growth fund will be affected by the next element.

The site places an image advertising Quincy Growth fund in the slot for those

investors who’ve met the mentioned requirements.

The scenario ends.

Scenarios Sharing Slots

The Show Promotion segment displays the Quincy Growth fund image for all eligible investors. The image exists

in a slot with other images like the Special Situations fund and Seminar advertisements:

According to the example demonstrated in the previous section, when an investor views the investor home

page, the scenarios associated with QFOfferSlot run. When certain events in the scenarios occur, the scenario

fills the slot with images. Those investors who own stock in both funds won’t see either image.

About Slots

A slot is a bucket that receives content from scenarios and displays that content on a Web page. Multiple

scenarios can make use of one slot. You can configure the order in which the items in a slot display.

The content rendered from a slot is determined on the fly. A combination of scenario conditions causes an

image to be placed in a slot. These conditions can incorporate a certain day of the week, delay in time, specific

user properties, or actions initiated by the system or a site visitor. For example, you could display one item to

all investors who register in the spring, received a welcome e-mail, but haven’t yet invested in a Quincy fund, or

display another item on Mondays to all men who’ve identified their investment strategy as aggressive although

their actions prove they’re conservative.


To use a slot, you need to complete the following steps:

1. Create the slot. (See Scenarios and Slots for Programmers (page 31).)

2. Use a targeter servlet bean to embed the slot in a page. (See Scenarios for Page Developers (page 30).)

3. Create a scenario that fills the slot with content. (See Inspecting the PromoteGrowthFund Scenario (page

27).)

For information on the differences between targeters and slots, see the Creating Scenarios chapter of the ATG

Personalization Guide for Business Users.

Placing an Image in a Slot

Return to the ATG Control Center Scenarios screen and browse the PromoteSpecialSituations scenario.

It resembles the Show Promotion segment in the PromoteGrowthFund scenario. Both scenarios use

QFOfferSlot.

Open the PromoteOverseasFund scenario. It displays an image advertising the Quincy Overseas Fund to all

investors who view the feature articles “Global Investment Focus” or “Quincy Bullish on International Markets”

but don’t own the Quincy Overseas Fund. The image is displayed in the QFOfferSlot.

To test this scenario:

1. Log in to the Quincy Funds demonstration as scott (user name and password). Under the Features section,

click the Global Investment Focus link to view the article.

2. Return to the investor home page.

You should see this new image:

Because this scenario is session-scoped, the contents in the slot are discarded at the end of each session. You

need to view the international-related articles again to see the Quincy Overseas fund advertisement again.

Scenarios for Page Developers

The page developer is responsible for inserting the targeter servlet bean that implements the slot into a site

page. This example uses the TargetingFirst bean; any targeting bean will work.

In short, the investor home page pulls from the QFOfferSlot the first item that complies with the slot’s

properties. That item displays as an image URL and links to offer.jsp.

To view how a slot is rendered in the investor home page:

1. Open investorhome.jsp in <ATG10dir>/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/en.


2. Locate the first instance of the TargetingRange bean, which is used to locate items in the Features

repository.

<dsp:droplet name="/atg/targeting/TargetingFirst"> <dsp:param bean="/atg/registry/Slots/QFOfferSlot" name="targeter"/> <dsp:param name="howMany" value="1"/> <dsp:param name="fireContentEvent" value="false"/> <dsp:param name="fireContentTypeEvent" value="false"/> <dsp:oparam name="output"> <dsp:a href="offer.jsp"> <dsp:param name="ElementId" param="element.repositoryId"/> <img border="0" src="<dsp:valueof param="element.imageURL"/>"></dsp:a> </dsp:oparam> </dsp:droplet>

The tags are described below:

<dsp:droplet name="/atg/targeting/

TargetingFirst">

Invokes the TargetingFirst servlet bean. For

more information on TargetingFirst, see the

TargetingFirst section in ATG Page Developer's

Guide.

<dsp:param bean="/atg/registry/Slots/

QFOfferSlot" name="targeter"/>

Instructs the servlet bean to execute the

QFOfferSlot rules against the items in the

repository.

<dsp:param name="howMany" value="1"/> In conjunction with the servlet bean

(TargetingFirst) determines the number of

items that the site displays in the slot and the

order in which they should display.

<dsp:oparam name="output">…</dsp:oparm> Renders the located offer items as output

available for display.

<dsp:a href="offer.jsp">



<dsp:valueof param="element.imageURL"/>"></

dsp:a>

Displays the image identified in the offer’s

imageURL property as a link to offer.jsp.

Sets the ElementId to the offer’s ID and passes

it to offer.jsp. When the image is clicked,

offer.jsp uses the ElementID to display the

text stored in the offer’s relativePath property.

Scenarios and Slots for Programmers

A programmer creates the QFOfferSlot. When you create a slot, you select a content source, which is the slot’s

repository (Offers, in this example) and a content type (HTML). Also, you determine how the slot will post the

content items it contains.

To view the slot:


1. Open the Pages and Components > Components by Path screen.

2. Navigate to atg/registry/Slots/QFOfferSlot.

The bar across the bottom of the Components panel displays information about the selected component

(QFOfferSlot): the path, class, scope, and description. The scope indicates the level of persistence (options

include session, global, and request). Session scope means the items in the slot will be discarded when the

session ends.

Note: Because QFOfferSlot is session-wide, in the PromoteOverseasFund scenario, a visitor activates a

trigger when viewing the international-related articles. Anytime throughout the session, a visit to the investor

home page may render the related image in the slot. Once that visitor initiates a new session, the image

won’t be available until the site activates the trigger again.

3. Double-click QFOfferSlot to open it in the Component Editor.

Inspect the items in the Properties tab. These values decide how the slot displays content.

• The generation property indicates whether the slot displays content received from scenarios (passive) or

triggers a scenario to solicit content (active).

• The ordering property selects from all items available in a slot, the order in which they display, either

sequentially (following the chronology in which they were added) or randomly.

• The retrieval property manages the retrieval process. Will all items display in a specific order and then be

removed from the slot (destructive)? Or will that order repeat (static)? Can an item display multiple times in

rotation (rotating)?

The QFOfferSlot displays items placed in it by scenarios (passive). It rotates the items, starting with the first

one placed in the slot. For a complete discussion of slots, see Using Slots in the ATG Personalization Guide for

Business Users.

7 Repository Structure in the Quincy Funds Demo 33

7 Repository Structure in the Quincy

Funds Demo

Content repositories in the Quincy Funds demo are designed to show a variety of approaches for structuring

SQL repositories for the delivery of Web site content. Each repository is an implementation of ATG’s Generic SQL

Adapter (GSA). For detailed information on GSA content repositories, please refer to the SQL Content Repositories

chapter in the ATG Repository Guide.

The Quincy Funds demo uses the following models. Note that both of these models are supported by ATG’s

SQL/File System Connector. This configuration is sometimes referred to as a SQL Repository with a Content

Repository Loader.

• Model 1: Hybrid content repository. Content is stored on the file system and metadata is stored in the SQL

repository.

In this configuration, a Content Repository Loader service monitors the file system on a specified path (or

collection of paths) and loads data from content files on the file system into a GSA SQL repository, with a one-

to-one mapping from a file to a content repository item. One of the properties of the repository item, tagged

in the item-descriptor as the content-property, acts as a pointer to the file on the file system.

• Model 2: Non-hybrid content repository. Both content and metadata are stored in the SQL repository.

In this configuration, both metadata and the content itself are stored in the SQL repository, with the content

being stored in a single column. The Content Repository Loader is used to load files in the file system to the

SQL repository. Again, there is a one-to-one mapping from a file to a content repository item.

It is important to note that neither model provides a means of propagating changes made to repository items

back from the repository to the source files. This behavior means that a user could theoretically make a change

to a repository item through the ATG Control Center, which would then be overwritten the next time the content

is loaded from the file system into the repository. To avoid this problem, the ability to create or edit repository

items through the ATG Control Center or JSPs is disabled for the Quincy Funds demo.

For Model 1, note also that the metadata and the file content are not synchronized between the time when

changes are made to the file content and the scheduled run time of the Content Repository Loader. Therefore a

state could exist where the file content used by the Content Repository Loader to construct the repository item

could have been modified, but the Content Repository Loader (because it is a scheduled service) has not yet

propagated the modifications to the repository item. In this state, it is possible for targeting rules or scenarios

to reference and serve the file content according to repository item properties that are no longer synchronized

with their content. For this reason, Model 1 is suitable for content repositories where synchronization between

the content and the metadata is not an important consideration, or where changes to the underlying content

are very infrequent.

Model 2 does, however, guarantee synchronization of served content and metadata properties. With this

configuration, the file content that the Content Repository Loader uses to construct the repository item is itself

34 7 Repository Structure in the Quincy Funds Demo

a property of the repository item; the item does not simply contain a pointer to the file. Therefore there is no

possibility of a loss of data integrity between the metadata and the content.

The content repositories in Quincy Funds use these models as follows:

• News repository: XML content served using Model 1. This configuration demonstrates the management of

XML content exclusively through the Repository API.

Model 1 is used in this case because the file content itself is never served (only metadata is served), so

synchronization is not an issue. Content is accessed only through properties of the repository items. There is

no serving of raw XML.

• Email, Images, InvestmentTips, and Offers repositories: HTML content served using Model 1.

These repositories demonstrate how Model 1 can be employed to serve HTML content.

• Funds repository: XML content served using Model 2. This configuration demonstrates the management of

XML content using the XMLTransform servlet bean and XSL stylesheets.

Model 2 is used in this case because the file content is referenced and served (through XMLTransform).

Synchronization is therefore important.

This repository also gives examples of managing nested XML (XML content that has items embedded in other

items). The Content Repository Loader does not handle nested XML items. This repository demonstrates how

nested XML can be displayed by means of XSL stylesheets, while the Content Repository Loader can still be

employed for the load process.

In addition, the Funds repository demonstrates how to create org.w3c.Documents from SQL repository

items. See Serving SQL Repository Items as org.w3c.Documents (page 35) for more information.

• Features repository: HTML content served using Model 2.

The Features repository demonstrates the deployment of Model 2 to serve HTML content in cases where

synchronization between content and metadata is considered to be important.

Content Repository Loaders in the Quincy Funds Demo

Each SQL content repository in the Quincy Funds demo has an associated Content Repository Loader (an

implementation of class atg.adapter.gsa.ContentRepositoryLoader) that is responsible for loading the

content into the repository. For each repository in Quincy Funds, the content is located at:

/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/repositories/{RepositoryName}

For instance, the content for the Funds repository is located as follows:

/DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/repositories/Funds

As an example mapping, the following file

/DSSJ2EEDemo/j2ee-apps/QuincyFunds/

7 Repository Structure in the Quincy Funds Demo 35

web-app/repositories/Funds/en_US/growth.xml

is mapped to the following repository item (id):

repositories/Funds/en_US/growth.xml

in repository:

/atg/demo/QuincyFunds/repositories/Funds/Funds

by the Content Repository Loader located at

/atg/demo/QuincyFunds/repositories/Funds/FundsLoader

Serving SQL Repository Items as org.w3c.Documents

Another important feature demonstrated by the Quincy Funds repositories is the ability to serve SQL

repository item properties as org.w3c.Document objects. org.w3c.Documents are implementations of the

Document Object Model standard for XML documents; for more information, refer to the Document Object

Model Level 2 Core specification at http://www.w3.org/DOM/DOMTR. Content stored in the repository as a

String or File can be transformed into an org.w3c.Document by means of the property descriptor classes

atg.xml.FileToDOMPropertyDescriptor (page 35) and atg.xml.PropertyToDOMPropertyDescriptor (page

36) (both are extensions of atg.repository.RepositoryPropertyDescriptor). The properties can then

be used as input to the XMLTransform servlet bean, for instance. For more information on the XMLTransform

servlet bean, refer to the ATG Page Developer's Guide. For more information on using property descriptors, refer

to User-Defined Property Types in the ATG Repository Guide.

Caching capability is also provided for org.w3c.Documents created through property descriptors.

org.w3c.Documents served from XML repositories are cached using a cache key that is based on

either a file name or URL. The ability to create org.w3c.Documents through SQL property descriptors,

as described above, requires a different cache key, because the property descriptors, in particular

atg.xml.PropertyToDOMPropertyDescriptor, do not have file or URL information. The cache key used by

the property descriptors for document caching is based on a concatenation of the repository item’s repository

name, item descriptor name, repository id, and content property name.

atg.xml.FileToDOMPropertyDescriptor

The FileToDOMPropertyDescriptor included with Quincy Funds is an

implementation of class atg.xml.FileToDOMPropertyDescriptor, which extends

atg.repository.RepositoryPropertyDescriptor. It takes another of the item descriptor’s properties

(of type File) as an attribute. It then transforms and caches the content of the other property as an

org.w3c.Document.

The following example definition is from the repository definition file DSSJ2EEDemo/config/atg/demo/

QuincyFunds/repositories/News/news.xml:

36 7 Repository Structure in the Quincy Funds Demo

<property name="document" property-type = "atg.xml.FileToDOMPropertyDescriptor" queryable="false"> <attribute name="documentSourcePropertyName" value = "newsContent"/> <attribute name="contextRootName" value="QuincyFunds"/></property>

(Note that this property is not actually used in the demo.)

For more information on this property descriptor class, refer to the ATG Platform API Reference.

atg.xml.PropertyToDOMPropertyDescriptor

The PropertyToDOMPropertyDescriptor used by Quincy Funds is an implementation

of class atg.xml.PropertyToDOMPropertyDescriptor, which extends

atg.repository.RepositoryPropertyDescriptor. This property descriptor takes another of the item

descriptor’s properties (of type String) as an attribute. It then transforms and caches the content of the other

property as an org.w3c.Document.

The following example definition is from the repository definition file DSSJ2EEDemo/config/atg/demo/

QuincyFunds/repositories/Funds/funds.xml:

<property name="document" property-type = "atg.xml.PropertyToDOMPropertyDescriptor" display-name-resource="document" description-resource="documentShortDescription"> <attribute name="documentSourcePropertyName" value="fundContent"/> <attribute name="contentTimeStampPropertyName" value="lastModified"/></property>

where fundContent is defined as follows:

<table name="dss_qf_fund_cont" type="auxiliary" id-column-name="id"> <property name="fundContent" column-name="file_content" … data-type="string" queryable="false"/> </table>

The Quincy Funds demo contains an example of a reference to this property in an XMLTransform servlet bean.

The example is located in the following JSP:

DSSJ2EEDemo/j2ee-apps/QuincyFunds/web-app/en/fund.jsp

<dsp:droplet name="/atg/dynamo/droplet/xml/XMLTransform"> <dsp:param name="input" param="element.document"/> <dsp:param name="template" value="funds-investor-template.xsl"/> <dsp:oparam name="failure"> <p> Failure to transform XML document: <dsp:valueof param="input"/> </dsp:oparam></dsp:droplet>

For more information on this property descriptor class, please refer to the ATG Platform API Reference.

Appendix A. Additional Scenario Examples 37

Appendix A. Additional Scenario

Examples

This appendix provides additional examples of how you can implement a marketing strategy through scenarios.

These scenarios replicate real-life strategies and often incorporate multiple touchpoints (such as e-mail) and

delays in time.

Converting Members into Frequent Visitors (page 37)

Sending a Monthly Newsletter (page 37)

Advertising a Seminar (page 38)

Converting Members into Frequent Visitors

Once a visitor signs up to be a member, Quincy Funds can take the next step towards its business goals, which

include ensuring that members visit often, benefit from each visit, and purchase funds. The Welcome Mail

scenario encourages visitor retention by predicting visitor actions and countering those actions with a positive

communication and offer.

To view the WelcomeMail scenario:


2. Expand the QuincyFunds and InvestorRetention folders.

3. Click WelcomeMail.

The New Members segment specifies that all investors new to Quincy Funds will receive a welcome e-mail five

minutes after joining. New investors who haven’t logged in after 30 days will receive a second e-mail containing

an offer.

Sending a Monthly Newsletter

In this example, a business user creates a monthly newsletter. Each month, the business user needs to modify

the e-mail message only, the scenario will automatically send the newsletter.

To view the MonthlyNewsletter scenario:

38 Appendix A. Additional Scenario Examples


2. Navigate to QuincyFunds/InvestorRetention/MonthlyNewsletter.

This scenario sends an e-mail to investors on the first of each month.

Using Scenario Templates

A scenario template is a useful format for creating one generalized scenario that (with minor configuring),

applies to multiple situations. The MonthlyNewsletter scenario was derived from a scenario template

called QFScheduleMailing that includes all of the elements necessary for sending a mailing. To view the

QFScheduleMailing scenario template, open the Scenarios > Scenario Templates screen, and select

QFScheduleMailing.

As you can see, the template is made up of conditions with placeholders, indicated by parentheses. You could

adapt this template to create a scenario that sends information about investing to brokers.

To create a scenario from this template:


2. Select File > New Scenario to open the Create New Scenario wizard.

3. Select QFScheduleMailing, and click Next.

4. Place your scenario in the Quincy Funds root-level folder. Name your scenario “New Brokers.” Click Finish.

5. By selecting words and choosing from related drop-down lists, define the following:

• Mailing Date: the 1st Monday of the month at 2:00am (Select the Weekday in Month option and then

specify the first Monday.)

• Mailing Group: brokers

• E-mail: Select the Quincy Funds demo from the list of applications at the top of the window. The list at the

bottom changes to show documents in this application. Select /en/email/newsfeatures.html.

6. Click OK. The scenario opens and appears as follows:

The scenario you’ve just created sends an e-mail to brokers that discusses the new feature articles. For

more information on scenario templates, see various sections in the Creating Scenarios chapter of the ATG

Personalization Guide for Business Users.

Advertising a Seminar

Quincy Funds is hosting a seminar to educate its investor community about investment strategies. This scenario

uses e-mail and an image on a Web page to publicize the seminar to those investors who are eligible to attend.

Appendix A. Additional Scenario Examples 39

To view the Promote Seminar scenario:


2. Navigate to QuincyFunds/InvestorPromotions/PromoteSeminar.

This scenario sends a targeted e-mail to only those investors who live near the seminar location. Once the

investors receive the e-mail, an advertisement for the seminar will appear on their home page.

You’ll notice that this scenario was derived from a scenario template called QFSeminarPromotion located on

the Scenarios > Scenario Templates screen. If Quincy Funds sponsors the seminar in other cities, the scenario

template can be easily applied to create a new scenario. To use this template, you would open the new scenario

wizard, which requests a template and prompts you to configure the variable elements.

E-Mail Seminar Promotion Segment

This segment sends the e-mail message on May 15, 2000 to all investors who want to receive e-mail and have

the zip code 02471 or 02472.

Show Seminar Promotion Segment

The second segment displays the related seminar image when an investor with either postal code logs in

between May 15 and September 25 2000. You can assume that the seminar registration deadline is September

25.

You may notice that the slot, QFOfferSlot, is the same slot that is used in the Quincy Growth fund, the Quincy

Special Situations fund, and Quincy Overseas fund promotions. This means that when an investor meets the

criteria to view the images associated with each promotion, those images display in an order specified by the

slot.

40 Appendix A. Additional Scenario Examples

Index 41

Index

Aadvertising a seminar, 38

aggressiveness index, 9, 15

ATG Control Center

editing demo properties in, 33

starting, 3

Bbrokers, 1

features, 5

home page, 11

my clients, 12

targeted e-mail, 12, 38

business users, 2

scenarios, 25

targeting, 23

Cchanging your profile and preferences, 9

components

SMPTEmail, 12

TargetingFirst, 30

TargetingRange, 23

Content Repository Loaders, 34

converting members into satisfied patrons, 37

Ee-mail (see targeted e-mail)

e-mail fund promotion segment, 27

e-mail seminar promotion segment, 39

emailHandlerHostName property, 12

FfireContentEvent, 17

fireContentTypeEvent, 17

Ggeneration property, 32

guests, 1

entering as, 6

features, 6

home page, 6

Hhome page

brokers, 11

guests, 6

investors, 7

targeting used on, 19

Iinternationalization, 5, 9, 9

driven by personalization, 9

file structure, 10

Japanese support (see Japanese support)

locales (see locales)

investors, 1

features, 5

home page, 7

JJapanese support, 10

Internet Explorer browser settings, 10

JavaServer Pages, editing in demo, 33

Llocales, 9

English / United States, 9

file structure, 10

French / France, 9

German / Germany, 9

Japanese / Japan, 9

setting, 10

localization (see internationalization)

logging out, 13

OOracle ATG Web Commerce

starting, with Quincy Funds, 3

ordering property, 32

org.w3c.Document objects, serving repository items as, 35

Ppage developers, 2

scenarios, 30

slots, 30

targeting, 23

tracking, 17

preferences, visitor, 9

previewing

pages, 17, 21

42 Index

targeting results, 21

profile groups, 5

profiles, 5

aggressiveness index, 9

changing, 8, 9

how tracking affects, 16

trackfundsviewed scenario, 16

programmers, 2

repositories, 17

scenarios, 31

slots, 31

targeting, 24

tracking, 17

PromoteGrowthFund scenario, 27

PromoteOverseasFund scenario, 30

PromoteSeminar scenario, 38

PromoteSpecialSituations scenario, 26

properties

emailHandlerHostName, 12

generation, 32

ordering, 32

retrieval, 32

QQF ScheduleMailing scenario template, 38

QF SeminarPromotion scenario template, 39

QFofferslot, 31, 39

Rregistering as an investor, 7

repositories, 17

programmers, 17, 33

targeting, 24

repository items, editing in demo, 33

retrieval property, 32

rules, targeting , 22

Sscenario templates, 38

creating, 38

QF ScheduleMailing, 38

QF SeminarPromotion, 39

scenarios, 25

advertising a seminar, 38

business users, 25

page developers, 30

programmers, 31

PromoteGrowthFund, 27

PromoteSeminar, 38

PromoteSpecialSituations, 26

sending a monthly newsletter, 37

slots (see slots)

TrackFundsViewed, 15, 16

using for visitor retention, 37

WelcomeMail, 37

Show Promotion segment, 28

Show Seminar Promotion segment, 39

slots, 29

generation property, 32

ordering property, 32

placing images in, 30

programmers, 31

QFofferslot, 30

retrieval property, 32

used by several scenarios, 29

SMPTEmail component, 12

SQL content repositories, 33

starting the ATG Control Center, 3

starting the demo, 3

Ttags

fireContentEvent, 17

fireContentTypeEvent, 17

targeted e-mail, 12

creating a mailing, 12

editing a mailing, 12

enabling, 12

viewing a summary of mailings, 12

targeting

business users, 21, 23

content, 19

example, 20

page developers, 23

previewing results, 21

programmers, 24

repositories, 24

rules, 22

used on investor home page, 19

TargetingFirst component, 30

TargetingRange component, 23

TrackFundsViewed scenario, 15, 16

tracking

aggressiveness index, 9, 15

example, 15

page developers, 17

programmers, 17

using scenarios for, 16

visitor interests, 15

Uuser profiles (see profiles)

Vvisitor retention

MonthlyNewsletter, 37

Index 43

WelcomeMail scenario, 37

WWelcomeMail scenario, 37

44 Index