Browse the help center

Configure optimization settings

The network-wide rotation algorithm on Admin → Ad serving → Optimization settings — Manual Weighting, eCPM Optimization and eCPM with Burn-up, their estimates, periods and thresholds, and the CTR and I2C optimized traffic shares — step by step, with the caveats and what each field does.

How-to admin Admin → Ad serving → Optimization settings

What it is and why

One network-wide setting decides how ad serving picks the campaign inside a delivery priority tier — by weight, or by the eCPM each campaign earns — and two more decide how much of an optimized campaign’s traffic the CTR and I2C optimizers are allowed to steer. Nothing here touches the priority tiers or the creative pick; those are set per campaign and creative on Optimize ad rotation.

Example. Under eCPM Optimization with Burn-up Period with Optimized traffic share at its stock 95, the optimized campaign with the best measured eCPM gets 95 % of the optimized traffic and the other 5 % goes to a random losing campaign, so a campaign that is behind on eCPM still collects data. With CTR optimized traffic share at 90, a campaign with CTR optimization on serves its best-clicking creative on 90 % of requests and rotates the rest by plain weight; at 100 the other creatives get nothing once the model has ranked them.

Typical scenarios

You wantSetWhere
Campaigns share a tier by the weights managers set — the default, and what the Banners probability card models exactlyOptimization algorithm = Manual WeightingCampaigns optimization
The campaign that earns the most per thousand wins its tier outright, weights ignoredeCPM Optimization (beta); Estimated CTR and Estimated conversion rate for CPC / CPA campaigns with no data yetCampaigns optimization
Some campaigns compete on eCPM, the rest keep their weightseCPM Optimization with Burn-up Period (Beta); Optimized traffic share 95; a 24-hour Burn-Up period; managers tick eCPM Optimization on the campaigns to optimizeCampaigns optimization; the campaign’s Advanced settings
CTR-optimized campaigns keep 10 % of traffic for the creatives that are not winningCTR optimized traffic share 90CTR / I2C optimization
An optimized campaign serves its winner and nothing elseCTR optimized traffic share / I2C optimized traffic share 100CTR / I2C optimization

Step by step

  1. Open Admin → Ad serving → Optimization settings. The page needs the administrator permission Optimization Settings.

    Optimization settings page with the Campaigns optimization and CTR / I2C optimization panels

  2. In Campaigns optimization, pick the Optimization algorithm: Manual Weighting, eCPM Optimization (beta) or eCPM Optimization with Burn-up Period (Beta). The fields below appear for the algorithm that reads them — none under Manual Weighting, the two estimates under eCPM Optimization, all seven under Burn-up.

  3. Fill in the fields the algorithm shows (table under Reference): the estimates seed a CPC or CPA campaign’s eCPM before it has data; the Burn-Up and Start-Up periods are in hours; the minimal clicks and conversions let a campaign skip the start-up wait on a placement and country where it has already proved itself.

  4. In CTR / I2C optimization, set the CTR optimized traffic share and I2C optimized traffic share (0 – 100): the share of an optimized campaign’s traffic each optimizer steers toward its best performer. The remainder is served by plain creative weight.

  5. Click Save. The page confirms with Auto-optimization settings are saved…. Ad servers pick the change up with their next cache update.

Caveats and exceptions

The algorithm changes the campaign pick only. Delivery priority tiers still run first, and the creative inside the chosen campaign is still drawn by weight or by its CTR / I2C bandit.

AlgorithmHow the campaign inside a tier is chosenDoes campaign Weight matter?
Manual Weighting (default)Weighted random draw on campaign weightYes — it is the mechanism
eCPM Optimization (beta)The campaign with the highest eCPM for the request’s country wins outright; ties broken at randomNo — weight is not read at all
eCPM Optimization with Burn-up Period (Beta)Non-optimized campaigns compete on weight first; if the draw lands on an eCPM-optimized campaign, only optimized campaigns continue and the one with the best measured eCPM over its burn-up window winsYes, for the first split

Under Burn-up, Optimized traffic share splits the optimized campaigns between the winner and the rest: the remainder (100 − the share) goes to a random non-winner, so a campaign that is losing on eCPM still gets a trickle. The stock value is 95, i.e. 5 % to the losers.

Only Burn-up puts an eCPM Optimization checkbox on the campaign. The checkbox on the campaign’s Advanced settings is rendered only under eCPM Optimization with Burn-up Period, and only for a role holding Set “eCPM Optimization”. Under Manual Weighting and plain eCPM the checkbox is not rendered and a campaign’s stored flag has no effect. The checkbox is disabled on a House ads campaign.

The per-campaign eCPM inputs are not the ones on this page. Burn-Up period, Start-Up period, Minimal clicks, Minimal conversions, Estimated CTR and Estimated conversion rate all exist a second time on each campaign’s Pricing card, and it is the campaign’s copy that ad serving reads. This page sets the network defaults. The campaign-level estimates appear only under Burn-up, only on CPC / CPA campaigns, and only with the Manage “eCPM Optimization” permission (enabled or read-only); the campaign card also carries Subperiod (h) and Subperiod weights. See Configure pricing.

Minimal clicks and conversions are not CTR or I2C floors, despite sitting on the same page. They belong to the eCPM burn-up algorithm: once a CPC or CPA campaign has recorded that many clicks or conversions on a given placement + country since its last reset, that combination may use its measured eCPM even if the start-up window has not elapsed yet. They do nothing for a CPM campaign, and nothing at all under Manual Weighting.

A traffic share of 100 means no exploration. The CTR and I2C optimizers serve a single winner; the share is the only thing that keeps traffic flowing to the other creatives. A manager whose optimized campaign “serves one creative only” is seeing this setting, not a bug — see Not working? on the rotation guide.

eCPM beta and the Banners probability card. The card still divides by campaign weight under eCPM Optimization (beta), which ad serving does not read; under Burn-up the card shows the burn-up split and is authoritative. The weight columns on the linked trees grey out a campaign weight the draw does not read, with an ⓘ naming the reason.

The eCPM Optimization Details window — in the Actions menu of a campaign or a placement — lists the learned per-country / per-placement eCPM records and lets a manager delete a selection of them. It appears only under Burn-up and only with the matching permission. Clearing the records after a landing-page overhaul stops stale learning from holding a campaign back.

The SSP bidding thresholds are not on this page. They open from the SSP bidding optimization button on Admin → DSP Partners.

Not working?

  • Managers see no eCPM Optimization checkbox on campaigns. Where: the Optimization algorithm here — it must be eCPM Optimization with Burn-up Period — and the role’s Set “eCPM Optimization” permission on Admin → Users & access → User roles & permissions.
  • The estimates are missing on a campaign’s Pricing card. Where: the algorithm (Burn-up only), the campaign’s pricing type (CPC or CPA only) and the role’s Manage “eCPM Optimization” permission.
  • An optimized campaign serves one creative and nothing else. Where: CTR optimized traffic share / I2C optimized traffic share — at 100 there is no exploratory slice.
  • Saving says you do not have permission. Where: the administrator permission Optimization Settings on your admin role.
  • A change does not show in serving yet. Ad servers read the setting on their next cache update, not on the next request.

Reference

FieldSectionShown whenWhat it does
Optimization algorithmCampaigns optimizationalwaysManual Weighting / eCPM Optimization (beta) / eCPM Optimization with Burn-up Period (Beta).
Optimized traffic shareCampaigns optimizationBurn-up only0 – 100. Share of optimized traffic given to the eCPM winner; the rest goes to a random losing campaign.
Estimated CTRCampaigns optimizationeCPM and Burn-up0 – 1. Turns a CPC price into an estimated eCPM (1000 × CTR × price) before real data exists.
Estimated conversion rateCampaigns optimizationeCPM and Burn-up0 – 1. Same for CPA (1000 × CR × price).
Burn-Up period (hours)Campaigns optimizationBurn-up onlyThe lookback window, in hours, that a campaign’s measured eCPM is averaged over. A whole number, 0 or more.
Start-Up period (hours)Campaigns optimizationBurn-up onlyHow many hours of history a campaign must have before its measured eCPM is trusted instead of the estimate. A whole number, 0 or more.
Minimal clicksCampaigns optimizationBurn-up onlyClicks on a placement + country that let a CPC campaign skip the start-up wait. A whole number, 0 or more.
Minimal conversionsCampaigns optimizationBurn-up onlyThe same for a CPA campaign.
CTR optimized traffic shareCTR / I2C optimizationalways0 – 100. Share of an optimized campaign’s traffic the CTR bandit steers. The remainder is served by plain banner weight. 100 means no exploration at all.
I2C optimized traffic shareCTR / I2C optimizationalwaysThe same for the I2C bandit.
PermissionLets you
Optimization Settings (administrator)Open and save this page.
Set “eCPM Optimization” (account role)See and tick the campaign’s eCPM Optimization checkbox under Burn-up.
Manage “eCPM Optimization” (account role)See (read-only) or edit the campaign’s own eCPM estimates and periods on its Pricing card.

How the algorithm sits inside the whole pick, the CTR and I2C internals and the Banners probability card: Optimization reference.

Related pages:

Related pages

Please disable Adblock
Are you using adblock? Disable it and reload the page to proceed to the destination page.

A registration has already been submitted from this page. Please try again in 10 minutes.