Professional DotNetNuke ASP.NET Portals wrox phần 4 pdf

Criteria This choice specifies how the Impressions and Date constraints should be

enforced. If enforced independently of one another (OR), a banner will

cease to display outside of its date constraint or even within its date con￾straint if the number of impressions has been reached. If enforced jointly

(AND), all criteria must be true for the banner to cease display.

The AND option helps to address a lack of throttling control. On a busy site

with few banners in rotation, a given number of impressions can be

chewed up very quickly and so displayed over only a brief time period. By

jointly evaluating the criteria, a more equitable rotation is achieved by pro￾viding for additional banner impressions during the time period.

Figure 4-45

You can advise vendors of the status a banner by clicking the Email Status to Vendor button at the bot￾tom of the Edit Banner page. This sends an e-mail to the address specified in the Vendor details, which

relays the banner field information (text, costs, and constraints) and performance (view and click￾through counts).

Vendors as Affiliates

Just as your site links to vendors through the use of banners, your vendors may also link to you. If you

would like to be able to track your vendors’ click-through performance to your site, you can click Add

New Affiliate. Define a tracking period and associated cost per click (CPC) and cost per acquisition

(CPA) and e-mail the vendor their link information by clicking Send Notification (see Figure 4-46).

Figure 4-46

105

Portal Administration

08_595636 ch04.qxd 5/10/05 10:00 PM Page 105

The CPC information for affiliate referrals will be summarized in the Edit Vendor list, just as click￾through is for banners. However the CPA information is currently unused. You can specify multiple

affiliate relationships under a single vendor to provide for tracking during discrete time periods.

At the time of this writing, it is possible to create affiliate referrals with overlapping date ranges. This

will produce double counts of vendor performance during the period of overlap. So be sure to end one

affiliate period before starting another.

Newsletters

Periodically, you’ll want to communicate with your users. The Newsletter page provides a very conve￾nient way for you to do this by allowing you to send e-mail to users in specified roles (see Figure 4-47).

Remember when you set up the Newsletter Subscribers role? Here’s where you put that to use.

Figure 4-47

Just select the role(s) that you want to be included in the distribution. If a user belongs to more than one

role, they’ll still only get one e-mail. You can also specify additional recipients separated by semicolons

in the Email List field. And you can format your e-mail as either text or HTML.

Figure 4-48 displays the advanced e-mail options, which include sending a file attachment and choosing

the priority setting. The Send Method option allows you to specify whether or not your e-mail is person￾alized. Choosing the BCC method sends just one e-mail, which will be delivered to all users. Choosing

the TO method causes your e-mail to be personalized (for example, Dear John Doe).

Using the TO method seems much more personal, but it comes at a cost. First, the processing required

to create a separate e-mail for each user could be significant (with large user volume). Second, it signifi￾cantly increases your bandwidth utilization. The bandwidth associated with the BCC method is mini￾mal — just one e-mail. However, the bandwidth associated with the TO version is the product of the

size of the e-mail and the number of users.

You can also choose whether the sending of e-mail is processed synchronously or asynchronously. If you

have a large list of users, asynchronously probably makes the most sense. In either case, a summary e-mail

is sent to the Portal Administrator reporting on the number of recipients, number of pieces of e-mail actu￾ally sent (1 or n), and the start/stop times for processing the job. DotNetNuke batches e-mail addresses

into groups in the background so you’ll never actually be trying to send an e-mail with thousands of BCC

recipients.

106

Chapter 4

08_595636 ch04.qxd 5/10/05 10:00 PM Page 106

Figure 4-48

Site Log

The Site Log displays text-based reports only, as shown in Figure 4-49.

Figure 4-49

Table 4-15 identifies the available report types.

Table 4-15: Site Log Report Types

Affiliate Referrals Track referrals from vendors who are defined as affiliates. By using their

affiliate ID numbers in links to your site, you’ll be able to capture how pro￾ductive those affiliate links are.

Detailed Site Log This detailed log of site activity includes all users and displays date and

time, user name, referrer, user agent, user host address, and page name.

Table continued on following page

107

Portal Administration

08_595636 ch04.qxd 5/10/05 10:00 PM Page 107

Page Popularity Display the total number of visits to the pages on your site in the period

specified. Date and time of the last page visit is included.

Page Views By This series of reports provides a summary of the number of visitors

(anonymous) and users (logged in) that accessed your site in the intervals

specified (Day, Day of Week, Hour, Month).

Site Referrals Summary list of web pages (including search engines) that users have

clicked on to lead them to your site.

User Details This series of reports provides a summary of the number of page visits

recorded according to the characteristic specified (Agents, Frequency, Regis￾trations by Country, and Registrations by Date). The Report by Frequency can

be interesting — it identifies your most frequent visitors in any given period.

Logging occurs at the discretion of the Host, who has a number of options for how it is configured. If the

Host chooses to generate text-based log files (like IIS logs), these reports will become obsolete because

they work only with database logging information (at this time). See Chapter 5 for more information on

Host settings that control logging.

Recycle Bin

Have you ever deleted a file on your computer only to experience a panic moment? Portal Administrators

might feel that too once in a while, which is why DotNetNuke has a Recycle Bin feature (see Figure 4-50).

Figure 4-50

The act of deleting a page or module doesn’t really delete anything; it merely sets a flag that DotNetNuke

understands internally as deleted and so ignores it in the general interface. Items that have this flag set

can be found (and restored from) the Recycle Bin.

Developers can see this implementation by looking at the database fields Tab.IsDeleted and

Modules.IsDeleted.

108

Chapter 4

08_595636 ch04.qxd 5/10/05 10:00 PM Page 108