Creatives, floors and yield in Ad Manager

0:00Welcome, outcomes and key terms

Play from 0:00 On Tuesday, someone on your team adds an Ad Manager pricing rule. One dollar fifty, on the homepage.

Play from 0:20 By Thursday, Prebid's wins on the homepage have halved (illustrative). Nobody touched Prebid. Its floor is still one dollar.

Play from 0:29 Bids between one dollar and one fifty still reach Ad Manager. Their line items just aren't allowed to compete any more.

Play from 0:34 This module is about the part of the set-up that decides whether a bid renders, competes and earns. Welcome to Module 6 of the RediAds Academy Header Bidding Masterclass: creatives, floors and yield in Ad Manager.

Play from 0:40 By the end of this module, you'll be able to do four things.

Play from 0:44 Choose between sending the top bid and sending all bids, with numbers, not habit.

Play from 0:50 Trace how a winning bid renders, including inside a SafeFrame.

Play from 0:55 Set floors in Prebid and in Ad Manager without the two layers fighting each other.

Play from 1:01 And design a split test whose answer you can trust.

Play from 1:07 Eight terms first. They all come back with examples.

Play from 1:11 Send all bids means every bidder's keys go to Ad Manager. Top bid means only the winner's keys go. The PUC, the Prebid Universal Creative, is a small script that renders the winning bid. A SafeFrame is a sandboxed frame that keeps the ad apart from your page.

Play from 1:31 The Price Floors module is Prebid's floor engine in the browser. A pricing rule is Ad Manager's floor, set inside the ad server. A control group is the traffic you leave unchanged in a test. And RPS is revenue per thousand sessions, the verdict metric for yield changes.

Play from 1:52 Here's where we are. Module 5 built the Ad Manager side: ad units, keys, granularity and the line item ladder.

Play from 2:07 Module 6 makes that set-up earn. Creatives first, then floors, then testing.

Play from 2:15 Module 7 is debugging, and Module 8 closes the loop with discrepancies and monitoring.

Play from 2:19 If you've already chosen send all bids and your creatives render cleanly, you can skip ahead to chapter four, floors in two places.

2:23Send all bids or the top bid

Play from 2:24 Chapter one. Prebid can send Ad Manager one bid per slot, or every bid it received. It sounds like a small setting. It changes your line items, your keys, your reports and your ad requests.

Play from 2:41 Let's see what reaches Ad Manager in each mode.

Play from 2:44 With top bid, only the winner travels. One generic set of keys: hb_pb, hb_bidder, hb_adid, hb_size and hb_format.

Play from 3:01 With send all bids, the generic set still travels, plus one set per bidder, like hb_pb underscore rediads.

Play from 3:11 Send all bids is Prebid's default. So if nobody chose, you're already in it.

Play from 3:18 First trade-off: line items. Here's the plan from Module 5. Illustrative.

Play from 3:25 Top bid: two hundred and thirty line items. One banner ladder, one video ladder.

Play from 3:31 Send all bids with four bidders: nine hundred and twenty. Every ladder repeats for every bidder.

Play from 3:38 Add a fifth bidder, and send all bids grows again, by two hundred and thirty. Top bid stays exactly where it was.

Play from 3:48 Second trade-off: what your reports can show.

Play from 3:52 Top bid shows only winners. You know who won, but not who bid and lost.

Play from 3:59 Send all bids shows every partner's bids. You can see bid rates, compare partners, and check contractual commitments.

Play from 4:07 That's the main reason to send all bids. If nobody reads those reports, you're paying for data you never use.

Play from 4:17 Third trade-off: keys and request size.

Play from 4:21 Top bid needs a handful of keys, whatever the number of bidders.

Play from 4:25 Send all bids adds five keys per bidder. Twelve bidders add sixty keys to the network's budget of two hundred.

Play from 4:33 And every key lengthens the ad request. Prebid's docs show fifteen bidders adding about two thousand six hundred characters.

Play from 4:44 Fourth trade-off, and it's often forgotten: control.

Play from 4:48 With a ladder per bidder, you can pause one bidder's line items in Ad Manager without touching the wrapper.

Play from 4:55 You can serve one bidder inside SafeFrames, and another outside them, if their creatives need it. We'll come back to that in chapter three.

Play from 5:04 With top bid, every bidder shares one ladder and one set of creative rules.

Play from 5:11 You don't have to choose all or nothing.

Play from 5:14 The hybrid: one generic ladder for targeting, plus a few bidder keys, like price and bidder, for reporting.

Play from 5:23 Prebid can also cap how many bids it sends, with a bid limit. For example, only the top three bids per slot.

Play from 5:31 And if you run private deals with top bid, Prebid can still send deal bids alongside the winner.

Play from 5:39 Here's a quick way to decide. Three questions.

Play from 5:42 Will someone read per-bidder reports every month? If not, lean towards top bid.

Play from 5:48 Do you need per-bidder control, like SafeFrame choices or pausing one partner? If yes, lean towards send all bids.

Play from 5:57 Are you close to the key budget, or adding bidders often? Then the hybrid is usually the comfortable middle.

Play from 6:04 Whatever you choose, write down why. The next person to change it will want to know.

Play from 6:11 Three mistakes we see with this choice.

Play from 6:14 One: send all bids left on by default, with no ladder per bidder. The bidder keys lengthen every request, and nothing ever uses them.

Play from 6:25 Two: switching modes in the wrapper without rebuilding the line items. Rungs that targeted hb_pb underscore rediads now wait for keys that never come.

Play from 6:38 Three: choosing send all bids for the reports, then never opening them.

6:44How the winning bid renders

Play from 6:45 Chapter two. A Prebid line item has won in Ad Manager. Now its creative has to show the right ad, from the right bidder, at the right size.

Play from 6:57 Here's what happens after the win.

Play from 6:59 Ad Manager serves the winning line item's creative into the slot.

Play from 7:04 Before it does, it fills the creative's macros with the key-values from the request. The one that matters most is hb_adid.

Play from 7:14 The creative is not an ad. It's a small loader that asks Prebid on the page for the bid with that ID.

Play from 7:22 Prebid hands over the ad, and the loader renders it in the slot.

Play from 7:27 The link between Ad Manager and Prebid is one macro in the creative.

Play from 7:33 The creative holds a pattern macro naming the key, hb_adid.

Play from 7:39 When Ad Manager serves the creative, it swaps the macro for that key's value from the request.

Play from 7:45 With send all bids, each bidder's creative uses that bidder's key, like hb_adid underscore rediads.

Play from 7:54 And for long bidder codes, it's the cut name from Module 5. The creative must use exactly what Ad Manager kept.

Play from 8:04 There are two kinds of loader you can put in that creative.

Play from 8:07 The Prebid Universal Creative is a script fetched from a CDN. It works for web pages, for AMP and for apps.

Play from 8:16 Prebid.js dynamic creatives are a smaller inline loader. They avoid the extra script fetch, but they depend on Prebid.js on the page, so they don't work for apps or AMP.

Play from 8:29 Same ladder, same keys, either way. Only the creative body changes.

Play from 8:36 If you use the Universal Creative, keep its version in step with your wrapper.

Play from 8:42 Recent Prebid versions set the hb_ver key you met in Module 5.

Play from 8:48 The creative can use it to load the matching Universal Creative version every time.

Play from 8:53 The alternative, copying the script straight into each creative, saves a fetch. But then it never updates itself, and someone has to remember.

Play from 9:05 A quick reminder on sizes, because it's where many render problems start.

Play from 9:10 A one-by-one creative serves into any size, and the loader resizes the frame using hb_size.

Play from 9:19 Real-size creatives report more precisely, but twenty sizes can mean a hundred creative copies. Prebid's own example.

Play from 9:28 And either way, Ad Manager shows each creative only once per page. So keep enough copies for every slot that could win at once.

Play from 9:39 On a normal page frame, the render path is short.

Play from 9:43 The creative's frame can reach the page directly.

Play from 9:46 So the loader calls Prebid's render function, passing the ad ID.

Play from 9:51 Prebid writes the winning ad into the frame, and records the bid as won.

Play from 9:55 Let's watch that happen on our demo page.

Play from 10:00 Here's the render path, slowed right down. This empty frame is a stand-in. On your site, Ad Manager would load the winning creative here.

Play from 10:38 The creative's only job is to find one ID. Here it is, the winner's hb_adid. In a real creative, the macro fills this in.

Play from 10:57 Now I'll do what the loader does. I ask Prebid to render that ID into the frame.

Play from 11:06 And there's the ad. The bid was two dollars thirty-seven, from our test RediAds bidder. Nothing came back from Ad Manager to make this happen, only the ID.

Play from 11:11 Let's confirm with Prebid's own records. One winning bid: RediAds, two thirty-seven, status rendered.

Play from 11:13 And the events, in order. First bid won, then ad render succeeded. These two events are what analytics adapters listen for. When a render fails, this is the first place you'll look. Module 7 does exactly that.

Play from 11:15 One thing this stand-in can't show is a SafeFrame. Our frame is on the same domain as the page, so a direct call works. Inside a SafeFrame, the same ID would travel as a message across the frame instead. That's chapter three.

Play from 11:16 Three creative mistakes we see.

Play from 11:19 One: a send all bids creative that still uses the plain hb_adid key. It renders the overall winner, whichever bidder's line item actually served.

Play from 11:32 Two: too few creative copies. The second slot that wins at the same rung has nothing to show.

Play from 11:39 Three: the loader pasted into each creative years ago, and never updated since.

11:46SafeFrames, native and video

Play from 11:46 Chapter three. Many publishers serve Prebid creatives inside SafeFrames. Native and video follow their own creative paths. Let's take them one at a time.

Play from 12:00 A SafeFrame is a managed iframe, served from a different domain from your page.

Play from 12:06 The ad can't reach into your page. Your page can't be rewritten by the ad.

Play from 12:12 They talk only through a defined messaging channel.

Play from 12:15 That's the security benefit. It's also why the direct call from chapter two no longer works.

Play from 12:23 So inside a SafeFrame, the render path changes.

Play from 12:27 The loader sends a message out of the frame, asking for the bid with this hb_adid.

Play from 12:34 Prebid on the page replies with the ad.

Play from 12:38 The loader then builds a frame of the right size inside the SafeFrame, and renders the ad there.

Play from 12:44 Same ID, same result. One extra conversation across the frame.

Play from 12:51 Here's Prebid's guidance, in four parts.

Play from 12:54 Use SafeFrames for banner and native creatives.

Play from 12:58 Some formats, like rich media, can't render inside a SafeFrame.

Play from 13:03 Some bidders don't support SafeFrames. Check each bidder's documentation, or ask them.

Play from 13:09 And with send all bids, you can decide bidder by bidder.

Play from 13:14 So before launch, test creatives bidder by bidder. Here's a simple routine.

Play from 13:20 Use a test page, with test bids for one bidder at a time.

Play from 13:24 Serve each test inside a SafeFrame, and outside one.

Play from 13:28 Check three things each time. The ad appears at the right size. A click opens the landing page. And any expanding ad expands.

Play from 13:38 Note the results in a short table, one row per bidder and format. When a new bidder joins, it gets a new row before it gets traffic.

Play from 13:48 Native follows the same pattern, with a different creative.

Play from 13:52 Native line items target hb_format equals native.

Play from 13:58 The creative uses an Ad Manager native style, built from your site's own design.

Play from 14:03 The loader fetches the winning bid's assets, like the title, image and sponsor, and fills them in. Prebid's docs describe the template options.

Play from 14:14 Video is different again.

Play from 14:17 Video usually gets its own ladder, often on custom buckets, because video prices run higher.

Play from 14:24 The creative is a VAST redirect, not a script. It points the video player at Prebid Cache.

Play from 14:31 The hb_uuid key tells the cache which video ad to return. With send all bids, each bidder has its own version of that key.

Play from 14:41 Same keys, same ladders, a different creative at the end.

Play from 14:47 Three mistakes we see here.

Play from 14:49 One: every Prebid creative forced into a SafeFrame, including a bidder whose rich media needs to expand. Its ads render small, or blank.

Play from 15:01 Two: native line items sharing banner creatives. The bid wins, and the assets never appear.

Play from 15:08 Three: video bids flattened at a twenty-dollar banner cap, because nobody built a video ladder.

15:16Floors in two places

Play from 15:17 Chapter four: floors. A floor is the lowest price you'll accept. You can set one in two places, and they don't automatically agree.

Play from 15:28 Here's where each layer acts.

Play from 15:31 Bids arrive from your partners, in the browser.

Play from 15:34 Prebid's Price Floors module checks them first. Bids below the floor are rejected, and never reach Ad Manager.

Play from 15:41 The surviving bids become key-values, and travel to Ad Manager.

Play from 15:46 Inside Ad Manager, pricing rules set floors for Google's demand, and for remnant line items, including your Prebid ladder.

Play from 15:54 Two layers means two places to make mistakes. Let's take each one properly.

Play from 16:01 First, Prebid's layer.

Play from 16:03 Floors are rules. They can vary by media type, size, ad unit or domain.

Play from 16:10 Bids below the matching floor are marked as rejected.

Play from 16:14 Prebid also passes the floor to bidders that support it, so they can bid with it in mind.

Play from 16:20 And a minimum floor can sit underneath every rule, as a safety net.

Play from 16:26 Here's why one fixed floor rarely lasts. Illustrative shape, not real data.

Play from 16:32 Bid prices move through the day, by size, by country and by device.

Play from 16:38 A static floor is one flat line. Too high at quiet times, blocking good bids. Too low at peak.

Play from 16:46 Prebid's own docs advise against static floors. Their words: blunt tools that you'll forget to update.

Play from 16:53 The module can fetch fresh rules from an endpoint instead, from your own data or a floor provider. RediAds' Jeanie AI is one such provider: it adjusts floors and bidder behaviour from live performance signals. Whichever you use, test it with a split, as you'll see in Chapter 5.

Play from 17:13 Now Ad Manager's layer. In December 2025, Google renamed unified pricing rules to simply pricing rules.

Play from 17:22 They apply to Google's open and private auctions, to Open Bidding, and to AdSense backfill.

Play from 17:29 They also apply to remnant line items: price priority, network and bulk. That includes your Prebid ladder.

Play from 17:38 They don't apply to programmatic direct deals, or to house line items.

Play from 17:43 And a network can have up to two hundred active pricing rules.

Play from 17:49 Each pricing rule offers two main ways to price.

Play from 17:52 A floor price is fixed. The winning bid must be at least that price.

Play from 17:58 A target CPM is the default. Google adjusts the actual floor automatically, aiming at your target while balancing fill and yield.

Play from 18:08 Since December 2025, a rule can also set different floors for specific programmatic bidders.

Play from 18:15 Whichever you use, remember the scope. If the rule covers price priority, it covers your Prebid rungs too.

Play from 18:24 Here's the cold open, worked through. Illustrative.

Play from 18:28 Prebid's floor: one dollar. Ad Manager's pricing rule on the homepage: one fifty, covering remnant line items.

Play from 18:37 A bid of one dollar thirty-two arrives. It passes Prebid's floor, and its key says one point three zero.

Play from 18:45 The one-thirty rung matches. But its rate is below the pricing rule, so it isn't allowed to compete.

Play from 18:53 Ad Manager's delivery tools would list that line item as below the pricing rule floor. Every bid between one dollar and one fifty is now wasted.

Play from 19:04 Let's see what a floor really does. Four test bids, and no floor yet.

Play from 19:37 RediAds at two thirty-seven, Index at two twelve, Sovrn at one ninety-six, OpenX at one fifty-two. All four are eligible.

Play from 19:54 Now the same page with a Prebid floor of two dollars five on banner. Two bids left. And here are the other two, rejected in the browser before Ad Manager ever saw them.

Play from 20:02 What does Ad Manager receive now? Only the survivors' keys. The winner hasn't changed, and its bucket hasn't changed. Notice that. Here, the floor didn't raise the price of the winning bid at all. It removed the losers.

Play from 20:06 Now let's push it. A floor of two fifty. The targeting is empty. Prebid sends nothing to Ad Manager for this slot. The impression goes to whatever demand is left, Ad Exchange, a house ad, or nothing.

Play from 20:08 That's the point to remember. A floor doesn't raise a bid. It removes the bids below it. Whether that earns you more depends on what happens to the impressions it removes.

Play from 20:11 Halfway check. Pause the video if you'd like to work it out.

Play from 20:21 Prebid's floor is one dollar. An Ad Manager pricing rule of one fifty covers your Prebid line items. You use medium granularity. A bid of one dollar fifty-four arrives. Can its line item compete?

Play from 20:31 Yes, just. Medium rounds one fifty-four down to one point five zero. The one-fifty rung meets the one-fifty pricing rule, so it competes. A bid of one forty-nine would not. Its rung is one forty.

Play from 20:48 Now the other side of the auction: Ad Exchange. Illustrative prices.

Play from 20:53 A bidder's real offer is two dollars thirty-seven.

Play from 20:57 On medium, your line item enters at two thirty.

Play from 21:01 Ad Exchange bids two thirty-three. It beats the line item, so it wins, even though the header bid was higher.

Play from 21:09 On dense, the rung would be two thirty-seven, and the header bid would win. Your bucket, not the real bid, is the price Ad Exchange has to beat.

Play from 21:21 So how do you keep two floor layers from fighting? Four habits.

Play from 21:26 Give floors one owner. One person, or one team, signs off every change in either layer.

Play from 21:33 Write down which layer does what. For example, Prebid protects against very low bids, and Ad Manager prices Google's demand.

Play from 21:42 When a pricing rule covers price priority, check which Prebid rungs fall below it. Those rungs can never win there.

Play from 21:50 And change one layer at a time. Otherwise, you'll never know which change did what.

Play from 21:58 Three floor mistakes we see.

Play from 22:00 One: a pricing rule added for Ad Exchange, without noticing it also covers the Prebid ladder.

Play from 22:08 Two: a Prebid floor raised to lift CPM, when what it really did was hand impressions to cheaper demand.

Play from 22:15 Three: floors changed in both layers in the same week. Revenue moves, and nobody can say why.

22:25Split-test design

Play from 22:25 Chapter five. Never roll out a floor, granularity or creative change to everyone at once. Split the traffic, and let the numbers decide. Here's how to design a test you can trust.

Play from 22:40 Before any traffic moves, write four lines.

Play from 22:44 The change. Exactly one. For example, raise the Prebid banner floor from fifty cents to eighty.

Play from 22:52 The question. Does it raise revenue per thousand sessions?

Play from 22:56 The verdict metric, chosen now, not after you see the results.

Play from 23:01 And the duration. At least two full weeks, so every weekday and every weekend appears in both groups.

Play from 23:11 Next, decide what gets split: auctions, or people.

Play from 23:16 Splitting by auction is simple. Each auction is randomly assigned. Prebid's Floors module does it this way.

Play from 23:24 Splitting by user or by page view keeps one person's experience consistent. You assign the group yourself, for example with a random number stored for the session.

Play from 23:35 Floors usually split well by auction. Changes people can feel, like refresh or lazy loading, are better split by user.

Play from 23:45 For floors, Prebid gives you two built-in ways to split.

Play from 23:49 Skip rate: a percentage of auctions where floors are skipped. A skip rate of ten leaves about one auction in ten without floors. That's your control.

Play from 24:01 Model groups: two or more floor models, each with a weight. Prebid normalises the weights. Weights of twenty and fifty send about twenty-nine percent of auctions to the first model.

Play from 24:14 Both are recorded on each bid request, so your analytics can tell the groups apart.

Play from 24:21 Prebid's analytics can see the groups. Ad Manager can't, unless you tell it.

Play from 24:27 Assign the group on the page, then set it as a page-level key-value. For example, a key called rd underscore test, with values a and b.

Play from 24:38 Create that key in Ad Manager, with both values predefined.

Play from 24:43 Switch reporting on before the test starts. No backfill, remember.

Play from 24:48 Now every Ad Manager report can be split by group, including Ad Exchange revenue, not just Prebid's.

Play from 24:57 Now the size of each group.

Play from 24:59 A fifty-fifty split gives a clear answer fastest. But half your traffic carries the risk.

Play from 25:06 A ninety-ten split is safer. But the small group is noisy, so the test must run longer.

Play from 25:14 Here's a habit worth adopting: run an A A test first. Same set-up in both groups, for a week. Illustrative.

Play from 25:22 The gap you see between two identical groups is your noise. Any real result has to beat it clearly.

Play from 25:31 Let's put the whole design on one page. Illustrative.

Play from 25:36 The change: Prebid banner floor from fifty cents to eighty, on article pages only.

Play from 25:42 The split: by page view, so Ad Manager can see it. The page picks group a or b at random, eighty to twenty, and loads the matching floor. Group a keeps the old floor, as control.

Play from 25:57 The label: rd underscore test, set to a or b, reportable before launch.

Play from 26:04 The timing: one week of A A, then two full weeks of the real test.

Play from 26:09 And the decision rule, written in advance: keep the change only if revenue per thousand sessions rises by more than the A A noise.

Play from 26:20 When you compare the groups, watch three numbers together.

Play from 26:24 CPM. Higher floors usually push it up, which looks great on its own.

Play from 26:31 Fill rate. The same floors can leave more impressions unsold, or hand them to cheaper demand.

Play from 26:38 Revenue per thousand sessions. It combines price and fill, across all demand. It's the only verdict that counts.

Play from 26:48 Here's a worked example. Illustrative numbers. Three ad slots per session in both groups.

Play from 26:55 Control: CPM one dollar twenty, fill ninety-two percent. Revenue per thousand sessions: three dollars thirty-one.

Play from 27:05 Test, with higher floors: CPM one thirty-eight. Up fifteen percent.

Play from 27:11 But fill falls to seventy-eight percent. Revenue per thousand sessions: three dollars twenty-three.

Play from 27:18 CPM rose fifteen percent. Revenue per session fell about two and a half percent. You'd keep the control. If your A A noise is bigger than that gap, you'd keep testing before deciding.

Play from 27:33 One caution before you trust any Ad Manager number.

Play from 27:37 Ad Manager values a Prebid impression at its line item's rate. That's the bucket, not the real bid.

Play from 27:44 So two thirty-seven bids served at the two-thirty rung appear as two thirty.

Play from 27:50 For a test, that's fine, as long as both groups use the same ladder. For finance, reconcile with your partners' reports. Module 8 shows how.

Play from 28:02 Three split-test mistakes we see.

Play from 28:05 One: comparing this month with last month and calling it a test. Seasons, news and budgets all changed too.

Play from 28:15 Two: changing two things at once. Floors and granularity in one test gives you one answer to two questions.

Play from 28:24 Three: a test key that wasn't reportable from day one. The test runs, and the Ad Manager side of the answer is missing.

28:33Run it like ad ops

Play from 28:34 Last chapter. Everything from Modules 5 and 6, turned into one checklist with twelve lines. Run it before every Prebid launch, and again whenever a bidder, a size, a granularity or a floor changes.

Play from 28:51 Part one covers the build, before traffic touches it.

Play from 28:55 Ad unit codes match the div IDs on the page.

Play from 28:59 The ladder mirrors your price buckets exactly, with matching decimals.

Play from 29:05 Every Prebid line item is price priority, with its rate equal to its rung.

Play from 29:11 Keys exist, predefined where possible, and reportable from day one.

Play from 29:16 Long bidder keys use the cut twenty-character names, in targeting and in creatives.

Play from 29:23 And every line item has enough creative copies for every slot that could win at once.

Play from 29:30 Part two covers launch, and everything after it.

Play from 29:35 The creative renders on a real page before traffic. Check SafeFrame behaviour for each bidder and format.

Play from 29:42 No pricing rule blocks Prebid rungs by accident.

Play from 29:46 Floors change in one layer at a time.

Play from 29:49 Every change runs as a split, with a reportable test key.

Play from 29:53 Revenue per thousand sessions is reviewed every week, not just CPM.

Play from 29:58 And line items are built and changed with a tool, never by hand.

Play from 30:04 Share both halves with whoever traffics line items, so the checks don't live in one person's head.

Play from 30:11 Three myths we hear a lot from publishers.

Play from 30:14 Myth one: higher floors always mean higher revenue. They raise CPM, but they can cut fill, or hand impressions to cheaper demand. Revenue per session is the judge.

Play from 30:28 Myth two: send all bids is always better. You get richer reports, but you pay in keys, line items and request size. Choose it because you'll use the reports.

Play from 30:40 Myth three: Ad Manager's pricing rules only affect Google's demand. If they cover price priority, they cover your Prebid ladder too.

Play from 30:51 Let's recap Module 6.

Play from 30:54 Send all bids buys reporting and per-bidder control, and costs line items, keys and request size.

Play from 31:02 A winning Prebid creative renders through one ID, hb_adid, with a direct call or a message across a SafeFrame.

Play from 31:13 Prebid's floors reject bids in the browser. Ad Manager's pricing rules can block your Prebid rungs too.

Play from 31:21 Every change is tested on a split, with the group carried into Ad Manager.

Play from 31:27 And revenue per thousand sessions is the verdict.

Play from 31:32 Quick check. Pause the video if you want to think.

Play from 31:40 A floor test raises CPM by twelve percent, but revenue per thousand sessions falls by three percent. Your A A test showed about one percent of noise. Do you keep the new floors?

Play from 31:49 No. Revenue per session already combines price and fill, and a three percent fall is clearly bigger than your noise. The higher CPM came at the cost of too many lost impressions.

Play from 32:04 One more. Your Prebid creatives serve inside SafeFrames. How does the creative get the winning ad?

Play from 32:11 It sends a message out of the frame to Prebid on the page, asking for the bid with this hb_adid. Prebid replies with the ad, and the creative renders it.

Play from 32:25 Your set-up now receives, renders and prices every header bid, and you can prove each change with a split.

Play from 32:35 In Module 7, we go hunting. A repeatable routine for debugging Prebid and Ad Manager, and four real-feeling cases, from a blank ad to a bucket mismatch.

Play from 32:47 That's Module 6. You can now choose how bids travel, trace how they render, keep two floor layers in step, and test every change properly.

Play from 32:59 Want to practise first? Try the levels in the RediAds Academy on blog dot rediads dot com.

Play from 33:05 And when you want a partner for any of this, the RediAds team is at rediads dot com. See you in Module 7.