# Configure Block Routing Rules
**Blocks**, a type of **Routing Rule**, will prevent traffic from being redirected to another web page. When traffic that meets certain criteria (known as *conditions*), for example, clicks on an ad that one of your partners is hosting, they will instead be blocked from visiting the ad's destination URL.
Traffic sourced from certain partners, specific countries, and even traffic that comes from a set URL (i.e., a *referring URL*) can be blocked from reaching a destination URL.
#### **Create a block rule**
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. On the right, under *Technical*, select **Blocking & Redirect**.
3. In the top-right corner, select **Configure rule**.
4. Add a **Name** for your rule.
5. In the *Condition* section, use the drop-down menus to configure your block rule.
* View the *Conditions reference* below to learn more about the different condition attributes.
6. In the *Action* section, ensure you set the drop-down menu to **Block**.
* If you want to have an [interstitial web page](https://en.wikipedia.org/wiki/Interstitial_webpage), toggle on and configure  **\[Toggle on]** **Use interstitial**. Ensure you set the *Template* drop-down menu to **Custom**.
7. Optionally, **Schedule** when this block rule will be active.
8. **Rank** the block rule.
* If multiple block rules share some of the same conditions and the same **Rank**, the one with the lower **ID** will take priority.
9. If you don't want the block to begin immediately and you did not **Schedule** the rule, you can **Pause** the rule.
* You will need to manually unpause this rule for it to become active.
10. **Save** your block rule.
**Interstitial setup**
Refer to the table below for more information about each of the options available for setting up a block interstitial.
| | |
| ------------------------ | ----------------------------------------------------------- |
| **Interstitial Setting** | **Description** |
| Header Text | A short phrase displayed on the interstitial in large type. |
| Body Text | Information that traffic will see on the interstitial. |
| Preview | Opens a new browser tab to preview the interstitial page. |
Condition reference
*Condition* setup works in an *AND/OR* system: Selecting  **\[Add]** **AND** will further refine a specific condition, whereas selecting  **\[Add]** **Add another** will add a separate condition that can, but does not necessarily need to, be met for the block rule to activate.
Below are the different attributes that can fill a condition:
| | |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Condition Attribute** | **Description** |
| IP Address | The IP Address registered to a device. |
| Shared Id | A partner-controlled query string parameter that is used in reporting. |
| Country | The country from where traffic is sourced. |
| Region | The geographical region from where traffic is sourced. |
| Ad Status | The associated ad's state of use. |
| Sub Id1 | A partner-controlled query string parameter that is used in reporting. |
| Sub Id2 | A partner-controlled query string parameter that is used in reporting. |
| Sub Id3 | A partner-controlled query string parameter that is used in reporting. |
| MP Id | impact.com's unique Id for a partner. |
| Device Type | What type of device the customer was using when the block rule is prompted to activate. |
| Ref URL | URL of the website that is referring traffic to the original destination URL. |
| Landing Page | The original destination URL. |
| Product SKU | An Id for the subject of the ad, which is usually designated in a product catalog. |
| Ad Id | impact.com's unique Id for an ad. |
| Probability | The block rule will randomly grab a percentage of traffic to be rerouted. This is primarily used for A/B testing. |
| Mobile Fallback |
If an ad has mobile fallback configured, the associated routing rule can request to reroute traffic to their respective app store to download an app.
You will never need to set up a block routing rule with a mobile fallback condition since traffic will not be redirected. Learn more about mobile fallback and app interstitials.
|
#### **Bulk upload block rules**
Block rules can also be uploaded and configured in bulk with a .XLSX or .CSV file. Not all file columns may be available for use—Refer to the [impact.com Routing Rule Bulk upload Data Fields](https://docs.google.com/spreadsheets/d/1wt39bVgv9p4XVNzF8MaBdRFTAD5DUPwZKM6jnR5OAnM/edit?usp=sharing) spreadsheet to learn more about each column.
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. On the right, under *Technical*, select **Blocking & Redirect**.
3. In the top-right corner, select **Bulk Upload**.
4. Select **Choose File**, then select your file.
* Refer to the [impact.com Routing Rule Bulk upload Data Fields](https://docs.google.com/spreadsheets/d/1wt39bVgv9p4XVNzF8MaBdRFTAD5DUPwZKM6jnR5OAnM/edit?usp=sharing) spreadsheet to see how your file should be formatted.
5. Select **Next**.
6. If validation errors exist, select **Back** to upload a new file. Otherwise, select **Accept & Create Rules**.
* Any block rules with validation errors will not be created.
Redirect rules uploaded in a bulk file can take up to a day to process.
#### **Archive a block rule**
Archiving routing rules works in the same way as deactivating them: traffic will no longer be blocked according to the condition(s) set in that block rule. No type of routing rule can be entirely deleted.
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. On the right, under *Technical*, select **Blocking & Redirect**.
3. Find the rule you want to archive, then select  **\[More]** **→ Archive**.
4. Select **I understand, continue**.
You can reactivate archived block rules at any time by selecting  **\[More]** **→ Reactivate**.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/blocking-and-redirect-rules/configure-block-routing-rules.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
