Real Time Location Lookup

IP2Location.io returns a visitor's country, region, and city the moment a page loads or a form is submitted. A Beam agent triggers this lookup on new sessions or signups, reads the returned location fields, and applies your approved rule for what happens next, such as showing a regional price or redirecting to a local page. It updates the visitor or account record with the resolved location so later steps in the workflow can use it. When the lookup returns a low confidence result or conflicts with a billing address already on file, the agent leaves the record for a person to confirm.

Regional Content Routing

Many sites use IP2Location.io's location data to decide which regional version of a page, price, or offer a visitor sees. A Beam agent reads the resolved country or region for a session, applies your approved routing rule, and updates the visitor's session or account record so the correct regional experience loads. It notifies the marketing or ops queue when a region has no matching rule yet. Visitors whose IP resolves to a country your team hasn't set a rule for, or where the result looks inconsistent with other account data, are routed to a person to decide how to handle it.

Signup Location Verification

When someone creates an account, IP2Location.io can confirm which country or city the request actually came from. A Beam agent reads this at signup, compares it against the address or region the person entered, and applies your approved rule for what counts as a mismatch worth flagging, such as a billing country that differs from the resolved IP location. It updates the account record with both values and notifies the relevant team when a mismatch rule is triggered. Cases involving travel, a noted proxy elsewhere, or repeat customers are left for a person to review rather than blocked outright.