Home >
Paid Traffic Sources >
Facebook & Instagram
TrafficArmor + Click Loss (6)
08-20-2018 10:23 AM
#1
vondutch (Member)
TrafficArmor + Click Loss
Hey guys,
I'm dealing here with an issue which really affects our ROI on FB. We are dealing more and more with click-loss between the cloaker (TrafficArmor) & Facebook.
We see a difference in the amount of clicks we buy in FB and the amount of clicks we effectively receive on our prelanders. So to give an example:
We buy 1000 clicks from FB (that's the amount that reflects back in FB), we have a cloak rate of 10% (the % we grab from TA), in theory this means that 900 people should have visited our prelander but in reality we would have +/- 700 visitors. We often have a click-loss of +/- 15-20% which means that ON TOP of the cloaked clicks, we miss an extra 15-20% of the total amount of clicks bought.
I have no idea where these clicks are going to, TA is not able to help me either..
About our TA setup:
We use their WP extension integration method with iFrame.
tl;dr:
We miss more clicks in Voluum then our cloaker says it cloaked (ex: we see 10% cloak rate in TA but we miss 30% of the clicks, so where did the other 20% go?)
Is here anybody dealing with the same issue? Or does somebody know why/how ?
Thanks
//EDIT: What is this garbage Voluum advertisement? I type the name and you guys turn it into an affiliate link, weak
08-20-2018 03:39 PM
#2
Traffic Armor ()

Originally Posted by
vondutch
I have no idea where these clicks are going to, TA is not able to help me either..
That's a first.
Could you please private message me with your account details so I can look into your initial query further?
Some issues are indeed out of our control, in which case we would at least point you in the right direction. At times, once the issue is identified, we even reach out to third-party companies directly to sort out any issues for our users. I personally had a chat with FunnelFlux's awesome support recently on behalf of a user.
When it comes to click discrepancies with the referring source, we go as far as manually comparing your server's raw access logs against those recorded in your Click Log. For discrepancies with the outbound source, what we typically recommend is adding a third-party click tracking tool between us and them (ie. "tiny.cc" is a free option). You can then independently confirm the number of outbound clicks sent by us, and take the missing IP addresses to the outbound source (ie.
Voluum) for investigation.
If the click discrepancy is specific to a particular device, this should be quite easy to identify by querying the missing IP addresses in your Click Log. The user agent for those IP addresses should be consistent. You can then test your setup in that particular environment (or let us know, and we can gladly do it for you).
If you are opening the outbound offer links in a new tab, can you confirm that the meta tag from our Integration page to pass referrers was added? For their outbound offer links to work,
Voluum requires referrers in instances where their cookie cannot be read.
This is our typical debugging process for click discrepancies with all users, so it's odd if we didn't go through this with you. If that is the case, I apologize and will review the steps again with our team internally.
In any case, we are always online and happy to help!
08-21-2018 08:19 AM
#3
vondutch (Member)
I buy safe-sites which refrains me from getting good raw server logs. And since you guys are so persistent on receiving that before you can do anything there is nothing I can discuss with you guys. So that's why I write that you guys aren't able to help. To be very honest, I'm also sure it has nothing to do with certain browser types or devices, the devices and browser 99% of the world are using are all reflecting back in the clicks that we got in. It just looks like randomly some clicks are not triggering the cloaker script.
Anyways, I'm also not blaming it on you guys from TrafficArmor. All I explain to here is how our set up looks like to see if there are people who are also bleeding clicks without any logical reason.
08-21-2018 04:22 PM
#4
Traffic Armor ()
We wouldn't insist on anything. If a user can't provide something, we will always offer an alternative. They just have to let us know!
In your case, if the click discrepancy is with the outbound source, we wouldn't even need your server's raw access logs. We would have just asked you to place a third-party click tracking tool between us and the outbound source, so that we can independently confirm the culprit. Much of the battle for developers is recreating the issue. After that, even if the issue isn't on our end, we can point our users in the right direction.
It seems you would rather get help from STM, which is perfectly fine. I will halt further comments that might discourage others from contributing.
Should you prefer assistance from us in the future, we are online 24/7 and happy to help. 
08-21-2018 06:17 PM
#5
vondutch (Member)
Let me just PM you... because with all respect, no help without raw server logs, I have been in contact with your guys before also about heavy click bleeds and there was no way you guys could help without raw server logs (you can look up our chat logs to verify for yourself..). Let's see if we can solve it in PM.
So "It seems you would rather get help from STM, which is perfectly fine. I will halt further comments that might discourage others from contributing." is not the case.
08-22-2018 05:50 AM
#6
Traffic Armor ()

Originally Posted by
vondutch
Let me just PM you... because with all respect, no help without raw server logs, I have been in contact with your guys before also about heavy click bleeds and there was no way you guys could help without raw server logs (you can look up our chat logs to verify for yourself..). Let's see if we can solve it in PM.
So "It seems you would rather get help from STM, which is perfectly fine. I will halt further comments that might discourage others from contributing." is not the case.
As noted, we wouldn't even need the raw server logs when we are debugging click discrepancies with an outbound source.
There is absolutely no circumstance where we wouldn't help our users. If you can't provide us with something, we will always figure out an alternative.
Your PM doesn't contain your account details for us to contact you, let alone allow us to review your chat logs. Can you please send this to us?
Home >
Paid Traffic Sources >
Facebook & Instagram