Voluum Double Meta Refresh (7)
Hi all,
I am a bit confused about
- 302: Server side redirection, so quick. Doesn't hide referrals
- Meta refresh: Page Redirection hiding specific page referral but not domain, and slower than 302
- Double Meta-refresh: Page Redirection hiding referral completely, but slower than previously, as it has 2 refresh
If I am ok, I have a doubt about Double Meta- refresh. Why are
<meta name="referrer" content="no-referrer">
https://www.w3.org/TR/referrer-polic...cy-no-referrer
Thanks!!
Carlos
Hey Carlos,
You seems to be correct, here is the description right from the Voluum's knowledgebase:
302
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.
-----
To answer your question why they are using a "slower" way is maybe because of the browsers support?
Here is some data about versions of browsers that already support this feature: http://caniuse.com/#feat=referrer-policy.
Once it will be more widely accepted I believe the trackers will switch to this solution as well.
Hi erikgyepes ,
Thank you for this quick and precise answer, it was really helpful for us!! Have a nice day!
Carlos
You are welcome Carlos! 
Wanted to add something, I did some tests and compared 302 and DMR to see whether it would make any impact on the conversions and I didn't see almost any. So the slower redirect speed wasn't really an issue for me. I know some people report DMR to caue problems, but I wasn't able to recreate it on my own.
One way or another, even tho DMR can help, it's still not 100% bulletproof and in some cases (browser dependent) the ref info will be passed through anyways.
Hello, I am nontechnical and pretty new to affiliate marketing. I've been using met refresh. But I just realized that my vital campaign information is showing up on Adplexity in my campaign url. For example Popads tokens such as bid shows bid=0.002. Does double meta refresh hide this type of information from spy tools and affiliate network?
Hello!
Yes, double meta refresh does add a layer of protection one could say.
-Alex
Home > Questions and Answers > Tracking Questions