Ads

Commerce Server supports two types of ads: paid ads and house ads.

  • Paid ads are pieces of content to be delivered by Commerce Server based on a specific formula for delivery referred to as Need of Delivery (NOD).

  • House ads are pieces of content that are served when paid ads are ahead of the Need of Delivery schedule specified for them. For example, a customer orders 1000 paid ads to be delivered over four months, but in the first two months the ad has been served 850 times. To balance the Need of Delivery schedule, house ads would be served.

    House ads are critical to ensure the smooth delivery of your paid ads. House ads are also displayed when there are no paid ads eligible for the request. For example, a house ad would be served because all paid ads missed a required target.

    House ads may also be used to sell leftover inventory at discounted prices. They may also be used if the ads on the site do not have specific delivery goals, but you want to have the ads run at specified weights.

Components of an Ad

In Commerce Server, ads are treated as having four parts:

  • Ad Properties include the name of the ad, the type (paid ad or house ad), the weight or number of requests or clicks scheduled to be delivered (paid ad versus house ad), the exposure limit, and the industry associated with the ad.

  • Ad Schedule is the start date/time and end date/time. You can select the days of the week on which the ad will be displayed, and what times of each day.

  • Ad Target identifies the pages on which the discount will be displayed, and the groups it will be targeted to.

  • Ad Display identifies the size of the ad, the type (for example, image, text, or HTML), and if needed, the image and/or URL that the user can click to go to another page (or Web site). You can display ads as images, text, HTML, non-clickable images, Buy Now ads, Windows Media Services, or vignette. (A vignette ad is composed of text that is displayed adjacent to the image where the ad is displayed.)

Targeting Ads

Using Commerce Server, you can determine when an ad is displayed, where, and to whom. When you create an ad, you specify the following:

  • Exposure limit. The number of times the ad can be shown to a user within a session.

  • Weight. A means of determining how frequently an ad is displayed, relative to all of the campaign items for a given customer. In a campaign, weight only applies to ads that are goaled at the campaign-level. If the ads are goaled at the item level, weight is not used for paid ads.

    For house ads the weight is relative to all other house ads for all customers and all campaigns. For paid ads, the weight is relative to other paid ads in the same campaign. The weight of an individual campaign item is relative to the weight of all the other campaign items.

    For example, assume you have four ads to sell paint, and you assign the weight as follows:

    Ad Weight Percentage of times served
    Blue paint 1 10
    Green paint 2 20
    Red paint 3 30
    Yellow paint 4 40
    Total Weight 10 100

    The total weight of all the ads is 100 (10+20+30+40 = 100). The Blue paint ad has a weight of 1 so it will be displayed once out of every ten ad requests.

    For paid ads, the weight is the ratio of a single ad to the sum of all the campaign items for that campaign. For house ads, the weight is the sum of the weights of all other house ads in the campaign.

    For ads that are goaled at the campaign item-level, weight is not used to determine the delivery of the ad. Instead, you directly specify the number of requests or clicks that should be served.

  • Page Groups. A set of related Web pages is tagged with a particular page group name and used for targeting ads. For example, if you are running a newspaper site, you might create a page group for Sports, one for the Top Story, and another for Local News. You can then target ads to display only on pages in certain page groups.

    You create page groups using the Reference Tables module.

  • Target Groups. A collection of targets to which content will be displayed. For example, you can target ads to users who have specific profile properties. For more information about targets and target groups, see Targeting and Personalization.

Processing Ad Campaign Items

The Content Selection Framework (CSF) processes the variables that you specify for an ad: campaign goaling, exposure limit, schedule, weight, page groups, and target groups. Each time a user visits your site, it determines whether the ad is to be displayed.

The Content Selection Framework for advertising uses a formula called Need of Delivery (NOD) to initially score the advertisements based on how far behind schedule they are. This formula takes into account the total quantity of content to be delivered and the length of time over which the quantity must be delivered. Need of Delivery is calculated for each ad request by the Content Selection Framework after it has processed the ad request. Need of Delivery is applied to paid ads only; it is not applied to house ads.

If you have several ads and want to know on what basis they are being displayed, contact your site developer. Commerce Server includes a tool named TraceScores that your site developer can use to trace the selection process. Use TraceScores to see exactly how the internal content decision process works.

If you plan to run many campaigns simultaneously, using the same target group and the same priority, the Content Selection Framework selects the ad to be displayed based on the ad type. If the ads are both house ads, an ad is selected at random using the weights as relative probabilities. If the ads are paid ads, an ad is selected for display based on the Need Of Delivery Calculation (which takes into account the start date, end date, number of events scheduled, and number of events served to date). One of the score modifications is History Penalty, which applies a decreasing penalty to ads recently seen by a user. When the History Penalty is enabled, ads are "rotated" over time.

See Also

Adding an Ad Campaign Item


All rights reserved.