Wrong Google Ads conversion value: why it happens and how to fix it
The Google Ads conversion value is the number that tells your campaign how much each purchase is worth. When it arrives wrong, the problem does not stay in the report. The conversion shows up, the count looks normal, but the value comes in at zero, multiplied by one hundred, with shipping on one ord


The Google Ads conversion value is the number that tells your campaign how much each purchase is worth. When it arrives wrong, the problem does not stay in the report. The conversion shows up, the count looks normal, but the value comes in at zero, multiplied by one hundred, with shipping on one order and without it on the next, in another currency or counted twice. And if the campaign uses Target ROAS or Maximize conversion value, bids are now calculated on top of that wrong number.
A hypothetical example shows how this happens without anyone noticing. The store sells a product for BRL 189.90. The platform stores the price in cents, as the integer 18990. The conversion tag reads that field and sends the number as it came. In Google Ads, the purchase shows up with a value of BRL 18,990.00, ROAS looks excellent and the bid strategy learns that the click is worth one hundred times more than it is.
This article covers the seven most common causes, what Google's official documentation says about each one, the correct code and how to test before you trust the dashboard.
How the Google Ads conversion value reaches your account
In the most common setup, the value is reported by the Google tag (gtag.js) or by the Google Ads Conversion Tracking tag in Tag Manager, which fires on the confirmation page and sends the value, the currency and the transaction ID.
In the conversion action, you choose between two modes. In the first, every conversion gets the same value. In the second, "Use different values for each conversion", the value comes from the tag on each purchase, and you set a default value for the cases where no value arrives. For ecommerce, the second one is right: Google's help recommends transaction-specific values when each sale has a different value.
The Target ROAS help is explicit: Google Ads predicts future conversions and their associated values using the conversion values recorded by conversion tracking. The Google Ads conversion value the tag sends is the value the algorithm uses.
Seven causes of a wrong Google Ads conversion value
The table sums up the symptom of each cause and where it usually lives.
Cause | Symptom in Google Ads | Where to fix it |
|---|---|---|
Value as text ("R$ 189,90") | Value off from what was expected, or falls back to the default value | Data layer or GTM variable |
Value in cents | Value 100 times higher | Data layer (divide by 100 at the source) |
Wrong variable (subtotal vs. total) | Value swings with shipping and tax | Variable mapping in GTM |
Empty or undefined value field | Value at zero | GTM variable and data layer event |
Missing or non-standard currency | Value in the wrong currency, or converted | "Currency code" field in the tag |
No transaction ID | Purchase counted again on reload | "Transaction ID" field in the tag |
Two primary actions for the same purchase | Value doubled | Goals > Conversions (primary vs. secondary) |

1. Value as text, with a comma or "R$"
Google Ads help asks, in so many words, that you send the conversion value as a number, using a period as the decimal delimiter. In other words: 189.90, not "189,90" and not "R$ 189,90".
This is easy to get wrong on a Brazilian site, because the value displayed on the page follows the Brazilian format, with the "R$" symbol and a decimal comma. When the GTM variable reads the page text (a CSS selector that grabs the price from the screen, for example), it gets exactly that format. What Google does with a value outside the documented format is not something worth betting on. The fix is to handle the number at the source: the data layer receives the numeric order value, not the formatted text.
2. Value in cents
This is the case from the opening. Some payment systems represent amounts as integers in the smallest currency unit: the Stripe API, for example, expects 1099 to charge 10.99 US dollars. If the data layer passes that field along, the number is valid, it just means something else: 18990 cents are BRL 189.90, but Google Ads reads BRL 18,990. The symptom is unmistakable: a Google Ads conversion value about one hundred times higher than the real order value. The fix is to divide by 100 before putting the value in the data layer, not later in the tag, where the rule gets lost.
3. Wrong data layer variable: subtotal vs. total
There is no absurd value here, and that is why this error lasts for months. The tag reads ecommerce.value in one implementation and ecommerce.total in another; the store theme sends the subtotal for card payments and the total with shipping for Pix; one app pushes the value with tax and another without it.
For reference, the GA4 purchase event specification defines value as the sum of price times quantity of the items and says not to include shipping or tax, which have their own parameters (shipping and tax). You can decide that your Google Ads conversion value includes shipping, or that it is the profit margin, which Google also mentions as a possible value. What you cannot do is let the rule change from order to order.
4. Empty or undefined value field: the zero value
Tag Manager help has a sentence that explains a good share of zero values: if the "Conversion Value" field is empty or undefined, Google Tag Manager sends the value as "0".
This happens when the variable points to a key that does not exist in that event: the name changed in the data layer, the push happens after the tag fires, or the purchase event was rebuilt by a new app with a different structure. The conversion is counted, but its Google Ads conversion value is zero. And the Target ROAS help warns that conversion values must be greater than 0 for those conversions to qualify.
5. Missing or different currency
The currency code follows the ISO 4217 standard, with three letters: BRL for the Brazilian real. Google Ads help says that if the conversion tag does not specify a currency code, or does not use that standard, Google ignores the tag's currency and uses the currency set with the conversion action's default value. And when values arrive in a currency different from the account currency, Google Ads converts them using the daily average exchange rate.
In practice: a store that sells in reais and in dollars and does not report the currency on each purchase records the dollar sales as if they were reais. The same help stresses that the conversion tag in Tag Manager must have the currency parameter set, either fixed or as a variable.
6. No transaction ID: the purchase counted again
Google Ads help describes the scenario: if the customer goes back to the conversion page or reloads it, the same tag can fire again and a second conversion can be counted for the same order. The Google Ads conversion value doubles along with it.
The fix is the transaction ID, usually the order number. If two conversions from the same action arrive with the same ID, Google Ads treats the second one as a duplicate and does not count it. Two points the documentation highlights:
- The ID must be dynamic and unique. Hard-coding the same ID makes Google Ads process only the first conversion with that ID, which leads to undercounting.
- A variable that does not resolve is an invalid ID. The help lists error examples such as
{{ order_number }}showing up literally,undefinedor.transaction_id. And IDs with theGG_prefix mean your tag is not sending any ID at all: Google generated a temporary one.
What about counting? "One" counts one conversion per ad click, even if that click leads to several purchases: it is the option for leads. For purchases, the official recommendation is "Every" with a transaction ID. A purchase action set to "One" hides the second purchase from the same click, and its value disappears with it.
7. Duplicate tag or two primary actions for the same purchase
The last case is structural. The store has the Google Ads conversion tag and has also imported the purchase from GA4. Both actions are set as primary. Google Ads documentation on conversions from multiple sources explains that deduplication happens within a single conversion action, not across two different actions: if both are active in the same campaign, a single transaction can be counted twice.
Secondary actions are for observation only: they show up in "All conversions", but they are not used for bidding. The help on data discrepancies also recommends checking that non-purchase actions, such as page views or add to cart, are not set as primary with a value assigned, which inflates the total value.
Want to know whether any of these causes is on your site right now? Enter your site URL and see if Google Ads is receiving the right value.
Why a wrong conversion value is expensive
Target ROAS sets bids to maximize conversion value while trying to reach the average return you chose. Maximize conversion value tries to get the most value possible out of the budget. Both strategies use the recorded value as their target. Conversion value rules, which multiply values by location, device or audience, are also applied on top of the value that arrived: they multiply the error along with it.
Each cause pulls the bid in a different direction:
- Inflated value (cents, duplication, doubled action): the return looks bigger than it is, and the strategy may spend more on clicks that do not pay for themselves.
- Zero value: conversions with a value of zero do not qualify for Target ROAS; the campaign loses the signal from the very sales that happened.
- Inconsistent value (subtotal on one order, total on another): the algorithm compares orders measured with different rulers.
A wrong Google Ads conversion value does not stay in a report column. It goes straight into how much the campaign is willing to pay for the next click.
How to fix the Google Ads conversion value: the right code
There is only one rule: the value, the currency and the transaction ID are born from the order, in the format Google asks for, and the tag only passes them along.
The data layer on the confirmation page
The store developer pushes the purchase event to the data layer with the value already numeric, in reais, and with the order number. This is the GA4 ecommerce format, which Tag Manager reads without any adaptation (example values):
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({ ecommerce: null }); // clears the object from the previous event
window.dataLayer.push({
event: "purchase",
ecommerce: {
transaction_id: "5550001112223", // order number, unique and dynamic
value: 189.90, // number, decimal point, in BRL (never 18990)
currency: "BRL", // ISO 4217
shipping: 15.00,
tax: 0,
items: [
{ item_id: "SKU-123", item_name: "Product", price: 189.90, quantity: 1 }
]
}
});In Tag Manager, create three variables of the "Data Layer Variable" type: ecommerce.value, ecommerce.currency and ecommerce.transaction_id. In the Google Ads Conversion Tracking tag, connect each one to its field: "Conversion Value", "Currency Code" and "Transaction ID". The trigger is a custom event named purchase, as Google Ads help itself shows.
If the platform only delivers the value in cents, convert it before the push (value: order.total_in_cents / 100) and never in the tag. That way the Google Ads conversion value, the GA4 revenue and any other destination read the same number.
The Google tag (gtag.js) event snippet
Without Tag Manager, the event snippet on the confirmation page looks like this. The format is the same one Google Ads help uses in its examples, with the values of the example order:
gtag('event', 'conversion', {
'send_to': 'AW-CONVERSION_ID/CONVERSION_LABEL',
'value': 189.90,
'currency': 'BRL',
'transaction_id': '5550001112223'
});value as a number, currency as text in the ISO 4217 standard and transaction_id with the order number generated by the store's server, never fixed text.
How to test the Google Ads conversion value before trusting the dashboard

Do not wait for the next report to find out whether the Google Ads conversion value is right. The test takes a few minutes:
- Tag Manager Preview mode. Click "Preview", connect the site and place a test order. In the Tag Assistant panel, open the
purchaseevent, then the Google Ads tag under "Tags Fired", and check the values sent: the value is the order value, the currency is BRL, the transaction ID is the order number and it does not show up asundefined. - Second order. Repeat and confirm that the transaction ID changed.
- Reload the thank you page. The tag may fire again; with the same ID, Google Ads treats the second one as a duplicate.
- Network request. In Chrome, open DevTools, go to the "Network" tab, filter by
googleadservices.com/pagead/conversionand open the "Payload". Google's help notes that the transaction ID usually shows up in theoidparameter. - Action settings. In Goals > Conversions > Summary, open the purchase action and check: "Use different values for each conversion", "Every" counting and only one purchase action as primary for the same sale.
How to tell if your conversion value is wrong
You do not need a tool for the first screening. Pick a period with volume and compare three numbers:
- Revenue from paid orders on the store platform for the period.
- Conversion value of the purchase action in Google Ads, for the same period (with the "All conv. value" column next to it).
- Average value per conversion in Google Ads compared to the store's average order value.
Keep in mind that Google Ads only records purchases attributed to ad clicks and views, so the total does not need to match store revenue. What gives the problem away is the proportion: an average Google Ads conversion value one hundred times higher than the average order (cents), an average value of zero or very low (empty field), an average value that shifts to a new level after a theme or app change (wrong variable), or "All conv. value" far above "Conv. value" (secondary or duplicated actions).
After the fix: history and bidding
Fixing the tag solves future conversions, not past ones. For history, Google Ads has conversion adjustments. The "Restate" option changes the value of a conversion already recorded without changing the count, and it affects the value columns and ROAS strategies. The "Retract" option removes the conversion. Both require online conversions to have been sent with a transaction ID, because that is how Google identifies which conversion to adjust. One more reason for the ID to be in the tag.
For bidding, the Target ROAS help recommends: if you changed how the Google Ads conversion value is recorded, wait 1 to 2 conversion cycles for the campaign to accumulate the new values before you start using Target ROAS.
Where server-side comes in
Five of the seven causes share the same root: the Google Ads conversion value is built in the browser, from whatever the page can read.
With server-side tracking, the purchase is sent from the server, with the data of the order recorded on the platform. Google documents how to set up Google Ads conversion tracking in server-side Tag Manager, with the Conversion Linker tag and the Google Ads Conversion Tracking tag in the server container, including how to set the conversion value through variables. The paid order has one value, one currency and one number. Those three pieces of data leave the same record for Google Ads, GA4 and Meta, and the order number becomes the transaction ID in all of them.
How Wascer fixes the Google Ads conversion value
Wascer launches and monitors a server-side Google Tag Manager container with no DevOps, no Docker and no command line. In the container, Wascer provides dedicated Google Ads, GA4 and Meta tags to send the purchase the way each platform requires, using the order number for deduplication. When the store sends its orders by webhook, the Wascer Data Client receives and processes that data inside sGTM, and the Google Ads conversion value starts to come from the order, not from the page text.
Learn what Wascer is and how it works or visit wascer.com.
Frequently asked questions
Should the Google Ads conversion value include shipping and tax?
It depends on the rule you choose, as long as it is always the same. GA4 recommends leaving shipping and tax out of the purchase value.
Why does the value show up as zero in Google Ads?
Most of the time, the variable in the "Conversion Value" field is empty or undefined when the tag fires, and Tag Manager sends "0".
“One” or “Every” counting for purchases?
"Every", with a transaction ID. "One" counts one conversion per click and is meant for leads.
Can I fix the value of conversions already recorded?
Yes, with "Restate" conversion adjustments, as long as the conversions were sent with a transaction ID.
Does server-side tracking fix a wrong value on its own?
It fixes where the number comes from. The conversion action settings (different values per conversion, counting and primary actions) still need to be right.
Conclusion
Google Ads does not know how much your store sold. It knows what the tag said. When the Google Ads conversion value arrives as text, in cents, without a currency, at zero or duplicated, the bid strategy optimizes with precision for a result that does not exist. The fix is simple to describe: a numeric value with a decimal point, BRL as the currency, a unique transaction ID, one primary action per purchase and, ideally, all of it coming from the order recorded on the server.
Before the next budget review, check that number. Enter your site URL and see if Google Ads is receiving the right value.

By Wascer
Wascer launches and monitors your server-side Google Tag Manager container in one click: no DevOps, no Docker and no command line. Technical content on tracking, Meta, GA4 and Google Ads for teams that decide with data. wascer.com
Sources
- Google Ads, tracking transaction-specific conversion values: https://support.google.com/google-ads/answer/6095947
- Google Ads, about conversion values: https://support.google.com/google-ads/answer/3419241
- Google Ads, setting additional settings (currency and ISO 4217): https://support.google.com/google-ads/answer/13064032
- Google Ads, using a transaction ID to minimize duplicate conversions: https://support.google.com/google-ads/answer/6386790
- Google Ads, about conversion counting options: https://support.google.com/google-ads/answer/3438531
- Google Ads, primary and secondary conversion actions: https://support.google.com/google-ads/answer/11461796
- Google Ads, conversions from multiple sources (deduplication within an action): https://support.google.com/google-ads/answer/16542291
- Google Ads, data discrepancies: https://support.google.com/google-ads/answer/7457111
- Google Ads, about Target ROAS bidding: https://support.google.com/google-ads/answer/6268637
- Google Ads, about conversion value rules: https://support.google.com/google-ads/answer/10518330
- Google Ads, about conversion adjustments: https://support.google.com/google-ads/answer/7686447
- Tag Manager, Google Ads conversions: https://support.google.com/tagmanager/answer/6105160
- Google Analytics, events reference (
purchase): https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtag#purchase - Google Analytics, ecommerce in Tag Manager (clearing the
ecommerceobject): https://developers.google.com/analytics/devguides/collection/ga4/ecommerce?client_type=gtm - Stripe, amounts in the smallest currency unit: https://docs.stripe.com/currencies
- Google, Google Ads conversion tracking in server-side GTM: https://developers.google.com/tag-platform/tag-manager/server-side/ads-setup
Wascer team · Published on Oct 26, 2026 · updated on Nov 6, 2026