Threat and Abuse Flagging

ipdata.co returns threat indicators for an IP address, such as whether it's associated with known proxies, tor exit nodes, or reported abuse. A Beam agent triggers a lookup when a signup, login, or order carries an IP needing a check, reads the threat fields, and applies your approved rule for how to treat each flag, for example holding an order for review or allowing a login with a notification. It updates the record with the threat result. Flags that fall outside the approved rule, or involve a customer with an established account history, are routed to a person rather than acted on automatically.

Company and Carrier Identification

ipdata.co identifies the company or mobile carrier associated with an IP address, which helps distinguish a corporate office, a home network, or a phone connection. A Beam agent reads this field for a record that needs context, such as a support ticket or a lead form submission, and applies your approved rule for what to do with each type, like tagging enterprise leads for a different queue. It writes the company or carrier name to the record and notifies the relevant team. Results that return no company match, or conflict with details the customer provided, are left for a person to confirm.

Location Based Record Tagging

ipdata.co resolves the country, region, and city behind an IP address, which a Beam agent uses to tag customer, lead, or order records for routing and reporting. On a trigger such as a new signup, the agent reads the resolved location, applies your approved tagging rule, and updates the record with the region so downstream workflows, like assigning a sales territory, can use it. It notifies the record owner when a new territory is created. Locations that don't map to an existing territory rule, or where the result conflicts with a stated address, are routed to a person to sort out.