With the new pixel it becomes abundantly clear if you are firing the pixel from different domain. IN the past I didnt worry too much about cloaking the old pixel but still used an iframe system like here http://listen.fraudbuster.im/w/I8QY5...XOGWgP1DpHEErg
this doesn't seem to work for the new pixel though. Could someone help with a solution to this issue? It seems pretty dumb to leave it uncloaked where the firing urls are listed right there in pixel backend.
Any help is appreciated! Thanks.
I don't cloak and know nothing about it, but what if you use the same lander URL by using PHP to echo a different html based on the user? That way the pixel should fire from the correct URL no matter what and if FB checks it out they still see the cloaked page.
xxf8xx is correct. Just use a PHP include and switch based on cloaking status.
I've been using traffic armor which I don't think does PHP includes. Will contact their support and then possibly switch cloakers. Thanks guys!
For non-conversion events you can use the ns version of the pixel and drop it inside of a frame. For conversions ("Purchase" events) use an inline-frame instead of a postback/image and drop the ns pixel in it based on the SID.
<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=<FB_PIXEL_ID>&ev=PageView&noscript=1"/>