Feature Requests

Got an idea for a new feature or integration? We’d love to hear it! You can find our roadmap here.

1 vote

Tagging a guest by country based on IP address?

Hi team, our business use case: we use WooCommerce, to sell wooSubscriptions to LearnDash Courses. We want and need: to setup “country based pricing” – by that I mean: set this price for a Brazillian product in Brazillian currency, and only allow someone viewing the shop (or in the checkout) to access or purchase this product IF their IP indicates they are “IN that country”. We also use FluentCRM, and FluentForms, and FluentSMTP in our stack along side wpFusion We are aware that: a) someone can IP spoof using VPN, that – we will just have to live with b) there are solutions that “change a USD price to Brazillian price equivalent” – but this is NOT what we want. We have a specific need to sell a class in Portuguese only, to Brazillians in Brazil at a fixed (greatly reduced) price in Brazillian. c) this is not (and there is no) fool proof way to determine if someone is in a particular country. We thought, perhaps – that wpF could: 1) identify the country by IP (if provided), 2) assign a tag to the “browsing client” through JS and page delivery (as they would be a guest and not logged in yet), 3) use that tag to limit or vet visibility of products, and possibly 4) vet checkout / restrict checkout, so that no one can checkout unless the IP meets the criteria for that country. 5) allow us to set a products price by country code. This may be too far out for wpF, perhaps there is a wooCommerce add-on that “does all of this” (love to hear about it). Just thought maybe, wpF could do this for us. Why? because wpF does such a fantastic job of visibility restrictions using tags. Thanks, Dan

Declined Category: Enhanced Ecommerce Dan Linstedt shared this idea Updated: August 25, 2025

2 thoughts on “Tagging a guest by country based on IP address?”

  1. It’s not reliable to detect IP addresses because, in addition to people using VPNs, if you’re behind Cloudflare or any other kind of caching service, or oftentimes your host, they’ll also have a proxy layer that masks the IP address.

    So by the time we detect it, we’re just seeing your host’s IP address.

    We’ve tried this as a custom implementation for some customers and I would say that it works maybe 60% of the time, which isn’t terrible. But it’s not something I would want to include as a feature because it can be quite complicated for us to try and untangle people’s hosting configurations when they notice the IP tracking isn’t accurate.

Leave a Comment

Your email address will not be published. Required fields are marked *