Skip to main content

Show Location-Based Storefront Currencies with CF Geo Controller - Article

Configure anonymous currency detection with the supported Geo Controller API and understand price selection and fallback behavior.
Updated: 14 Nov 2026
4 min read

Summary

Presenting a familiar currency can make a commercial training offer easier to evaluate before a visitor signs in. CF Geo Controller supplies location information; Eurekos uses that result to choose among the prices configured for the offer.

This supports a localized storefront experience. It does not create a new currency price or perform automatic foreign-exchange conversion.

Use this article to:

  • Connect the supported geolocation service
  • Enable the corresponding Commerce display settings
  • Check anonymous price selection and fallback cases

Business Context

The CF Geo Controller integration enables Eurekos to adapt the commercial storefront experience based on a user’s geographic location. Rather than presenting all users with a single currency, the platform can select an available price in a relevant currency, helping the visitor understand the offer without manually comparing currencies.

From a business perspective it directly supports:

  • Clearer regional pricing to support the purchase decision
  • Market adaptation across regions
  • Improved user experience at the point of entry

Importantly, this functionality applies before login, shaping the initial storefront experience.

Feature Overview

CF Geo Controller (formerly CF Geo Plugin) is a WordPress-based geolocation service that integrates with Eurekos to enable location-aware storefront behavior.

Once configured, the integration allows Eurekos to:

  • Detect a user’s geographic location (via external service)
  • Request user consent for location tracking
  • Display prices in the user’s local currency

This functionality applies specifically to anonymous users browsing the storefront, ensuring that pricing is aligned with their location before any interaction takes place.

Data Exchange: Geo Controller & Eurekos

The CF Geo Controller integration is dependent on an external WordPress-based geolocation service and cannot function independently within Eurekos. Rather than performing geolocation internally, Eurekos relies entirely on a connected WordPress environment where the Geo Controller plugin is installed and configured.

This means that the integration is not self-contained—it is part of a broader ecosystem setup, where WordPress acts as the source of truth for user location data.

To successfully enable this integration, the following prerequisites must be met:

  • An active Geo Controller subscription
  • A WordPress-managed website with the Geo Controller plugin installed
  • Administrative access to configure and retrieve API credentials from that site

Without this setup, no geolocation data will be available to Eurekos, and the feature will not operate.

SystemResponsibility
WordPress (Geo Controller)Detects user location based on IP and manages user consent
EurekosReceives location data and applies it to storefront currency display

⚠️ Eurekos does not control how location is detected — it only consumes the result provided by the Geo Controller plugin

Configuration

The integration is configured in two steps:

Step 1: Configure CF Geo Controller Integration

Navigate to Settings → Third-party integrations → CF Geo Plugin.

Enter the required API configuration.

FieldDescription
API VersionUse API v2; v1 is deprecated
EndpointWordPress endpoint (e.g. /wp-admin/admin-ajax.php)

These values must be retrieved from your WordPress Geo Controller setup.

Step 2: Enable Currency Detection

Navigate to Settings → Commerce → Activity information (General tab).

Ensure the following settings are enabled:

  • Price is enabled
  • Auto detect currency for anonymous users based on location

Click Save to activate the feature 

Understand which price is selected

Configure the relevant currency prices on the offer before relying on location detection. Eurekos selects an existing price using this sequence:

Available offer pricesAnonymous Storefront result
A price matches the detected location currencyThat matching currency price is displayed
No matching price, but a default-currency price existsThe default-currency price is displayed
Neither matching nor default-currency price existsOne of the available configured prices is displayed
Automatic detection is disabledThe Storefront uses the default-currency display behavior

For example, a product-training offer may have EUR and GBP prices. A UK visitor can see its configured GBP price; that amount need not be a conversion of the EUR price. Decide the commercial prices deliberately.

Relationship to the User Journey

This integration operates at the very beginning of the user journey, before any interaction or authentication takes place.

StageBehavior
Anonymous visitCurrency is auto-detected
SignupNo direct impact
LoginStandard behavior applies
EnrollmentUses defined pricing from configurations

Governance and Best Practices

  1. Ensure alignment with pricing strategy → Currency display should match how pricing is structured in activities and tax configuration
  2. Always test with different locations → Use VPN tools to verify:
    1. Currency changes correctly
    2. Consent flow behaves as expected
  3. Validate configuration → Most issues originate from:
    1. Incorrect endpoint
    2. An unsupported API version; use v2
    3. Plugin misconfiguration
  4. Understand consent requirements → Users must approve location tracking—otherwise, default behavior applies
  5. Use in combination with commerce setup → This feature only works when:
    1. Pricing is enabled
    2. Commerce configuration is correctly set

Verify the anonymous shopping experience

CheckExpected result or evidence
Configured matching currencyA representative anonymous visit selects the intended configured price
No matching currencyThe configured fallback is used; no new exchange amount is calculated
Price display disabledThe storefront follows its Commerce visibility configuration
Location unavailableReview provider consent and fallback behavior without assuming a detected country

Troubleshooting

ProblemWhat to check
Currency does not changeAnonymous visit, API v2 endpoint, provider setup and both Commerce display settings
Unexpected amount is displayedWhich currency prices actually exist on the offer and which fallback applies
Location is not detectedExternal service availability and the consent flow
Signed-in behavior differsThis location-based display feature applies to anonymous visitors

Third Party Integrations

FAQ