GTM-Ads Currency Code Consistency
Why It Matters
Google Ads reports every conversion value in the account currency. When a tag sends a valid ISO 4217 code (USD, EUR, GBP), Google Ads uses it and converts the value into the account currency at the average daily foreign exchange rate. The currency on the conversion action's default value is only a fallback: Google uses it when the tag sends no currency code or an invalid one. A tag that sends EUR to an action set up in USD is therefore recorded correctly, as the USD equivalent of the euro amount.
The conversion is only as good as the code it is given. Google takes the tag's code at face value. If a tag is hardcoded to USD and the order was charged in EUR, Google records €100 as $100, and reported revenue drifts from the commerce backend by the exchange rate. Value-based bidding then optimises against the distorted values.
A hardcoded currency is the usual way this happens: it was right when the tag was built and was not updated when the business started charging in other currencies. AdLint compares the hardcoded codes in the GTM container with the currencies in the Google Ads export, and a difference tells you where to look. Neither export records the currency of individual orders, so AdLint cannot tell whether a hardcoded code is wrong.
How To Fix It
For each currency in the finding, find the GTM conversion tags that hardcode it. AdLint lists the GTM and Google Ads currencies side by side.
Check which currencies the site actually charges in. If it charges in one currency, the hardcoded code should be that currency.
If it charges in more than one, replace the hardcoded code with a Data Layer Variable that reads the order currency, typically
{{DLV - ecommerce.currency}}. Read it from the order, not from the visitor's browser locale.Send a valid ISO 4217 three-letter code. A missing or invalid code makes Google fall back to the currency on the action's default value.
Place a test order in a non-default currency. Confirm in Tag Assistant that the tag sends the order's currency, then that Google Ads reports the order total converted into the account currency at that day's rate.
Example
Account currency: USD
GTM tag currency: 'EUR' (hardcoded), site charges in EUR only
Google Ads records: the USD equivalent at that day's rate (correct)
Same tag after the site adds USD pricing
A $129.99 order is sent as 129.99 EUR
Google Ads records: the USD equivalent of €129.99 (wrong by the exchange rate)This account has GTM conversion tags that hardcode a currency code different from the currency in the Google Ads export. Per Google Ads Help ("Set up additional settings", conversion value currency), a valid ISO 4217 currency code in the tag is used and converted into the account currency at the average daily foreign exchange rate, and the currency on the conversion action's default value applies only when the tag sends no code or an invalid one. The difference is therefore supported on its own and reported here for information. The risk is a hardcoded code that does not match the amount actually charged, which neither export shows: Google then converts the amount from the wrong currency, so reported revenue and value-based bidding drift from the commerce backend. Fix: confirm each hardcoded code matches the currency charged, read the currency from the order in the dataLayer if the site charges in more than one, and verify a test conversion in a non-default currency. Source: support.google.com/google-ads/answer/13064032.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.