One feature request I would really love to see in FluentCRM v3 is native geolocation enrichment from lead IPs.
Right now, when we capture leads through Fluent Forms, the IP address can already be collected as part of the submission data (which is something Fluent Forms has supported for a long time).
In many legitimate operational and compliance-related scenarios where there is a valid legal basis, that IP can be used to determine approximate country or city information for the lead.
What always surprised me is that FluentCRM does not currently process or enrich that data automatically.
In our case, for workflows where it is legally justified and operationally necessary, we built our own automation layer:
- capture IP from Fluent Forms,
- verify it through a trusted service,
- update the contact profile inside FluentCRM automatically.
So technically, yes, this can already be solved with custom workflows. And ours work reliably.
But honestly, it still feels like a patch for something that is extremely basic inside a modern CRM.
Having approximate location data is sometimes operationally necessary for:
- determining whether a service can legally be provided,
- shipping restrictions,
- VAT/tax handling,
- language segmentation,
- timezone-based automations,
- fraud prevention,
- compliance-related workflows.
Most CRMs already handle this natively.
So my question is:
is native IP-based country/city enrichment part of the roadmap for FluentCRM v3 or future releases?
Even better:
having trusted geolocation providers integrated directly into FluentCRM would make this much more powerful and reliable.
Because right now, needing external automations for something so foundational feels a bit strange inside an otherwise very complete ecosystem.
And of course, the more services, jurisdictions, automations and edge cases you handle, the more operational obligations you have (and the more room there is for costly mistakes if these basics are not handled properly inside the CRM itself).
Really good point, especially regarding timezone-based automations.
I actually asked support before about having a “wait until local time” condition inside automations (for example, wait until it is 10:00 AM in the contact’s local timezone before sending).
They told me,
“We have the database field for timezone, but we don't have interface to do so. In the future, we will implement that.”
One thing that immediately came to my mind regarding IP-based geolocation:
I personally would not rely only on the IP captured during the original opt-in form submission.
People travel, use VPNs, and move countries, and timezone relevance changes over time.
What I know from ActiveCampaign, for example, is that location/timezone data gets refreshed repeatedly through email opens and tracking activity, which makes timezone-based automations much more reliable long-term.
So if FluentCRM ever adds native geolocation enrichment, it would probably make sense to treat it as dynamic data instead of a one-time form capture value.
Otherwise, timezone-based sends, segmentation, or compliance-related workflows could slowly become inaccurate over time, especially for businesses with international audiences.
Sebastian Really good point Sebastian!
In our case, we usually update this type of data when there is a clear operational event, for example a transaction, a checkout, or an acceptance of terms and conditions.
Refreshing location/timezone from email activity can definitely be useful. I also like how ActiveCampaign handles it technically.
My only concern, especially in Europe, is the GDPR/ePrivacy side of doing this through email opens. Tracking pixels are not always neutral from a legal perspective, and many users may not have given valid consent for that level of monitoring.
So I agree with the dynamic-data approach, but I would probably design it with source, freshness and legal basis attached to the field, not just as an automatic update from every email open. Also, I am not sure how reliable it could be vs link clicks. But would be nice to explore all this idea in general!
Interesting, geolocation and sending email automation based on users local timezone would be really useful. not just for FluentCRM.