Integrations and geo databases
The two things this install can reach outside itself — a DNS account that creates your tracking domain record, and the geo databases that answer where a visitor is.
#Connected accounts
Third-party accounts this install can act through. Today that is DNS.
It exists for a specific reason: adding a tracking domain is one DNS record, and it is the step people reliably get wrong — because it happens in somebody else's control panel, and it fails quietly when done wrong. Connecting the account that holds your DNS lets UTMCAP create the record itself, which removes the typo and the grey-cloud switch in one move.
Each row says whether it is connected, what it can reach, and when that was last true. The last of those is the useful one: a token revoked three weeks ago looks exactly like a working connection until something needs it.
#Geo databases
Three views of one subject, and the split is worth understanding because people usually want the second or third and go looking in the first.
Databases — which are installed, and how current.
Fields — which database answers each field. Country, region, city, ISP, ASN and connection type do not all come from the same place, and when a country looks wrong this says what to update.
Signals — how the bot detector reads what they say, and what each signal has caught. This is the one that answers "why was this click called a bot", in aggregate rather than one row at a time.
#When a country looks wrong
Geo lookup is an inference from an IP address, not a fact. It is right the large majority of the time and it is never right always.
Three ordinary causes, before assuming a bug: a mobile network egressing from a different country than the handset is in; a corporate VPN; and a stale database, which is what the Databases view is for.
A visitor whose IP cannot be placed gets an empty country, not a wrong one.
That is why {country} can arrive blank in a token and
why a routing rule on country in [...] will not
match them — worth a default path that catches them rather than a flow that
assumes everyone has a country.
#Why the connection type matters
Residential, mobile, corporate, datacentre. It is the strongest single bot signal there is: real buyers browse from residential and mobile networks, and traffic from a hosting provider is almost never a customer.
It is also usable in a routing rule, which is a cheaper thing to do than it sounds — sending datacentre traffic to a harmless page keeps your click-outs clean on the network's side.