Choose the level of control that fits your use case.
Proxy geo targeting on AnonEdge comes in two tiers. One is included in your rate. The other narrows the exit further and bills at twice it.
Default targeting picks a country and rules networks out. Target Filters pick a place inside a country, or a specific network to route through. The split matters because the second tier changes what you pay per gigabyte and what happens when no exit matches.
Included in base pricing.
Country selection and country exclusion are alternatives, not a pair. Set one or the other. ASN exclusion rules a network out of the pool without saying anything about where the exit sits.
Traffic routed through Target Filters is billed at 2× the standard rate. The multiplier applies to the traffic, not to the account, so a job that runs country-level and a job that runs city-level bill separately at their own rates.
Note the asymmetry with the tier above: ASN exclusion is default targeting and costs nothing extra, while ASN selection is a Target Filter and bills at the doubled rate. Ruling a network out is cheap. Insisting on one is not.
| Parameter | Granularity | Tier | Rate |
|---|---|---|---|
| Country select | Country | Default targeting | Base |
| Country exclude | Country | Default targeting | Base |
| ASN exclude | Network | Default targeting | Base |
| State | Subdivision | Target Filters | 2× |
| City | Municipality | Target Filters | 2× |
| ZIP | Postal code | Target Filters | 2× |
| ASN select | Network | Target Filters | 2× |
Narrower is not automatically better. Each step down the table shrinks the set of exits that can serve you, which is the point when a target checks location and the cost when it does not.
Set the options in your dashboard, then click Save Configuration. Nothing takes effect until you do. A change left unsaved is a change your next request will not see, which is the most common reason a configuration appears to have been ignored.
Targeting is configured once and read on every request. It is independent of the port you connect to, so a saved configuration applies the same way on rotating and sticky sessions.
If no IPs are available for a specific filter, you may receive 400 NO_RAY.
It means the filter matched nothing, not that the request was malformed. Widen it. Drop from ZIP to city, from city to state, or from a single ASN to the country. The narrower the combination, the more often this is what you get back.