Global Coverage Lookup

ipbase resolves IP addresses across a broad set of countries and networks, including many regions smaller geolocation providers cover less completely. A Beam agent triggers a lookup when a new customer, order, or session record needs a location, reads the returned country, region, and city, and applies your approved rule for what to do with a result, such as tagging the record or selecting a regional workflow. It writes the resolved location back to the record. Addresses that return only partial data or fall in a region your team hasn't set a rule for are routed to a person to fill in the gap.

Network and Connection Type Data

ipbase reports the network type behind an IP address, such as whether it belongs to a mobile carrier, a business connection, or a hosting provider. A Beam agent reads this field alongside the customer or order record it relates to, applies your approved rule for how each connection type should be treated, for instance flagging hosting provider traffic on high value orders, and updates the record accordingly. It notifies the relevant queue when the rule is triggered. Connection types the rule doesn't cover, or results that look inconsistent with other order details, are left for a person to review.

Bulk Record Enrichment

Because ipbase is built to handle geolocation lookups at volume, a Beam agent can work through a batch of existing customer or lead records that are missing location data, requesting a lookup for each one in turn. It reads the returned fields, applies your approved rule for which ones qualify as complete, and writes the country, region, and city back to each record. It notifies the data owner once a batch finishes. Records where the lookup returns no result, or where the address appears invalid, are set aside for a person to check rather than left silently blank.