Traffic Redirect Methods
Traffic Redirect Methods
Redirect method defines the technical way a visitor is redirected from a tracking link to a target URL (flow, landing, PWA, or offer). The setting is specified in the campaign settings and applies to all traffic of this campaign.
Why is it needed
From the user's perspective, the result is the same — they land on the target page. But the method of transition affects the technical details that are important in traffic arbitrage:
Refererheader — it shows the target page (as well as the anti-fraud systems of ad networks and partners) where the click came from. Some methods pass the referrer, while others hide or clear it.- Compatibility with moderation and anti-fraud of advertising platforms — different transition methods appear differently to verification systems.
- Speed and reliability of the transition, as well as behavior in mobile in-app browsers (Facebook, TikTok, Instagram).
If you have no special requirements — leave the default method (HTTP redirect 302). It is the fastest and most predictable. Other methods should be applied consciously, for specific tasks.
Where to configure
Open the campaign → main settings block → “Redirect method” field and select the desired option from the list. By default, all campaigns (including those created earlier) use HTTP redirect (302) — this preserves the previous behavior and requires no action.
Available types
Method | How it works | When to apply |
|---|---|---|
HTTP redirect (302) | Server-side redirect: in response to a click, an HTTP status 302 is returned with the new address in the | The basic option for most campaigns. The fastest and most reliable, works everywhere. |
Meta refresh | An HTML page is returned with the | When a transition is needed through the page rather than the server, or to change the referrer behavior compared to 302. |
JS redirect | A page is returned with JavaScript that redirects the user to the target URL (via | When a transition through a script is needed — for example, to execute logic on an intermediate page before the redirect. |
Without referrer (empty referrer) | The transition is performed in such a way that the target page does not receive the | When there is no need to pass information about the traffic source to the target page. |
Double meta refresh | The transition occurs in two steps through an intermediate page with a meta refresh. The additional “jump” breaks the direct referrer chain between the source and target pages. | When it is necessary to more reliably clear the referrer chain than with a regular meta refresh. |
Form submit | The transition is initiated by automatically submitting an HTML form to the target URL (usually via POST method). | When a transition through form submission is preferable to a regular link or redirect. |
iFrame | The target page is loaded inside a frame ( | When it is necessary to show the target page without changing the URL in the address bar. Keep in mind that some sites prohibit embedding in a frame. |
Recommendations
- Do not change the method “just in case”. For normal operation, HTTP 302 is sufficient — it does not create unnecessary intermediate pages and redirects as quickly as possible.
- Choose methods that hide or clear the referrer (without referrer, double meta refresh) only when it is really needed by the platform or link requirements.
- Methods that depend on the client (JS redirect, iFrame) require working JavaScript and correct browser behavior; in some in-app browsers, behavior may differ — test the link on a real device.
- After changing the method, check the transition via the tracking link from a real device and ensure that the click and conversion are recorded in the statistics.