> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/proxies/targeting.md).

# Targeting

Master DataImpulse proxy targeting options. Configure country, city, ASN, session type, and more parameters to target the exact location you need.

We offer two types of targeting options for DataImpulse’s proxy network:

1. [**Default Targeting**: ](/proxies/targeting/default-targeting.md)\
   This includes country selection/exclusion and ASN exclusion. These options are already included in the base proxy price and are not billed additionally.
2. [**Target Filters**: ](/proxies/targeting/target-filters.md)\
   This advanced targeting option includes selection by state, city, ZIP code, and ASN. \
   Traffic routed through these filters is billed at double the standard rate.

{% hint style="info" %}
Traffic routed through the Target Filter (state, city, ZIP code, and ASN) is billed at double the standard rate.
{% endhint %}

<table data-column-title-hidden data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Default Targeting</strong></td><td>Country (select/exclude)</td><td>exclude ASN</td></tr><tr><td><strong>Target Filters</strong></td><td>State<br>City<br>ZIP<br>ASN</td><td></td></tr></tbody></table>

If no IPs are currently available for a specific city/state/ZIP/ASN, you will receive a `400 NO_RAY` response code. Please try another city/state/ZIP/ASN in such cases.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dataimpulse.com/proxies/targeting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.