Overview

Multi-currency Support lets you support advertisers that manage campaigns in different local currencies, while auctions continue to run in the platform’s base currency.

This feature is useful for multi-country retailers and marketplaces where advertisers price products, fund wallets, set budgets, and review performance in their own currency.

With Multi-currency Support, each ad account can operate in a currency that is different from the platform’s base currency.

📘

Note

Your platform can only have a single base currency and can support up to 25 different ad account currencies (1. USD 2. KRW 3. JPY 4. EUR 5. GBP 6. SEK 7. INR 8. THB 9. IDR 10. CNY 11. CAD 12. RUB 13. BRL 14. SGD 15. HKD 16. AUD 17. PLN 18. DKK 19. VND 20. MYR 21. PHP 22. TRY 23. VES 24. AED 25. CHF).

Advertisers use their ad account currency for:

• Campaign budgets
• Campaign bids
• Wallets Spending limits
• Spend caps
• Advertiser-facing reporting

The auction continues to run in the platform’s base currency so that all campaigns compete consistently in the same auction.

🚧

Be attentive

Moloco applies daily foreign exchange rates to convert advertiser-currency bids into the platform base currency for auction-time comparison. Exchange rates are sourced daily from OANDA and applied automatically.

Prerequisites

Before enabling Multi-currency Support, confirm the following with Moloco:

• Report API V3 is available for the platform
• The catalog feed includes valid currency values for items that need a currency different from the platform base currency
• The catalog feed has been processed after currency values were added
• The platform understands the daily FX conversion methodology and related FX risk
• API integrations have been reviewed for campaign, reporting, wallet, spending limit, and spend cap behavior
• The platform has identified the currencies that advertisers are expected to use

When to use Multi-currency Support

Multi-currency Support is intended for platforms that have advertisers operating in more than one currency.

Typical examples include:

• Multi-country retailers with sellers in different countries who price products in local currencies
• Global marketplaces where sellers from different countries participate in the same advertising marketplace
• Platforms where advertisers need to manage budgets, bids, wallets, and performance reporting in their local currency

Platforms where all advertisers use the same currency as the platform base currency generally should not enable Multi-currency Support.

Key currency concepts

How auctions work

Advertisers configure campaigns in their ad account currency.

At auction time, Moloco converts the bid from the ad account currency into the platform base currency using the daily exchange rate. The auction compares bids in the platform base currency, which allows campaigns from different currencies to compete consistently.

When an auction is won, Moloco records the winning price in both the platform base currency and the advertiser’s ad account currency.

This supports consistent auction operation while preserving advertiser-facing spend and reporting in the advertiser’s currency.

Campaign behavior

For ad accounts using a currency different from the base currency, campaign configuration is done in the ad account currency.

This includes budgets, bids, and recommended guidance values.

Campaign creation and update requests must use the ad account currency. If a request uses a mismatched currency, the API returns an error.

Reporting behavior

Multi-currency Support changes reporting behavior by allowing monetary metrics to be viewed in the platform base currency or the ad account currency, depending on the user and reporting surface.

📘

Note

Multi-currency Support requires Report API V3. Before enabling Multi-currency Support, you should work with Moloco to confirm that Report API V3 is available and that any expected reporting behavior changes have been reviewed.

API behavior

Decision API

The Decision API request format does not change.

The decision response includes pricing information that supports both platform base currency and ad account currency views.

The existing win price continues to represent the platform base currency. For ad accounts using a different currency, the response also includes the win price in the advertiser’s ad account currency.

Management API

Management API behavior changes for ad accounts, campaigns, reports, wallets, spending limits, and spend caps.

If you integrate with these APIs, review the expected behavior before activation.

Important changes include:

• Ad account responses include the ad account currency
• Campaign create and update requests must use the ad account currency
• Campaign read responses reflect the ad account currency
• Report requests can support platform-currency and ad-account-currency views, depending on user permissions and feature availability
• Wallet operations use the ad account currency
• Spending limit and spend cap operations use the ad account currency

Activation considerations

Multi-currency Support should be treated as a one-way enablement. Once an ad accounts been created with secondary currencies, disabling the feature may leave the platform in an undefined state and is not considered a standard operating path.

Before activation, you should review and acknowledge the following:

• Ad account currencies are immutable once assigned
• Rates are applied once daily Intraday FX movement is not reflected until the next daily rate is applied
• The platform absorbs any gains or losses from rate movements that occur between daily rate updates.

Next steps

• If you have any questions, check FAQ.