TL;DR
Your Shopify purchase value reaches Google Ads with tax and shipping inside it. On a store selling into several VAT markets, Smart Bidding counts each country's VAT as revenue, and the VAT share differs by country. A Location value rule corrects the bidder without touching the tracking, using the formula Shopify itself uses to pull tax out of a tax-inclusive price. Settle two constraints first, restate the target the same day, and know which orders the correction gets wrong.
Key Takeaways
- The Multiply factor for a tax-inclusive value is 1 ÷ (1 + rate), which follows from Shopify's own formula, Tax = (Tax Rate × Price) ÷ (1 + Tax Rate) [7].
- Multiply accepts values from 0.5 to 10 and Add accepts only positive values, so Multiply is the only proportional way to lower a value [2].
- Only one value rule applies to a given conversion, and every rule in the account must use the same condition types [2]. Choosing Location for VAT decides the account's scheme.
- Restate Target ROAS on the day the rules go live: new target = old target × factor, so 400% becomes about 331% at an illustrative 21%.
- Rules apply to Search, Shopping, Display, Hotel and Performance Max campaigns per Google's set-up page [2]; values adjust on manual and Target CPA campaigns too, but only value-based strategies optimize to them [4].
- After a day of uploads, check
Segment → Conversions → Value rule adjustmentin the campaigns report [4] and the app's action's value in the conversion actions table [2].
What number goes in each rule?
The reciprocal of one plus the tax rate. Shopify's help page on tax-inclusive pricing gives its formula for extracting tax from a price: Tax = (Tax Rate × Price) ÷ (1 + Tax Rate) [7]. Subtract that from the price and the net share is exactly 1 ÷ (1 + Tax Rate). That share is your Multiply factor.
Whether the value should include tax and shipping at all is settled in should your Shopify purchase value include tax and shipping. This picks up where that one ends: your value is gross, you're keeping it gross, and you want the bidder to see something close to net.
Run the arithmetic on illustrative rates. Look up the current rate for each country you sell into; these only show the math.
| Illustrative VAT rate | Multiply factor | A 100.00 gross value becomes | A 400% tROAS restated |
|---|---|---|---|
| 19% | 0.840 | 84.03 | 336% |
| 20% | 0.833 | 83.33 | 333% |
| 21% | 0.826 | 82.64 | 331% |
| 25% | 0.800 | 80.00 | 320% |
| 27% | 0.787 | 78.74 | 315% |
All five sit inside Google's 0.5 to 10 range for Multiply [2]. The floor would only bite above a 100% rate.
To take shipping out as well, use the reciprocal of that article's composition multiplier (order total ÷ line-item prices before tax and shipping, as that article defines it), computed on the country's orders. Its illustrative store, 21% VAT plus shipping at 6% of the subtotal, has a multiplier of about 1.28, so the factor is 0.780. It has to be one number. Add only takes values "greater than 0" [2], so no rule subtracts a shipping amount.
With mixed goods there's a better number than the standard rate. Export the last 30 days of orders by date, filter the Shipping Country column to the country, sum the Taxes and Total columns [8], and use 1 − (Taxes ÷ Total). A single-rate store gets the table's answer; a store with reduced-rate goods or tax-exempt customers gets the blended share it actually collected.
Why a location rule is legitimate here
Google cautions against rules that duplicate what Smart Bidding already sees: "Smart Bidding already uses signals like geography, device, and first-party audience lists (when applied). If a user in one of those segments converts better, and this is reflected in your reporting, Smart Bidding already accounts for that" [1]. So a rule that says "shoppers in Germany are worth more" usually second-guesses the bidder.
Tax is the opposite case: every country's value arrives gross, so the inflation is exactly what your reporting doesn't reflect. Google pitches rules as a way to "provide additional value information that isn't already reflected in your account" [1], and a per-country VAT factor fits that better than most rules people build.
The tracking stays as it is. On a store running WeltPixel Conversion Tracking, the app uploads the Shopify order total (tax, shipping and discounts applied) to the offline-import conversion action you picked. Every destination gets that same total; the app never sends a subtotal, and it never creates, edits or reads value rules. Google Ads is part of the Plus plan. The rule lives in Google Ads, which works "without having to change tagging code" [1].
Two neighbours to keep out of the rule. A rule is a percentage, so it won't fix a currency mismatch. And if the goal is paying more for first orders, use the customer lifecycle goal's New Customer Value mode ("Bid higher for new customers than existing ones", which needs "at least one Purchase conversion goal" [6]). The new-or-returning label the app attaches for that on the Plus plan is covered in new vs returning customer tracking on Shopify. Don't build an audience value rule for it.
Two constraints to settle before you build
The first is per conversion. "No matter how many rules are set up, only one rule can be applied to a given conversion" [2]. When several location rules could match, "the most precise location rule is applied" [2]. A VAT rule and a later high-value-audience rule never combine on one conversion. One wins.
The second is account-wide. "All value rules in your account must use the same type of primary and (optional) secondary conditions," and changing the type means you "delete all value rules and create new rules with the consistent conditions" [2]. Pick Location for VAT and the account's primary condition is Location from then on. A later device or audience rule means the VAT rules come down first. Write the scheme down before you touch the account:
- Primary condition: Location, one rule per VAT country, country level only. A city or region rule would outrank the country rule on precision [2] and quietly replace its factor.
- Secondary condition: leave it empty unless you already need one, since every rule must carry the same type [2].
- Scope: account-wide, or attached to specific campaigns. In the API a campaign-level rule set takes precedence for that campaign, so account-level VAT rules stop applying wherever a campaign has its own rule [5].
- Manager accounts: "If you are using cross-account conversion tracking, you must set your conversion value rules from the manager-level account" [2].
How do you set the rules up and restate the target?
A new rule changes what Smart Bidding optimizes toward at auction time [3], which puts it on the list of things to lock before Black Friday.
- Confirm which action carries bidding. A rule only changes bids through the action the bidder reads, and on a server-side store that's the action the app uploads to. If you haven't verified which action is primary, do that first with the primary conversion action guide.
- Open
Goals → Conversions → Value rulesand select Create conversion value rule [2]. - Choose Location as the condition and select the country. Selections inside one rule are treated as "or" [2], so countries sharing a rate can share a rule.
- Choose Multiply and enter the factor for that country.
- Choose the scope, account or specific campaigns, and save. Repeat per rate.
- The same day, restate every Target ROAS the rules touch. The bidder now sees value × factor, so an unchanged 400% target behaves like 400% × 1.21, or 484%, on the old gross basis, and the campaign spends less. The equivalent target is 400% ÷ 1.21, about 331%. For a campaign spanning several VAT countries, use the factor weighted by each country's share of the campaign's conversion value.
- Write the reconciliation note: which accounts carry rules, which factor per country, and the date they went live.
Step 6 is the one people skip. Don't. Without it, the rule shows up as a spend drop nobody connects to a settings change. Removing a rule reverses it: "If you remove a conversion value rule our system will resume optimizing for your current definition of value" [3].
Values also adjust "across all campaigns, including those using manual or Target CPA" bidding, while "only value-based bid strategies" optimize to them [4]. A manual-CPC campaign's reported value drops; its bids don't move.
Where the approximation goes wrong
The rule is right in aggregate for a consumer store selling at one rate per country, and wrong in four places.
It reads the ad interaction, not the order. Location matches "Physical location or location of interest" [5], which isn't the shipping or billing country. A shopper who clicks while travelling gets the factor of wherever they were, or of the place they searched about.
It hits orders that carry no tax. Reverse-charge business orders pay no VAT, yet the rule scales them down anyway. So do tax-exempt customers, who under tax-inclusive pricing are "still charged the full listed product price" [7], all of it revenue. A B2B-heavy store should use the blended 1 − (tax ÷ total) factor, or skip rules where most orders are exempt.
It treats reduced-rate goods at whatever rate you entered. Same fix.
It can't go below 0.5 or subtract. Irrelevant for VAT, where the table bottoms out at 0.787.
Did the rule actually touch the app's uploads?
Google's help pages don't sort value rules by how a conversion arrived. They scope rules by campaign type [2], by conversion category and by the ad interaction's audience, location and device [5], and the API says an empty category list means the rule set "applies to all categories" [5]. Google names "offline conversion value" among the goals [1]. No page we found names conversions uploaded through the API. So check your own account instead of trusting anyone's summary, ours included.
- Wait for a day of uploads after the rules go live.
- In the campaigns report, open
Segment → Conversions → Value rule adjustment[4]. - Look for a row labelled "Original conv. value (rule applied)" with a value, next to "Original conv. value (no rule applied)" and a Location row showing the net adjustment [4]. Because the segment is campaign-level [4], it proves the uploads were adjusted only when the app's action is the only valued conversion action in those campaigns.
- In the conversion actions table, compare the app's action's conversion value with the Shopify order totals for the same days. With the rule applied it should sit near gross × factor [2].
- Add the "All value adjustment" and "Value adjustment" columns [4] if you want the adjustment beside the value.
The two "Original conv. value" rows add up to the total original value [4], which is your gross figure for reconciliation. Expect a short mixed period in the first days, since Google doesn't document how uploads for clicks from before the rule existed are treated.
You've probably fielded the question already: why is Google Ads ROAS lower than the finance deck's? The systems now disagree by design. Google Ads reports roughly net; Shopify, GA4 and Meta still report the gross order total, because the rule changes Google Ads and nothing upstream. Keep the reconciliation note next to the ROAS reconciliation method, and use the segment's original values when you report one blended ROAS across Meta and Google Ads.
FAQ
Do Google Ads conversion value rules apply to offline or API-uploaded conversions?
Google scopes value rules by campaign type, conversion category and the ad interaction's location, audience and device, and names offline conversion value as a use case [1][2][5]. No Google page we found names API-uploaded click conversions, so confirm it on your own account with the check above [4].
Can I subtract shipping with a value rule?
No. Add only accepts positive values [2]. Use one Multiply factor equal to 1 ÷ (the composition multiplier from that article), which removes tax and shipping together as a proportion.
Why did my spend drop after I added value rules?
The bidder now sees lower values against an unchanged Target ROAS. Restate the target as old target × factor on the day the rules go live, or remove the rule and Google resumes optimizing on the original values [3].
Do value rules change what Shopify or GA4 report?
No. The rules act inside Google Ads only. Shopify keeps its order total, and GA4 and Meta keep the gross total the app sends them.
Keep the tracking gross and correct the bidder
WeltPixel Conversion Tracking uploads the Shopify order total of each conversion it sends to the Google Ads conversion action you pick, with the order ID attached, and leaves value rules, goals and targets in your account. Build the VAT rules there, restate the target the same day, and check the adjusted values the morning after.
Sources
- Google Ads Help, "About conversion value rules", support.google.com/google-ads/answer/10518330, accessed September 30, 2026
- Google Ads Help, "Set up conversion value rules" (campaign types; Add and Multiply limits; one rule per conversion; condition types; manager accounts), support.google.com/google-ads/answer/10520348, accessed September 30, 2026
- Google Ads Help, "Impact of conversion value rules on Smart Bidding and performance", support.google.com/google-ads/answer/10520545, accessed September 30, 2026
- Google Ads Help, "View your conversion value rules report" (Value rule adjustment segment), support.google.com/google-ads/answer/10519848, accessed September 30, 2026
- Google Ads API, "Conversion value rules", developers.google.com/google-ads/api/docs/conversions/conversion-value-rules, accessed September 30, 2026
- Google Ads Help, "About customer lifecycle goals", support.google.com/google-ads/answer/12080169, accessed September 30, 2026
- Shopify Help Center, "Include taxes in product prices", help.shopify.com/en/manual/taxes/include-exclude-taxes, accessed September 30, 2026
- Shopify Help Center, "Export orders", help.shopify.com/en/manual/fulfillment/managing-orders/exporting-orders, accessed September 30, 2026