> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/pricing-experiences/pricing-experiences-overview/multi-currency-testing.md). # Multi-Currency Testing Run price tests in different currencies ### Introduction Intelligems price tests run in your store's default currency by default. However, Intelligems supports price testing in any Shopify-supported currency, so you can find the price that earns you the most profit in each market instead of taking whatever your exchange rate hands you. Each currency you want to test will require its own separate test configuration in the Intelligems app. {% hint style="info" %} **Multi-currency runs as a Test.** A Price Change run as a Personalization applies in your store's default currency only, so anything priced in another currency is set up as a Test. {% endhint %} {% hint style="info" %} Multi-currency testing is included with the **Smart Pricing Unlimited** module and on the **Unlimited** plan. It also has to be switched on for your account by Intelligems before the currency selector appears in the app. [Reach out to support](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) if you're not sure whether it's on yet. {% endhint %} ### Requirements * [ ] Make sure Multi-currency testing is enabled on your account. Reach out to support [here](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) if you are not sure if this feature has been enabled for you yet * [ ] Your store handles currency conversion through [Shopify Markets](https://www.shopify.com/markets), [Global-E](https://www.global-e.com/), Shopify localization, or the Coin Currency App. These are the localization sources we can read a shopper's currency from. [Reach out to support](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) if you use something else. * [ ] Your [price testing integration](/pricing-experiences/price-testing-integration-guides.md) is complete. Multi-currency works on both our Shopify Functions and duplicate products integrations. If the Modifications tab shows a **No price tags detected** badge, [talk to us](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) before you build anything, because prices won't swap on your storefront. * [ ] Every variant you plan to test has a **fixed price** set in the currency you're testing, rather than an automatic conversion from your default currency. Automatic conversions move with the exchange rate while the test is live, which shifts your prices underneath your own results. * [ ] You are ready to upload prices to your desired market when you [start](#step-4-start-the-test), [pause](#step-5-pause-or-end-the-test) or [end](#step-5-pause-or-end-the-test) your price test ### **Which currency setting am I looking at?** Two settings in a Pricing experience are called currency, and they do different jobs.
SettingWhat it does
Currency, on the Modifications tabSets the currency the test is priced in. The prices you type are real prices in that currency, and shoppers in that currency see them. This is multi-currency testing.
Currency, on the Targeting tabFilters which currencies a test applies to. On a Pricing experience it locks to your test's currency and can't be edited.
You can confirm which currency a test is priced in at any time from the pill under its name, which reads **Shown only to visitors in:** followed by the currency code. ### **Step 1: Set up your test** Creating a multi-currency test is generally similar to any other Price Test, with a few key changes to note. If you are not familiar with setting up a Price Test, please see our article [here](/pricing-experiences/pricing-experiences-overview/how-to-set-up-a-price-test.md). The main differences in setting up a Price Test that is not in your default currency are: 1. Once you've added your test product(s) in the Modifications tab, you will need to update the currency to match your desired test currency as shown in the screenshot below:
{% hint style="warning" %} This option will not be available until an Intelligems team member has enabled the multi-currency setting for you. {% endhint %} 2. You will need to update control prices to match your test currency prices. Prices aren't automatically converted, so verify each cell displays the correct amount. The price on the far left of each row is the product's price in your store's default currency, shown for reference, so don't read it as a conversion of what's in your test groups. {% hint style="warning" %} Quick filling test groups based on control prices is not available for multi-currency tests. While you'll see the Quick Fill option in the app, clicking on it opens the **Fill By Upload** tab rather than **Fill By Formula**. {% endhint %} 3. Currency targeting is set to your selected test currency by default, and will not be editable directly in the targeting section. ### **Step 2: QA your test** This will be generally the same as [QAing any other Price Test](/pricing-experiences/price-test-qa-checklist.md), with two additions. * **Switch your own store currency to the test's currency first.** Your selected currency has to match the test's currency or you won't see the test at all. * **Read the price CSV before you upload it.** Open the file, check the prices against the test group you downloaded, and check the compare-at prices match what you intended. You’re about to change catalog prices in a live market with it. ### **Step 3: Get your price file ready** You don’t have to wait for the start prompt to get your prices. Open the `...` menu on the experience, choose **Get price CSV**, and pick the test group whose prices you want. You can prepare and check the upload before anything goes live. Doing this in advance is worth the few minutes. Once you press Start, your test prices are being served, and the market prices in Shopify need to be right by then. ### **Step 4: Start the test** On our Shopify Functions integration, your market prices need to be set to your highest-priced test group in order for the test to run properly. Every shopper sees the same product, and Intelligems discounts the lower-priced groups down from that price. The rest of the start sequence is the same as any Price Change, covered in [Starting a Price Change Experience](/pricing-experiences/pricing-experiences-overview/starting-a-price-test.md). When you hit the play button for your test, Intelligems will prompt you to download a price CSV. Choose your highest-priced group.
Once you have this CSV, follow the upload steps for your setup [below](#uploading-your-prices). {% hint style="info" %} You cannot have a product in more than one experiment *if* the experiments are set to the same currency. If so, the test will not start. {% endhint %} {% hint style="info" %} On our duplicate products integration, the prices work differently. Each test group gets its own copy of the product, so your original products stay at your control prices and each duplicate carries its own group’s price. The Shopify Markets file format below doesn’t include duplicate products yet, so talk to us before you start and we’ll help you get the right prices into your market. {% endhint %} ### **Step 5: Pause or end the test** When pausing or ending a test, you'll be prompted to download a CSV with the prices that you want to roll out either while the test is paused, or permanently. Choose the test group whose prices you’re keeping, then upload it the same way you did at the start, using the steps below.
### **Uploading your prices** #### **If you are using Global-e** Reach out to your account manager at Global-e with this CSV. They will help you upload this information. They will also need to revert this at the end of the test so the prices can sync with the current exchange rate. #### **If you are using Shopify Markets** 1. Download your price CSV in the **Shopify Markets** format, and pick the Markets catalog you’re updating. The list only shows catalogs that aren’t archived and have prices set in your test’s currency. 2. From your Shopify admin, go to **Markets** > **Catalogs** and import the file into that catalog. Shopify covers the import in Export and import catalogs using CSV files. *\[link to the Shopify URL above]* 3. Check Shopify’s preview before you confirm. Your test prices go in the **Fixed Price** and **Compare At** columns, in your catalog’s currency. {% hint style="warning" %} The two files don't share a column layout, so this is a manual merge rather than a straight upload. Build it If the catalog you need isn’t in the list, check in Shopify that it isn’t archived and has fixed prices in your test’s currency. Talk to us if it still doesn’t appear. {% endhint %} ### **Testing more than one currency** Each currency runs as its own test with its own analytics, and you can have several running at the same time as long as they're in different currencies. Your price testing integration only has to be done once for the store, no matter how many currencies you go on to test. A few things worth deciding before you build them: * **Pick your markets by volume, not by coverage.** Testing every market you sell into isn't practical for most catalogs. Sort your last 90 days by country in Sitewide Analytics, test your largest few, and take the direction of those results into the rest. * **Decide up front whether prices have to match across markets.** Separate tests can produce different winners, so you can either roll out the most profitable price in each market or hold one price everywhere for consistency. Your results will tell you what's most profitable per market; whether that's the right call for your brand is a judgement about your customers, particularly if they switch markets between visits. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.intelligems.io/pricing-experiences/pricing-experiences-overview/multi-currency-testing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.