Compare Revenue Across Currencies
Use tenant reporting currency consistently when comparing Commerce and Acquisition revenue.
Orders may arrive in different transaction currencies. Hardal's reporting currency presents revenue in a common currency for a Commerce tenant's Commerce and Acquisition reports.
Check the three currency contexts
| Context | Meaning |
|---|---|
| Collected currency | The original currency sent with a purchase |
| Tenant reporting currency | The currency used to present supported revenue reports |
| External comparison currency | The currency used in your finance, media, or spreadsheet report |
Continue sending the original currency and value for each order. Changing the reporting setting is not a reason to relabel an order's original value.
Review the tenant setting
Open Organization → Tenants → Edit for a Commerce tenant and inspect Reporting currency. Owners and admins can change it; the choice applies to the tenant's revenue reports. Review the impact on other report readers before changing a shared setting.
Set the same period, source, and timezone in Commerce and Acquisition. Check the displayed currency and Acquisition's conversion configuration. Currency alignment alone does not make order counts and attributed conversions the same measurement.
Compare markets and brands
If separate tenants use different reporting currencies, normalize the amounts deliberately before adding them in an external report. Keep the original report currency in your export or reporting notes so another reader can reproduce the comparison.
Do not treat unavailable revenue as zero. A purchase missing valid currency data or an available conversion rate can be absent from revenue calculations even when activity was collected. Inspect the underlying event and report response before interpreting the result.
For implementation, read Track Server-Confirmed Purchases. For repeatable reporting, use the Analytics API.