Redirect modes (302, Meta refresh & Double meta refresh)

Within a campaign's / flow's configuration you can choose one of the following redirect modes;
  • 302
  • Meta Refresh
  • Double Meta Refresh

Here's an explanation of each mode;


Standard temporary redirect that sends visitor to the desired location ( Lander OR Offer ) along with referring data. 

Meta refresh

Is implemented via a code put in the <head> tags of an html document that tells the browser to refresh and load a new URL.
In this case, the browser does start loading the page - but only the head, not the body, before going to the new destination.

Double meta refresh

It performs meta-refresh twice in a row. 
This way, the first meta-refresh page has the referrer we want to hide. It goes to a second page, and the referrer is now the first meta-refresh page.
This goes to our affiliate link, and the referrer is now the second meta-refresh page. 
This mode is slow due to the multiple page loads by the browser (particularly for mobile traffic). However, It is the most effective in obscuring the referrer data sent through to a campaign's endpoint (offer).

In general, meta refresh modes are used by advertisers when they wish to pass alternate referrer data through the interim redirects within a campaign's funnel.

This is applied by the changing the referring data* which is sent to the campaign's endpoint (offer) via an interim redirect domain.

For example,
You have a campaign with a landing page included within it's funnel, when visitors click through on the LPs CTA link and are then redirected to a 3rd party offer,
the offer owner / host won't see referrer data to identify your landing page, but will see different referred data (domain) passed instead.

   Contact us

Feedback and Knowledge Base