Has Anyone Successfully Implemented Bid by Profit Margin ...
Based on an r/PPC community discussion
Bidding by profit margin is one of those strategies that sounds obvious in theory but gets genuinely complicated in practice. A common question in the r/PPC community is whether anyone has actually pulled this off at scale — not just in a spreadsheet thought experiment, but in live campaigns with real data flowing into Google Ads. The honest answer is yes, it works, but the implementation requires a level of data infrastructure that most advertisers aren't ready for on day one. If you've ever lost money on a sale because Google optimized for revenue instead of margin, this guide is for you.
Most Google Ads accounts are set up to optimize for revenue or conversion value — which sounds correct until you think about it for five minutes. If you sell 500 products with margins ranging from 8% to 72%, telling Google to maximize conversion value treats a $200 sale at 10% margin the exact same way as a $200 sale at 65% margin. You're optimizing for the wrong number.
This creates a predictable failure mode: Smart Bidding chases high-revenue, low-margin products because they generate big conversion values. Your ROAS looks great. Your actual profit looks terrible. You're busy congratulating yourself on a 600% ROAS while your accountant is quietly losing their mind.
The fix isn't to stop using Smart Bidding — it's to feed Smart Bidding the right signal. That signal is profit, not revenue.
There's no single implementation path here. Based on managing campaigns across retail, SaaS, and lead-gen accounts with complex margin structures, I've seen three distinct approaches that actually work in production environments.
This is the cleanest and most scalable method. Instead of firing a conversion with the order revenue, you fire it with the gross profit dollar amount. If a customer buys a product for $150 and your margin on that SKU is 40%, you pass $60 as the conversion value.
Implementation requires:
For example, if your target is to spend no more than 30% of gross profit on ads, your tROAS target should be set to roughly 333% (1 ÷ 0.30 × 100). This is a fundamentally different number than what most teams are used to — and it confuses stakeholders until you walk them through the math once.
If passing dynamic margin values at the tag level is too complex for your current stack, segmenting your products into margin tiers and managing them in separate campaigns is a viable middle ground.
A typical segmentation looks like this:
| Margin Tier | Gross Margin Range | tROAS Target | Bidding Strategy |
|---|---|---|---|
| Tier 1 (High Margin) | 50%+ | 150–250% | Maximize Conversion Value with tROAS |
| Tier 2 (Mid Margin) | 25–49% | 300–450% | Maximize Conversion Value with tROAS |
| Tier 3 (Low Margin) | <25% | 500–700% | Target ROAS (aggressive efficiency) |
| Loss Leader / Clearance | <10% | Exclude or CPA-based | tCPA or manual bidding |
The downside of this approach is operational complexity — you're managing more campaigns, your Shopping feed needs labels to segment products, and when a product's margin changes, you need a process to move it between campaigns. It works, but it's more maintenance than the dynamic margin tag approach.
This is the least automated option but requires the least technical lift. You pull margin data into a reporting layer (Looker, Data Studio, or even a well-structured spreadsheet), calculate your true profit-per-click at the ad group or campaign level, and use that data to make manual bid adjustments or portfolio bid strategy decisions.
As practitioners often discuss in forums like r/PPC, this approach is most useful for accounts with fewer than 20–30 campaigns where a human can reasonably review and act on the data weekly. It breaks down fast at scale.
The biggest barrier to profit-margin bidding is the data pipeline. Most advertisers have their margin data somewhere — an ERP, a Shopify metafield, a master SKU spreadsheet — but getting it to fire on the conversion tag at the moment of purchase requires a specific setup.
This is the gold standard. Your development team pushes a data layer object at the confirmation page that includes:
Your GTM conversion tag then reads the total margin value variable and fires that to Google Ads instead of revenue. The math happens server-side or in the data layer, which keeps it accurate and prevents margin data from being exposed to end users.
If you're already using server-side tagging (which you should be for match rate reasons), you can enrich the conversion hit server-side before it goes to Google. The flow looks like this:
This approach keeps all margin logic server-side, is more resilient to ad blocking, and gives you a single place to update margin logic without touching front-end code.
If you're running Shopping or PMax and want to go the tier-segmentation route, Google's custom labels (0–4) in your product feed are your mechanism. You can programmatically assign a margin tier label in your feed management tool (Feedonomics, DataFeedWatch, GoDataFeed, or directly via Google Merchant Center supplemental feeds), then use those labels to structure your campaigns.
Here's the challenge nobody talks about enough: when you segment campaigns by margin tier or pass margin values instead of revenue, your conversion data gets fragmented. Smart Bidding needs roughly 30–50 conversions per month per campaign to function reliably. If you split one high-performing campaign into three margin tiers, you might drop each from 90 conversions/month to 30 — right at the edge of viability.
This is a real tension. The more granular your margin segmentation, the more accurate your bidding signal — but the less data each campaign has to learn from.
Practical solutions:
Even before you change your bidding strategy, making profit margin visible in your reporting creates immediate value. As the r/PPC community discussion notes, tracking profitability based on profit margin helps make profitability data visible through reports — and that visibility alone often surfaces optimization opportunities that would otherwise be invisible.
If you're passing margin as conversion value, your standard "Conv. value" and "Conv. value / cost" (ROAS) columns are now showing margin data. But you'll want additional calculated columns:
In Google Ads, you can create custom columns for most of these using the "Custom Columns" feature in the reporting interface. Gross profit generated is a simple formula: [Conv. value] - [Cost]. This single column often changes conversations with clients more than any other metric — suddenly you're looking at campaigns that look healthy on ROAS but are actually destroying margin dollars at scale.
For more sophisticated margin reporting — especially if you need to blend Google Ads data with actuals from your ERP or financial systems — connecting your Google Ads data to a BI tool like Looker Studio, Tableau, or Power BI gives you the flexibility to build P&L-style dashboards by channel, campaign, or product category. This is particularly valuable when presenting to finance teams who want to see advertising cost of sales as a percentage of gross profit rather than revenue.
Margin-aware bidding works best when your account structure is built around business economics rather than just keyword or product taxonomy. Here's what that looks like in practice:
If you've read this far, you're serious about making this work. Here's how to sequence the implementation:
This isn't a weekend project — a proper margin-bidding implementation in a mid-size e-commerce account typically takes 6–10 weeks from data audit to full rollout. But the accounts I've seen make this shift consistently find 15–30% improvement in actual profit generated from the same ad spend. That's not a rounding error. That's the difference between a channel that's working and one that's quietly subsidizing your least profitable products.
The infrastructure investment is real. The payoff is larger.