Frequency and Recency Targeting
When a user is shown an ad multiple times over a short period, that user can begin to ignore the ad, reaching the point where they don't even see it anymore. Or they can see it often enough that they're simply annoyed by it. This is referred to as overexposure or ad burnout. Frequency and recency targeting helps you prevent overexposure by limiting how often a user is shown a creative. For example, you might decide that after a user has seen the same creative more than three times in a single day, it's not worth showing that creative to that user again. Or you might price a campaign higher if the user has seen it fewer than three times in a day and price it lower if the user has seen it more than three times. This page has information about:
- The frequency and recency targeting supported by our API through the Profile Service
- Example of ow to use this type of targeting
- How and where you can apply frequency and recency targeting
AppNexus supports several levels of frequency targeting through the API. This targeting is specified on the Profile Service, which can be set at the advertiser, insertion order line item, campaign, and creative level. The API frequency settings follow the format shown here:
|x imps per day|
|The maximum number of times a creative can be served to a user within one day.|
|x imps per hour|
|The maximum number of times a creative can be served to a user within a one-hour period.|
|x imps per week|
The maximum number of times a creative can be served within one week, beginning on Sunday.
Regardless of when a creative is first served to the user, every Sunday the impression count for the user will be reset to zero and the frequency values will begin recounting.
|x imps per month|
The maximum number of times a creative can be served within one calendar month.
Regardless of how far into a month a creative is first served to the user, the impression count for the user will be reset on the first day of the following month and the frequency count will start over.
|x imps per lifetime|
|The maximum number of times a creative can be served to the user.|
The API recency settings follow the format shown here:
|1 imp per x minutes/hours/days/weeks|
|A single creative will not be shown to an individual user more than once every x minutes. (Value is in minutes, so 1 imp every 2 hours would be a value of 120.)|
Some additional settings related to frequency capping include the following:
|Serve only 1 imp per page|
|Creatives from a single advertiser will not be shown on a given page load in more than the specified number of placements. (If this value is set in the Console UI, the value will be null [off] or 1 [on].)|
|Include users without cookies|
A value of
Setting this option to
In addition to the preceding fields, there are two more fields that can be set only through the API:
|Minimum imps per session|
|Creatives from a single campaign will be shown to a given user at least X times per session.|
|Maximum imps per session|
|Creatives from a single campaign will not be shown to a given user more than X times per session.|
Show a creative no more than 50 times over the lifetime of the campaign, 3 times per session, and 10 times per day:
Show a campaign up to 8 times per day but no more than once per hour:
Show a campaign no more than 3 times per hour:
min_minutes_per_imp= 20 minutes
Where and How
Frequency can be applied through profiles to advertisers, insertion orders, line items, campaigns, and creatives, as well as to payment rules for publishers. The most restrictive setting always takes precedence.
When you set a frequency or recency cap for an object at one level, its child objects will inherit that cap, but it will be inherited by all child objects as a group. For example: If you set a frequency cap of ten impressions per day at the advertiser level and have ten line items attached to that advertiser, one line item could potentially use all 10 of the allotted impressions on one user. If you would like to spread the ten impressions out more evenly among your line items, you should also set a frequency cap at the line item level.
Another important point to remember is that frequency and recency settings will be applied according to the strictest settings available. For example, imagine that you have two creatives,
B, associated with the same line item. The frequency settings for creative
A specify that it can only serve three times per day (where a day is defined as a calendar day). Creative
B is set to only serve once per day. The line item settings, however, specify a frequency cap of two impressions per day.
Since the strictest settings are applied, the line item frequency settings override those set at the creative level. Therefore, even though creative
A's settings dictate that it can serve three times per day, it will never serve more than the two times per day specified at the line item level. If creative
B serves its single allowed impression to the user before
A can serve,
A will only be allowed to serve once to that user.