Every unified ranking setup contains one number that settles an argument merchandising and retail media have been having for years: how far should an advertiser's money be allowed to move a product up the page?

In Pentaleap that number is called bid impact. It's set per ad unit by the retailer in Publisher Manager, and it controls how far a bid can move a product from its organic position.

Bid impact is a governance decision, not a technical setting. Whoever sets it is deciding how your site trades relevance against ad revenue on every page it touches. That decision belongs to merchandising and retail media together, agreed page by page and written down before go-live, not left to whoever happens to have access to the configuration screen.

TL;DR

• Bid impact is a setting, configured per ad unit in Publisher Manager, that controls how far a bid can move a product's position.
• It works in the positions your merchandising rules don't govern. Pinned products and other rules are enforced separately.
• The setting encodes a business priority, so neither merchandising nor retail media should own it alone. Agree it jointly and name one person to make changes.
• Agree it page by page. Shopper intent on a search results page is different from a browse or category page, and Pentaleap's own documentation recommends different settings for each.
• Some categories won't fit the page-level setting. List every exception in writing, with a reason next to each one.

‍

What is bid impact, in plain terms?

Bid impact is the dial that decides how much an advertiser's bid counts when Pentaleap ranks sponsored and organic products together.

Unified ranking scores sponsored and organic products in one decision, on compound margin: retail margin plus ad margin. Bid impact sets how much weight the bid carries in that decision. Turn it down and a sponsored product has to be a strong match for the shopper to move up. Turn it up and money does more of the work.

It's one of three controls that shape a page, and the other two are covered elsewhere. Merchandising rules, such as pinned products and category rules, are enforced by the same ranking layer, so a pin holds its position whatever anyone bids. We've covered that in detail in whether unified ranking overrides merchandising rules, along with the question of who decides how many sponsored products appear on a page. Bid impact governs what happens in the positions those rules leave open.

That makes it the setting with the most day-to-day influence on what shoppers actually see, and the one most likely to be changed quietly.

‍

Why isn't bid impact just a technical setting?

Because every position on the dial is a business choice with a winner and a loser.

Set bid impact high and bids do more of the work, which earns more on broad pages but lets weaker matches move up. Set it low and sponsored products stay close to their organic positions, which protects the page but gives advertisers less visibility for their money. Neither end is wrong in every case. Each one is a statement about what the page is for.

That's why it shouldn't sit with whichever team has the login. If retail media owns it alone, there's a standing incentive to nudge it up at the end of a soft quarter. If merchandising owns it alone, there's an equal and opposite incentive to nudge it down whenever a page looks busier than they'd like. Left unowned, it ends up set the way the thermostat in a shared office gets set: by whoever touched it last.

‍

Who should own the bid impact setting?

Merchandising and retail media should own it jointly, with ecommerce and search consulted, and one named person on your side responsible for making changes in the tool.

In Pentaleap, bid impact is configured by the retailer in Publisher Manager, alongside floor prices and the maximum number of ads per ad unit. That's the right place for it technically. The governance question is who on your side is allowed to change it, and what has to be true before they do.

A workable split looks like this. Merchandising and retail media agree the setting for each ad unit and any category exceptions. One person makes the change in Publisher Manager. Any change after go-live needs sign-off from both sides, against evidence both sides agreed to in advance. If you're mapping how these conversations get sequenced across your organization, getting ecommerce, search and finance to agree on a ranking change covers the wider version of this problem.

‍

Why agree on bid impact page by page?

Because bid impact is set per ad unit, and different pages carry different shopper intent.

A shopper on a search results page has usually told you exactly what they want. A shopper on a browse or category page is often exploring. A sponsored product that doesn't match a specific search is immediately, visibly wrong. The same product on a browsing page might be a reasonable suggestion.

Pentaleap's own developer documentation already makes this split. Its example setups use a medium bid impact for in-grid search and a higher one for browse pages, because browse results are broader than a search result set. Treat that as a starting point, and let your own test results settle the final number.

Some categories make the case sharper. In categories where shoppers search with very specific intent, a mismatched sponsored product costs more than a wasted impression, which we've looked at in why an irrelevant sponsored product costs pharmacy retailers most.

Agreeing page by page also stops the conversation from collapsing into one site-wide number that suits nobody. It's easier for merchandising and retail media to agree on twelve specific settings than on one abstract principle.

‍

How should you handle category exceptions?

Some categories won't fit the page-level setting. In Pentaleap, floor prices can be set for specific categories and searches, so a category where relevance matters more can carry a higher bar for sponsorship.

The governance agreement should list every exception explicitly, with a reason next to each one. An exception without a written reason is the first thing to drift.

Fixed slots are configured separately from fluid ones, which we covered in how to keep guaranteed placements in a relevance-ranked grid. A tile your sales team has sold at a fixed price is a separate decision from how much weight bids carry in the positions around it.

‍

What should change the setting after go-live?

Evidence both teams agreed to before go-live, and nothing else.

Pentaleap tests alongside your existing stack, with your current setup still running, so the first settings can be proven against your current page before anything is permanent. Agree in advance which results would justify moving the dial in either direction.

Merchandising will want organic conversion on the same pages tracked alongside sponsored clicks, so a gain in ad revenue can't hide a loss on the retail side. Here's how testing a ranking change on a slice of traffic works.

After the test, the same rule applies. If someone wants to move bid impact on an ad unit, they bring the numbers to both teams, both teams sign off, and the named owner makes the change. That takes slightly longer than one person adjusting a setting. It also means nobody discovers a changed page from a dashboard three weeks later.

‍

Three diagnostic questions

1. Who on your side could change how much a bid moves a product today, and would anyone else know they'd done it?
2. Have merchandising and retail media ever agreed, in writing, how much weight advertiser money should carry on your search results page?
3. What result would have to show up in a test before either team accepted a change to that weight?

‍

What does a bid impact agreement look like?

It fits on one page. For each ad unit, it lists the bid impact setting, any category exceptions with a reason for each, the named owner who makes changes, who signs off, and which test results would trigger a review.

That document is what turns bid impact from a quiet source of friction into a decision both teams can defend. It protects the retail media team's revenue from being dialed down every time a page looks crowded, and it protects merchandising from ad revenue targets being met by turning the dial up. Write it before go-live, while both teams are still in the same room for the same project.

‍

Key Takeaways

• Bid impact is a setting, configured per ad unit in Publisher Manager, that controls how far a bid can move a product's position.
• It governs the positions merchandising rules leave open. Pinned products and other rules are enforced separately by the same ranking layer.
• Every setting is a business choice between relevance and ad revenue, so merchandising and retail media should own it jointly, with one named person making changes.
• Agree the setting page by page. Pentaleap's documentation recommends a medium bid impact for in-grid search and a higher one for broader browse pages, as a starting point to test.
• Category exceptions belong in the written agreement, each with a reason, and floor prices can be set for specific categories and searches.
• Changes after go-live should follow evidence both teams agreed to in advance, starting with a test alongside your existing stack.

‍

Frequently Asked Questions

Who decides how much a bid can move a product's position? The retailer does. In Pentaleap, bid impact is configured by the retailer in Publisher Manager for each ad unit. Because the setting trades relevance against ad revenue, merchandising and retail media should agree it jointly, with one named person responsible for making changes.

What is bid impact in unified ranking? Bid impact is a setting, configured per ad unit, that controls how much weight a bid carries when sponsored and organic products are ranked together, and so how far a bid can move a product's position.

Can a high bid move a sponsored product above a pinned product? No. Pinned products and other merchandising rules are enforced by the ranking layer, so a pin holds its position. Bid impact applies to the positions that rules don't govern.

Should bid impact be the same on search and browse pages? Usually not. Search shoppers have stated a specific intent, and browse shoppers are exploring a broader set of products. Pentaleap's documentation recommends a medium bid impact for in-grid search and a higher one for browse pages, as a starting point to test against.

Can we set different floor prices for specific categories? Yes. In Pentaleap's Publisher Manager, floor prices can be set for categories and searches, so a category where relevance matters more can carry a higher bar for sponsorship.

Does unified ranking replace our search engine's ranking? No. Unified ranking uses the relevance your existing search and personalization system already produces, such as Google Vertex AI or Algolia, and ranks sponsored products against the same signals.