Multiple Currency Codes
Why It Matters
Google Ads reports every conversion value in the account currency. When a conversion arrives with a different ISO 4217 currency code, Google converts it at the average daily foreign exchange rate before it reaches reports and bidding. On a USD account, a €100 order sent with currency "EUR" is recorded as the dollar equivalent on that day, not as 100. A multi-currency setup is supported, and on its own it is not a defect.
The conversion is only as good as the currency code it is given. Google takes the code at face value and cannot tell that an amount labelled USD was charged in EUR. Three setups produce a code that does not match the money. The first is a GTM conversion tag with the currency hardcoded, often to USD, on a site that later started charging in other currencies. The second is a tag that sends no currency code, or one that is not a valid three-letter ISO 4217 code: Google then ignores the tag's currency and uses the currency set on the conversion action's default value. The third is an offline conversion import where the currency column is filled differently across uploads.
In each case Google converts the amount from the wrong currency. Revenue in Google Ads drifts from the commerce backend by roughly the exchange rate, and value-based bidding optimises against the distorted values.
AdLint reports mixed currency codes as information because they show where to look, not because they are wrong. The problem that matters, a code that does not match the money actually charged, cannot be detected from the export: it lists each action's currency setting, not the currency of individual orders. Only a test order shows it.
How To Fix It
For each currency in the finding, find where the conversion value comes from: a GTM tag, a gtag snippet, or an import.
Check that the currency sent with the value is the currency the customer was charged in. In GTM, the Google Ads Conversion Tracking tag's Currency Code field should read the order currency from the dataLayer, typically
{{DLV - ecommerce.currency}}. Hardcode it only if the site charges in a single currency.Send a valid ISO 4217 three-letter code (USD, EUR, GBP). A missing or invalid code makes Google fall back to the currency on the action's default value.
For offline conversion imports, fill the currency column on every row of every upload.
Place a test order in a non-default currency. Confirm that Google Ads reports it as the order total converted into the account currency at that day's rate.
Example
Account currency: USD
Order: €100.00, tag sends currency "EUR"
Google Ads records: the USD equivalent at that day's rate (correct)
Same order, tag hardcoded to currency "USD"
Google Ads records: $100.00 (wrong by the exchange rate)This account has Google Ads conversion actions that use more than one currency code. Per Google Ads Help ("Set up additional settings", conversion value currency), Google Ads converts conversion values reported in a currency other than the account currency at the average daily foreign exchange rate, and uses the currency on the conversion action's default value when a tag sends no currency code or an invalid one. Mixed currencies are therefore supported and reported here for information. The export does not show whether each code matches the amount charged. The risk is a currency code that does not match the amount actually charged, for example a tag hardcoded to USD on a site that charges in EUR: Google converts that amount from the wrong currency, so reported revenue and value-based bidding drift from the commerce backend. Fix: send the order's actual ISO 4217 currency code with every conversion value, 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.