CF Geo Controller - Article
Summary
Configure CF Geo Controller to detect user location and automatically display storefront prices in local currency for anonymous users based on geolocation.
In this article you will learn:
- How geo-based currency detection works in Eurekos
- How CF Geo Controller integrates with a WordPress site
- How location data influences storefront pricing
- How to configure and activate the integration
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 dynamically adjust pricing to reflect the user’s local currency—improving clarity, trust, and conversion.
From a business perspective it directly supports:
- Conversion optimization through localized pricing
- 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.
| System | Responsibility |
|---|---|
| WordPress (Geo Controller) | Detects user location based on IP and manages user consent |
| Eurekos | Receives 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.
| Field | Description |
|---|---|
| API Version | Select v1 (legacy REST API) or v2 (modern WordPress setup) |
| Endpoint | WordPress 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
Relationship to the User Journey
This integration operates at the very beginning of the user journey, before any interaction or authentication takes place.
| Stage | Behavior |
|---|---|
| Anonymous visit | Currency is auto-detected |
| Signup | No direct impact |
| Login | Standard behavior applies |
| Enrollment | Uses defined pricing from configurations |
Governance and Best Practices
- Ensure alignment with pricing strategy → Currency display should match how pricing is structured in activities and tax configuration
- Always test with different locations → Use VPN tools to verify:
- Currency changes correctly
- Consent flow behaves as expected
- Validate configuration → Most issues originate from:
- Incorrect endpoint
- API mismatch (v1 vs v2)
- Plugin misconfiguration
- Understand consent requirements → Users must approve location tracking—otherwise, default behavior applies
- Use in combination with commerce setup → This feature only works when:
- Pricing is enabled
- Commerce configuration is correctly set