Browse the help center

Clean up stale location targeting

Find the location rules that name a city or region the IP data provider has renamed or merged — rules that match no visitor — see what removing each one would change, and remove or replace them in one pass, or let Fix with AI match every place to its current name.

How-to network manager advertiser publisher Account → Advertisers / Publishers → action rail → Stale locations

The list of places behind location targeting comes from the IP data provider and is updated a few times a month. Now and then an update renames a city or folds it into a neighbour, and every rule saved under the old name silently stops matching anyone. Stale locations finds those rules across all the advertisers, campaigns, banners, sites, zones and placements you manage, says what removing each one would change, and removes or replaces them in one pass.

Example. A campaign targets United States, Kentucky, Lexington-Fayette. The provider renames the city to Lexington. The rule still reads “Lexington-Fayette”, nothing on the campaign looks wrong, but no visitor is ever reported from a place of that name — so the campaign, whose only location include this is, reaches nobody until the rule is replaced with Lexington.

Typical scenarios

  • One renamed city, one campaign. The Lexington-Fayette case above: 1 rule, kind Opens to all locations. Replace… it with Lexington and the campaign serves again, to the same place.
  • Suburbs merged into a city. A publisher’s 3 placements pre-target Enterprise and Spring Valley, which the provider now reports as Las Vegas. Each placement still includes Las Vegas itself, so all 6 rules are Safe to remove — they are already preselected; one click removes them.
  • The same district excluded on many banners. 5 banners exclude a district that was renamed. Each exclude is now Starts delivery: it blocks every visitor instead of one district. Replace… on one banner with Also replace it in 4 other rules ticked moves all five to the new name.
  • A long list after a provider switch. The administrator changed the network’s IP data provider and 42 campaign rules name Oslo County, which the new provider calls Oslo. Fix with AI proposes Norway, Oslo, Oslo for the lot with a high confidence, and Apply fixes all 42 in one go.

Step by step

  1. Open Account → Advertisers (or Publishers). When that side has stale rules whose removal would change delivery, a red Stale locations button — a crossed-out map pin with a count — sits on the action rail left of the tree. The tooltip reads Stale locations — action required. Click it.

    Advertisers tree with the red Stale locations button on the action rail

  2. Read the three cards at the top: how many rules are Safe to remove, Opens to all locations and Starts delivery. Click a card to show only that kind; click it again to show everything. The line under the header says how many places were checked. Each row names the entity (a link to its edit page), the place, include or exclude, and If removed with a one-line hint for that rule.

    Stale locations page: three summary cards and the grid with safe rows preselected

    If removedWhenWhat removing it does
    Safe to removeA stale include while the entity still targets a valid place of the same type, or a stale country excludeNothing. The ad server already ignores it.
    Opens to all locationsThe entity’s only includes of that type are staleToday the entity reaches no visitor. Once every such place is gone, the location limit is lifted and it serves everywhere.
    Starts deliveryA stale location excludeToday it keeps every visitor out. Once it is gone the entity starts serving to everyone else.
  3. For a rule that opens or starts delivery, click Replace… — the highlighted button on those rows. Pick the place it is called now (country, then optionally region and city, as on the targeting card). If the dialog shows a Suggested: line, Use fills the picker with it; check it. When other listed rules name the same stale place with the same include or exclude, Also replace it in N other rules with this place is offered, ticked; Show them lists those entities. Click Replace. The new place gets the same include or exclude on the same entity and the stale rule is removed, so the targeting stays as the advertiser meant it.

    Replace dialog with the Suggested line, Use, and Also replace it in N other rules ticked

  4. Or fix every place at once: click Fix with AI, the first button of the toolbar row above the list. Under Proposed changes each card reads old place → new place with how many rules name it, what removing them would do, a one-line reason and a confidence meter; cards the AI matched carry an AI tag. Only the sure name matches (High confidence) are ticked — tick the others you agree with, or use Select all / Clear. Places under Needs your decision get no proposal; Show rules lists their rules on the page so you can replace or remove them by hand. Click Apply N changes, read the result line, and click Done.

    Fix with AI panel: Proposed changes with an AI tag and confidence meter, Needs your decision, Apply

  5. Tick anything else you want gone — rules that are safe to remove are already selected — and click Remove selected (N). The confirmation counts how many of the selected rules are safe and how many change delivery, and names the change. Confirm with Delete.

  6. The list refreshes; the rail count and the targeting cards follow. Rules the server did not remove or replace are named in a message with the reason — for example, someone removed them meanwhile. On an entity’s edit page the targeting card no longer shows the place in red.

    Campaign targeting card with a stale place as a red chip and the Clean up stale places link

Every removal and replacement goes through the same path as an edit on the targeting card: it is written to the action log and reaches the ad servers like any other targeting change.

Caveats and exceptions

  • What is counted. Rules of paused entities and of entities whose targeting is switched off are checked and counted too, since they apply again once those run; rules of deleted entities are left out. The rail count is only the rules whose removal would change delivery; while a side has none — no stale rules, or only safe ones — the button is hidden.
  • Grid view and the targeting card. Grid view has no tree and no rail: the same alarm is a red Stale locations button with the count in the grid toolbar, on the right next to Enable rule view. A red place on a targeting card always links here: Clean up stale places across the account.
  • “Safe” is decided per entity and per targeting type. A stale city next to a valid city on the same campaign is safe; the same stale city on a banner whose only location include it is opens that banner to every location, even if its campaign still targets cities. Location and country rules are separate types, so a valid country include does not make a stale location include safe.
  • Country rules. A country exclude naming a code nobody has excludes nobody, so it is safe to remove; a stale location exclude keeps every visitor out and is Starts delivery. Country rules cannot be replaced from this page — remove them and add the country again on the targeting card.
  • Filters and selection. Remove selected acts only on the selected rules the list shows; a rule ticked under another filter (a card, If removed, Entity type, or the chip left by Show rules) waits until that filter is shown again. Rules that are safe to remove have Replace… too, as a plain button: removing them changes nothing today, but replacing keeps a merged or renamed town in the targeting.
  • Bulk replace. Leave Also replace it in N other rules ticked to move every one of them to the new place with this one click, each keeping its own entity and rule; untick it to replace only this row. The message afterwards says how many rules were replaced and, when some were left as they were, how many and why.
  • Freshness. The list is computed when you open the page; the places it looks up are remembered for about ten minutes, so a refresh after a cleanup is quick. The rail button’s count reads a check up to five minutes old (a minute while the geo service is not answering), so opening the trees does not look every place up again. Opening this page, removing or replacing a rule here, or saving or removing a location or country rule on a targeting card refreshes it at once. A rule saved on a targeting card is checked against the geo database when you save it — an unknown region or city is refused (Unknown region: …, Unknown city: …) — so new stale rules appear only when the provider renames a place later.
  • An outage is not mistaken for stale places. A place is listed only when the geo service’s own lists prove it unknown. When the service does not answer, answers for too few places, or nearly every place fails at once, the page shows Places cannot be checked right now with Try again and lists nothing; the rail button stays hidden rather than raise a false alarm. A handful of places with no clear answer are left out and counted under the header (… without a clear answer). An empty list is an answer, not an outage: a region named in a country the provider lists no regions for is stale, so a single such place no longer keeps a small network on Try again.
  • Fix with AI spends AI budget; nothing else does. Opening the panel is the only thing that asks the AI — and only about places it has not answered before; the list, the count and the Replace… dialog never do. It takes a few seconds for a handful of places and up to about two minutes for several hundred. A place the AI matched is never ticked for you, however sure it is. Answers are kept in the server’s memory for up to a week (a restart forgets them). Each match costs like a short assistant request on the same key and budget. Without the assistant permission, the assistant switched on, an AI key or budget left, the panel still opens with what names alone matched and says why.
  • Suggestions are re-checked when applied. A place the geo database dropped in the meantime is refused like any replacement; that card ends with a cross and the reason, without holding back the others. A card that ends in Remove has no current place, and removing its rules changes nothing.
  • Roles. Advertiser or publisher roles see only the rules of the entities they manage, on the side their role manages targeting on. With read-only (view) access the page does not open — there is nothing it could change. A user on an admin-based role has no account pages: use Switch user to a network user to clean up.

Not working?

  • No Stale locations button on the rail. It appears only while that side has rules whose removal would change delivery — safe rules alone never show it. In grid view look in the grid toolbar, right of Enable rule view. The count is up to five minutes old; open the page from a red chip on any targeting card to force a fresh check. If your role cannot manage that side’s targeting, there is no button on it.
  • The page refuses to open. Your role needs Manage Demand Targeting or Manage Supply Pre-targeting; a view-only role is refused. A user on an admin-based role must Switch user first.
  • “Places cannot be checked right now.” The geo service is not answering, answered for too few places, or nearly every place failed at once. Nothing is listed so nothing is removed by mistake. Click Try again in a few minutes; the message says which of the three it was.
  • A rule you expected is not listed. Check, in this order: the entity is deleted (left out); your role lacks the Location (or Country) targeting permission on that side or update rights on the entity (listed only when you may change it); the place is counted under … without a clear answer (try again later); the place is in fact current — a rule saved on a targeting card cannot be stale on the day it is saved.
  • Fewer rules were removed than you ticked. Rules ticked under another filter are not shown and not touched — clear the cards, If removed, Entity type and the Show rules chip. Otherwise the message names each skipped rule: Your role cannot change this rule, Not a stale place you can manage, or already removed (someone got there first), or It could not be changed this time and was left as it was. Try again.
  • Replace is refused. Unknown region / Unknown city: the picker matches as the geo service does — case does not matter, accents and spaces do (Sao Paulo is not São Paulo); pick from the list rather than typing. That is the place the rule names already: the provider lists the name again while the stale verdict is still remembered — pick the current name or wait ten minutes. Only location rules can be replaced: it is a country rule; remove it and add the country on the targeting card. The geo service did not answer. Retry later.: a real outage, not a wrong place — a look-up that fails for a moment never calls a real place unknown.
  • Fix with AI says “matched by name only”. The note tells you which: the AI assistant is switched off on this network; your role does not include the assistant; no AI key is set up; the monthly AI budget is used up; or the AI did not answer this time (try again later). The name matches still apply.
  • A place sits under Needs your decision. Either removing its rules would change delivery and no current name was found, or the geo service did not answer for it. Click Show rules, then Replace… each rule by hand, or try the panel again later.
  • A proposed change ended with a cross. The place was re-checked when applied and refused — usually the geo database dropped it since the panel opened. The others still went through; open Show rules for that place and replace by hand.

Reference

FieldMeaning
EntityThe advertiser, campaign, banner, site, zone or placement; a link to its edit page, where the targeting card shows the place in red. switched off / targeting off marks a paused entity or one whose targeting is off.
PlaceThe country, region and city the rule names (a country rule shows the code).
RuleInclude or Exclude.
If removedSafe to remove, Opens to all locations or Starts delivery — see the table under the steps.
Confidence (Fix with AI)High when the name matches a listed place spelled another way, or without its administrative word; Medium when both names match only with their administrative words set aside, or the city was found under a different region than before; Low when a city’s region is gone in a country with more than 80 regions. An AI answer is Medium at most. Only High name matches are preselected.
PermissionLets you
Manage Demand TargetingOpen the page and see rules of advertisers, campaigns and banners.
Manage Supply Pre-targetingOpen the page and see rules of sites, zones and placements.
Location / Country targeting (per side) + update on the entityHave that rule listed and change it.
AI assistant permission, assistant enabled, AI key, budgetHave Fix with AI ask the AI; otherwise names only.

How names are matched (accents, hyphens, administrative words, renamed regions, what the AI may and may not answer) is in Stale locations: matching and API reference.

Over the API

CallWhat it does
GET /rest-api/targeting/stale-locations.doThe same list: status, counts, rows with kind per rule.
GET /rest-api/targeting/stale-locations/count.doRules that block delivery per side (demand, supply), from the same check the rail reads. Cheap on a page load; do not poll it — after any location rule change the next call scans the whole network.
POST /rest-api/targeting/stale-locations/remove.dotargetIds; removes only SAFE rules unless confirmChanges=true.
POST /rest-api/targeting/stale-locations/replace.dotargetId (or targetIds for one stale place in bulk) + countryCode, regionName, cityName.
GET / POST /rest-api/targeting/stale-locations/suggestions.doOne suggestion per stale place; GET never calls the AI, POST is what Fix with AI sends.

Responses, skip reasons, error codes and the stale_locations / stale_locations_fix MCP tools are in Stale locations: matching and API reference. See also Targeting rules via API.

Related pages

Please disable Adblock
Are you using adblock? Disable it and reload the page to proceed to the destination page.

A registration has already been submitted from this page. Please try again in 10 minutes.