ROAS
Revenue ÷ Ad spend
MerchantPro stores often report strong Shopping ROAS on popular SKUs while acquisition cost (cost_net / cost_gross) and fees quietly erase contribution.
MerchantPro merchants: connect via API, sync catalog cost_net / cost_gross, upload POAS conversions to Google Ads, and automate product labels — while keeping ROAS visible for revenue reporting.

Revenue ÷ Ad spend
MerchantPro stores often report strong Shopping ROAS on popular SKUs while acquisition cost (cost_net / cost_gross) and fees quietly erase contribution.
Gross profit ÷ Ad spend
Profit Bid imports MerchantPro catalog costs, maps order lines to gross profit, and uploads POAS-weighted conversion values — Smart Bidding follows margin, not cart total.
MerchantPro stores sync acquisition costs and orders into POAS — upload profit conversions to Google Ads and compare revenue ROAS with contribution margin.
MerchantPro Shopping ROAS often stays flat while POAS rises once cost_net / cost_gross feeds Smart Bidding.
One MerchantPro sync powers POAS upload across linked ad platforms.
Profit Bid subtracts MerchantPro costs before calculating POAS conversion values.
Connect MerchantPro via API — map cost_net / cost_gross and upload POAS to Google Ads in under 30 minutes.
Connect with MerchantPro API User credentials. Add order webhooks later for live sync, or rely on scheduled catalog and order pulls.
Import MerchantPro cost_net / cost_gross into Profit Bid COGS so POAS uses purchase cost, not a static margin guess.
Send POAS-weighted values to Google Ads and other linked ad platforms tied to your store domain.
Label MerchantPro catalog winners and losers by POAS tier and sync labels into Shopping campaigns.
Keep revenue ROAS for reporting while Smart Bidding and budgets follow contribution profit.
Run MerchantPro alongside Woo, Shopify, or other platforms on Growth+ — same license, mixed stack.
Create an API User in MerchantPro Settings → API and webhooks, then connect from Profit Bid My Account.
Choose cost_net or cost_gross as the COGS import source and sync the catalog.
Authorize Google Ads (and other ad platforms). Map the primary purchase conversion action.
Enable POAS conversion upload. Optionally paste the MerchantPro webhook secret for live orders.
Turn on A/C/X labels once COGS coverage is solid — exclude X SKUs from paid traffic.
MerchantPro merchants in Romania and EU markets use Profit Bid to feed purchase-cost POAS into Google Ads instead of revenue-only ROAS.
Create an API User in MerchantPro, enter store URL, username, and password in Profit Bid Connect store, then sync products. Webhooks are optional for live order updates.
Use cost_net (ex-VAT) when your finance reports exclude VAT. Use cost_gross only if your acquisition cost is stored VAT-inclusive.
Yes — Growth and above include multiple store slots. Connect each MerchantPro shop separately, or mix with other platforms under one license.
Yes. Dashboards keep ROAS for revenue KPIs while conversion upload and labels use POAS.
More answers on our FAQ page.
$14.99/ month
$29For one store getting started with profit-based bidding






$39/ month
$59For brands that need a second store — same platform or mixed






$79/ month
$119For multi-store teams with advanced Google Ads






$149/ month
$199For agencies and high-volume merchants






14-day free trial available — start free · full pricing details
Connect your store, upload POAS conversions, and see ROAS vs POAS in one workspace.