---
title: "Count stale location targeting that blocks delivery"
type: reference
method: GET
path: /rest-api/targeting/stale-locations/count.do
tag: "Targeting Rules"
---

# Count stale location targeting that blocks delivery

`GET https://YOUR-NETWORK-DOMAIN/rest-api/targeting/stale-locations/count.do`

How many of the rules the list would show change delivery when removed (kind OPENS_ALL or STARTS_DELIVERY), split into 'demand' (advertisers, campaigns, banners) and 'supply' (sites, zones, placements). SAFE rules are not counted: the ad server already ignores them; rules of entities that are switched off or have targeting off are. Read from a network-wide geo scan up to five minutes old (one minute when the geo service did not answer well enough), which a list request refreshes, so asking it whenever a page loads is cheap; once that scan is out of date, or after any change to a location or country rule, the next count scans the whole network again - do not poll it in a loop. When the geo service does not answer, or nearly every place fails at once, 'status' is GEO_UNAVAILABLE with the reason in 'unavailable' and both counts are 0. Requires MANAGE_DEMAND_TARGETING or MANAGE_SUPPLY_PRE_TARGETING; only rules the user may manage are counted.

## Responses

- `200` — {success, status: OK|GEO_UNAVAILABLE, unavailable, demand, supply}
- `400` — Bad request — invalid or missing parameters
- `401` — Authentication error
- `403` — The role lacks both MANAGE_DEMAND_TARGETING and MANAGE_SUPPLY_PRE_TARGETING

## Example request

```bash
curl --request GET \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/targeting/stale-locations/count.do' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

Source: https://epom.com/ad-server/docs/api/targeting-rules/get-targeting-stale-locations-count