Key takeaways
- Preserve the original amount and ISO currency alongside every converted reporting value.
- Document the exchange-rate source, date convention, refresh cadence, and treatment of refunds.
- Keep pipeline stage definitions and probability logic consistent before comparing markets.
- Show both local and normalized views so commercial performance and currency movement do not get confused.
01
Do not let conversion erase the original event
A lead worth 20,000 in one currency is not comparable to 20,000 in another. Store original amount, original currency, event time, converted amount, reporting currency, rate, rate date, and rate source. The converted field is a view of the event, not a replacement for it.
Google Analytics expects event-scoped currency in the three-letter ISO 4217 format. That standardization solves identification, not policy. Finance and revenue operations still need to decide whether a booking uses the close-date rate, invoice-date rate, monthly average, or another approved convention.
Swipe to compare every column
| Field | Example purpose | Failure prevented |
|---|---|---|
| Original amount and currency | Preserve the commercial event | Irreversible normalization |
| Rate and rate date | Make conversion reproducible | Unexplained dashboard drift |
| Reporting amount and currency | Support portfolio comparison | Mixed-unit totals |
| Value version | Track logic changes | Rewriting prior pipeline silently |
02
Choose the clock attached to the value
Marketing cost may occur on click date, pipeline on qualification date, a booking on signature date, and cash on payment date. One exchange-rate convention cannot be assumed to suit every metric. Name the economic event and the rate date together.
Store timestamps with an explicit UTC relationship and retain the market time zone separately when local-day reporting matters. Month-end discrepancies often begin as innocent differences in currency and clock conventions, then become attribution arguments.
03
Normalize definitions before ranking countries
A qualified opportunity in one team may require budget and timing; another may advance any positive reply. Currency-normalized pipeline still misleads when stage definitions differ. Establish stage entry criteria, probability ownership, expiry rules, and reversal behavior across markets.
Show local amount, normalized amount, volume, win rate, cycle length, and evidence maturity. A large converted pipeline with long aging and weak qualification should not outrank a smaller, faster, better-evidenced market by default.
04
Separate commercial change from currency movement
Provide a constant-currency view when leadership needs to understand operating performance independent of exchange-rate movement. Keep the actual reported-currency view beside it. Label the base period and method so “growth” does not quietly change definitions between meetings.
Reconcile analytics events, ad costs, CRM values, invoices, credits, and finance totals through fixed cohorts. Google Analytics now requires a currency field for campaign cost imports, which reinforces the operational point: cost and revenue need explicit units before they can share a ratio.
Primary sources and further reading
Use the source material to validate details against your own context and current platform configuration.
- Google Analytics: Currency dimension
- Google Analytics: About Data Import
- Unicode CLDR: Number and currency patterns
This field note follows the XenGrowth editorial policy: primary sources where available, visible limitations, material review dates, and no invented first-hand experience.
Stay with the problem
