Hey guys I just started my first mobile campaign on decisive and in the traffic network dashboard it show 345 clicks but in my affiliate network it only show 113 clicks. Is this normal? about only one third of the clicks show up at the affiliate network. Oh by the way I am using cpvlab for tracking and I show 422 clicks there more than I see on the traffic network. Am I doing something wrong? I appreciate and welcome any help. and thanks for taking the time to read my post :-)
How are you redirecting users to the affiliate link?
Check your tracker data to see if many clicks are detected as outside your target country.
Test your tracker URL on a mobile device.
yup I did that and it looks like the clicks are coming from the targeted country Malaysia
In CPV Lab do you have the option to do meta-refreshes or 302 redirects, and/or use cloaking? Are you using just 302?
You could also hit up your AM and ask for a click report, i.e. to see if there are any bounced for geo for example.
ok I will talk to my AM and see what he say. Thanks Zeno you rock :-)




You should absolutely be using the direct redirect.
Unless you want/need to hide information from your network, the direct redirect is the best option in all circumstances, period.
It will always be the fastest.
A quick summary:
Direct redirect, also known as a 301/302 redirect - user requests URL (e.g. tracker URL), tracker responds to request with a new URL i.e. an http header and the browser moves on to that URL instead. This involves no downloading of anything from the user, they ask for A and get told to go to B.
Meta refresh - user requests URL and tracker sends them to a page. On this page there is a code in the head part of the page that tells it to immediately refresh or go to a new URL. The user requests A > gets sent to page A, page A is partially loaded by the browser but immediately told to go to page B. The page wouldn't load body content because the head part of the page tells it to go somewhere else immediately. So, no page content on A gets displayed to the user. This redirect happens client side so is useful if you don't control the server-side.
Javascript - user requests URL > loads page, browser processes javascript on the page that tells the browser to redirect. Easily the slowest approach possible. Could put redirect in head or body, head would be better (avoids browser loading page content once again).
The direct method is unequivocally the fastest but it passes referrer information. If you want to blank referrer info, i.e. where the clicks came from (traffic source), you can do a meta refresh to page B which then meta refreshes again to your outgoing URL. The referrer on page A is the traffic source. The referrer on page B is page A. The referrer on the outgoing URL is then page B. These hops are added in an attempt to hide referrers but this is clearly going to slow things down as your users a) get redirected slower in the first instance, b) have to do it twice.
301/302 redirect:
User -> requests tracking system URL -> requests offer URL.
Meta refresh:
User -> requests tracking system URL -> requests page A -> partial load of page A -> requests page B -> partial load of page B -> requests offer URL.
Clearly the meta refresh has a lot more potential for click loss, especially if you have a high user-server latency and poor user connectivity.
)In an ideal world, you wouldn't have to hide anything.
Do it if a) you don't trust the network, b) you are doing things that you don't want them to see.
If you have for example submitted all landers for approval, then there is little point in then cloaking them (unless you want to hid your domain name because it is used elsewhere).