Data CloudAdvancedcalculated-insightsretailmulti-currencyglobal
Normalize multi-currency retail metrics in cross-border calculated insights
Real World Scenario
Global retail segments on total spend rank APAC customers incorrectly when mixing JPY, EUR, and USD amounts without normalization.
Expected Answer
• Convert transaction amounts to corporate reporting currency at daily exchange rate table ingested to Data Cloud
• Store both local currency and normalized amount for regional and global segment use cases
• Handle refunds in original transaction currency to avoid skewed net spend insights
• Document exchange rate source and refresh cadence in insight metadata
• Build regional segments on local currency; global VIP on normalized fields only
• Validate normalization against finance ERP totals monthly
• Alert when exchange rate feed stale beyond finance SLA
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Convert transaction amounts to corporate reporting currency at daily exchange rate table ingested to Data Cloud Also consider: Store both local currency and normalized amount for regional and global segment use cases In practice: Handle refunds in original transaction currency to avoid skewed net spend insights Optimize for scale and operational observability.
Architect Perspective
Cross-border retail insights fail silently on currency—normalize explicitly with finance-approved rates, not implicit locale assumptions.