Capping and Restrictions

This article explains how to use the Aniview Server Capping options as well as Player setting restrictions

Client's Level restrictions (Player Settings):

Restrictions will take place on the client level only, while the ad-server behavior will not change.

Restriction applies to all associated ad sources for that channel.

Timeout Time:
The MAXIMUM amount of time the player will wait until the Ad Source associated with that channel finds an ad before going to the next one from the waterfall.

Max Requests per Minute

The player will limit the number of requests to the ad source. The calculation is 60 / *configured_number value*

Example: If set to 2, the ad-source will send requests every 30 seconds.

The player will calculate the time, and set the entered value as a max request for all ad sources associated with the channel on the client level.

Adserver might still provide ad sources that the player will avoid sending requests to and thus result in less relevant ad sources on the waterfall.

Maximum Impression Per Session:

The Adsource will not generate more IMPRESSIONS than this amount.

A session is from a player load till the user closes/exits the page.

If a channel has 3 ads sources associated, the player setting has “Maximum Impression Per Session” = 1

the max theoretical impression per session will be 3.

Maximum Requests Per Session:

The Adsource will not generate more REQUESTS than this amount.

A session is from a player load till the user closes/exits the page.

All ad sources will be limited to that number value and will not generate additional requests.

Waterfall might still contain ad sources that will not get requested on a specific session per this limitation.

AdSource>PLAYER SETTINGS:

Same as above, but applies exclusively to an ad source via the client.

Aniview Adserver Capping:

Demand>Ad source>Impressions Capping

Limit the maximum amount of impressions of this ad source per the value selected Daily/Monthly/Total

Requests Per Day = true; the value indicates the maximum amount of requests from that source.

Requests Pacing: pacing the request capping ratio.

APAP: Will exhaust the request cap as quickly as the calls from the waterfalls occur. (Theoretically, all amounts could be “burned” in moments)

Even: will distribute the capping exhaustion ~evenly throughout the day

Frequency Capping:

Limit the number of impressions per user per the time frame value: Daily/Weekly/Hourly/To

If a user generates an impression by this ad source, it will be counted until hitting the cap of the timeframe.

Later this user will not generate requests to the ad sources until the timeframe restarts.

Demand>Advertiser capping:

Same as above, but will apply to all child ad sources of the advertiser.