Redirect methods
The redirect method defines what a visitor sees between the click and the destination URL: 10 methods, from Meta Refresh to 302 and iFrame.
The redirect method defines what a visitor sees between the click and the destination URL, whether the destination site learns where the visitor came from, and how the link looks in messengers.
You choose the method in the Traffic route block of a template (Links mode) or a campaign (Tracker mode). The list splits the methods into two groups.
Redirect right away
| Method | How the redirect happens | Site sees the source | Preview from Meta Settings |
|---|---|---|---|
| Meta Refresh | a short blank page, then the redirect | no | yes |
| Double Meta Refresh | the page reloads once, then the redirect | no | yes |
| JavaScript | a script redirects | no | yes |
| 302 Temporary | an instant redirect | yes | no |
| 301 Permanent | an instant redirect that the browser remembers | yes | no |
| Preloader | a loading screen for 2 to 3 seconds | no | yes |
| Image And Redirect | shows an image, then the redirect | no | yes |
Show a page with a transition
| Method | How the redirect happens | Site sees the source | Preview from Meta Settings |
|---|---|---|---|
| Button Page | a page with a button, the redirect happens on a press | no | yes |
| iFrame | the destination opens in a frame under the link address | no | yes |
| Simple Iframe | a plain frame with no wrapper, for simple pages | no | yes |
The method is read on every click, so changing it applies at once to all links of the template or campaign.
How to choose
- With no special requirements, Meta Refresh fits.
- The destination site must see the source: 302 Temporary. With other methods you can pass the source in the
{referer}macro. - You need your own preview in messengers: any method except 301 and 302.
- You need the strict JavaScript filter: Meta Refresh, JavaScript or Image And Redirect. The browser check works only with them.
- The destination may change: do not use 301, the browser will remember the old address.

Double Meta Refresh
The click is recorded only after the page reloads. A visitor who closed the page earlier does not reach statistics.
Delay and parameters
In Advanced Settings → Redirect Settings you set the redirect delay, from 0 to 30 seconds. It does not apply to 301 and 302. The Parameter Forwarding field is there too: Off, GET parameters or GET + URI. It decides which parameters from the link address go to the destination.
Previews in messengers
Messengers build a preview from what they receive when they open the link. With the filter on, their crawlers count as bots and do not reach the destination, so with 301 and 302 the preview comes from the bot URL page. At the filter level Off, messenger crawlers pass as people, and with 301 and 302 the preview is built from the destination.
The preview from Meta Settings is not shown with 301 and 302.
Landing
Instead of a URL, a link can open your landing: the Landing switch in the Where traffic goes field. How to create a landing and tie its button to an offer is in the Landings article.
Bot filtering: levels and lists
The bot filter decides which clicks count as bots: four levels from Off to JavaScript, a bot action, quarantine and your own IP and User-Agent lists.
Landing pages
A landing page is your HTML page right at the link address: built in the editor, uploaded as .html or .zip, or drafted from a description, with an offer button.