Introduction
Developing and testing ad server setups on a production website can be slow and inefficient, especially when switching between local and production environments. Constantly uploading new configurations to test changes takes up valuable time, hindering rapid iteration.
With Requestly, you can connect your local ad server directly to the production website, speeding up the development process by 2x and enabling real-time testing without any delays.
Redirect Your Local Ad Server to Production
The Redirect Rule in Requestly enables you to easily redirect requests from a production website to your local ad server, allowing faster testing and development. This eliminates the need for continuous deployment, letting you fine-tune ad configurations in real time. By working in a live environment without affecting the client’s production setup, you can gain accurate insights while reducing development time by 2x.
- Another URL:Â You can redirect the request to a different URL. In this case, the redirection is happening to a new JavaScript file URL.
- Local File:Â This option lets you redirect to a local file stored on your machine.
- From Files/Mock server: You can also choose to redirect the request to a file hosted on a mock server or from files you’ve set up.
- Source Condition:Â This determines which requests will be redirected. Here, any request containingÂ
https://production.example.com/ads.js will be redirected. - Destination URL: This is the URL where the request is redirected. In the example, it’s redirecting to a new debug script.
- Test URL Condition: You can check if the rules you’ve set up work correctly by testing them on specific URLs.
- Filter Out Condition:Â You can applyÂ
filters to limit which requests are affected, making sure only the ones you want are modified.
Or create your own Rule by following the steps below
Interactive Guide
Check this interactive and easy explanation of how to use Redirect Rule
