How to Test JivoChat Geo Triggers and Regions Before Your Visitors See Them

5 minutes
Some links may be affiliate links, but they do not impact our reviews or recommendations.

JivoChat can greet a visitor from Lisbon in Portuguese, offer free shipping to London only to people in London, and send a chat from Texas to the Texas team. All of this depends on one thing the widget reads before anything else: the visitor's IP address. That also makes it hard to check. From your office you only ever see the version for your own country, so a typo in the Spanish invitation or a region that routes chats to the wrong department can stay live for weeks.

The fix is to look at your site the way a visitor from each market does. Below is a test routine for country-based triggers and the Regions feature, with the settings that most often trip people up. If you are still setting up invitations, start with our guide to live chat triggers and how to use proactive invites.

What depends on the visitor's location

Several JivoChat settings depend on where the visitor is:

Trigger conditions. In Manage → Channels → Settings → Triggers, a proactive invitation can be limited by Visitor's Country or by city (the condition appears as Visitor's Location or Visitor's City in different help articles). JivoChat's own help notes that geolocation is determined by IP and may not be precise.

Regions. On the PRO plan, Regions sends visitors to the agents of a specific area based on their IP. Each region gets its own channel with separate design, labels, triggers, agents and statistics, and everyone outside your regions lands in the Default region.

Chat language. Instead of installing a separate widget code per language, you can let Regions (also a PRO feature) switch the chat window language by visitor location. The trigger texts still have to be translated one by one, which is where untranslated invitations usually slip through. Pair this with solid proactive chat rules so each market gets a message that matches local language and intent.

Step 1. Write down what each market should see

Before opening a browser, make a short table: country, chat window language, invitation text, which agents should receive the chat, and what the offline form says. Testing against a written expectation is faster than deciding on the spot whether a greeting "looks right", and it gives whoever fixes the settings a clear list.

Step 2. Start every test from a clean browser profile

The widget recognizes returning visitors. Conditions such as "only once per day for one visitor", "number of visits" and "time since JivoChat window was closed" will keep a trigger you already saw from showing again, and the test then looks broken when it isn't. Use a fresh browser profile or a private window for each country and each run.

Step 3. Connect through a proxy in the target country

A proxy server in the country you're testing gives your browser an IP address from that country, so JivoChat and your site treat you as a local visitor. Firefox has its own proxy settings under Settings → General → Network Settings, which keeps the change inside one browser; in Chrome, a separate profile with a proxy extension does the same job.

For a check like this you need a small number of static IPs in specific countries rather than a large rotating pool. FineProxy, for example, sells static IPs by country, with dedicated addresses from $2 per IP. Access is tied to your own IP address, so after you add it in the dashboard the browser connects without a password prompt, and a login and password can be added if you test from several places. Any static plan can be bought for 48 hours, which is usually enough for a pre-launch check. Targeting there is by country, which covers country triggers and country-based regions; city conditions need an IP in that exact city.

Step 4. Confirm where the IP appears to be

Open an IP lookup page through the proxy and check the country it reports. Geolocation databases don't always agree, and JivoChat's may differ from the one you checked. If a trigger doesn't fire for a country that looks right in the lookup, try a second IP from the same country before changing the trigger.

Step 5. Match the time zone for time-based triggers

JivoChat's help warns that the time-of-day condition uses the time on the customer's side, not the time set in your admin panel. A proxy changes your IP but not your computer's clock, so a "show after 6 pm" trigger for Australia will follow your local time. In Chrome DevTools, the Sensors panel lets you override the time zone for the current tab; set it to the market you're testing before reloading the page.

Step 6. Walk the visitor's path

Triggers rarely fire on page load. Repeat the path a real visitor takes: time on site, time on page, the number of pages visited, scroll depth, and the URL or title conditions you set for specific product pages. Check that the invitation appears in the right language, the text matches your table, and the widget design matches the region. For a broader refresher on how live chat should behave for visitors, keep that checklist next to your region table.

Step 7. Start a test chat and check routing

Send a message from each country and confirm it reaches the agents assigned to that region, not the Default region. Mark these conversations as tests for your team, since each region keeps its own statistics and test chats can end up in them. Then switch agents offline and repeat: the offline form text and language also need checking per region. When you compare platforms later, our roundup of the best live chat apps covers routing and regional setups in more detail.

A short checklist before launch

  • Each region's chat window language and every trigger text are translated.
  • Country conditions match the countries listed in your regions.
  • Time-based triggers fire at the right local hour.
  • Test chats from each market reach the right agents.
  • The offline form reads correctly in every language.
  • Test conversations are labelled so they don't skew reports.

Running this routine once before launch and again after any change to regions or triggers takes about an hour for a handful of markets, and it shows you the chat the way customers abroad see it.

Join our blog and learn how successful
entrepreneurs are growing online sales.
Become one of them today!
Subscribe