When a user reports a problem, the session replay shows what they experienced. IP addresses and geolocation add another piece of the story: where the session originated. That context gives your team a fuller picture when investigating the issue.
Set up session analytics and enable session recording for your application.
Make sure you can access your workspace's PLuG settings.
In DevRev, go to Settings > PLuG and Portal > Session Replays.
Select the General Settings tab
Turn on Geo Enrichment to enable IP address capture and geolocation.
Start a new session in your application to verify the configuration.
This feature requires no Web SDK code changes or SDK updates. DevRev derives the client IP address from the session request and uses it to determine approximate location.
Note: Changes apply to new sessions started after the setting changes. Existing sessions are not updated with IP addresses or location information retroactively.
When Geo Enrichment is enabled, DevRev captures the session's client IP address and uses it to derive approximate location information, such as country, region, and city.
Enabled: Captures the client IP address and adds location information when the location lookup succeeds.
Disabled: Does not collect additional IP address or geolocation information for new sessions through this feature.
Privacy note: IP addresses and derived location information can be personal data. Before enabling Geo Enrichment, ensure your privacy notice covers both and that collection is consistent with your organization's privacy requirements.
Go to Explore and search for Session Replays.
Select the platform and a date range that includes sessions started after you enabled Geo Enrichment.
Open a session and review the available IP and location information alongside the replay under the Details tab
Location information is available when the IP address can be resolved to a location. A missing location does not indicate that IP capture and geolocation are configured separately.
Geolocation is derived from an IP address. It represents an approximate network location, not the user's precise physical location or GPS coordinates.
Use location information as supporting context when investigating a session, rather than as proof of a user's physical location.
Return to Settings > PLuG and Portal > Session Replays
Open the relevant platform settings, and turn off Geo Enrichment
Turning off this toggle disables IP address capture and geolocation together for new sessions.
Q. IP address or location information is missing
Check that Geo Enrichment is enabled for all the relevants platform (Web / iOS / Android)
Check that the session started after you changed the setting. Earlier sessions are not updated retroactively.
Location information may be unavailable when the IP address cannot be resolved to a location.
If the information is still missing from a new session, contact DevRev support with the session link and confirm whether Geo Enrichment was enabled when the session started.
Q. The location does not match the user's expected location
IP-derived location is approximate and should not be treated as a precise device location. Review it alongside other session information when investigating the reported behavior.