Geo.IP Address Derived Field Description
FunnelConnect uses across its Data Pipeline services IP2Location DB23 to map IP addresses to structured metadata, providing insights into the geographical and network attributes of the client making the request. This information aids in analytics, compliance, and user experience optimisation. The Location data is only accurate to certain degree and can’t be used like GPS derived data.
Derived Fields
These fields are derived from the client’s IP address.
Field | Description | Example value |
---|---|---|
|
| |
| Region or state name. |
|
| City name. |
|
| Latitude of the city. Defaults to capital city latitude if city is unknown. |
|
| Longitude of the city. Defaults to capital city longitude if city is unknown. |
|
| Internet Service Provider or company name. |
|
| Domain name associated with the ISP or company. |
|
| Mobile Country Code. |
|
| Mobile Network Code. |
|
| Carrier brand name. |
|
| Usage type classification. Possible values include: |
|
| Custom field representing network latency in milliseconds. Not a standard IP2Location field. |
|
Information for Business & Legal Teams
Purpose: These fields help identify the geographical and network attributes of the client accessing your services, which is crucial for analytics, security, and compliance.
Data Privacy: All derived fields are obtained from the IP address, which is part of the network request and does not contain personally identifiable information.
Compliance: Understanding client locations can aid in ensuring compliance with various regional regulations and standards.
Consent: IP2Location Data is only derived, collected and inlined by FunnelConnect if the configured consent checks are passed.