11–20 of 30 posts
All the Facebook campaigns I have run use url parameter tagging to track clicks (i.e. for Google Analytics append &utm_source=facebook...) to the url. I think this is fairly standard practice so it seems unlikely to me that they'd have to use the referrer exclusively
> The first is that the traffic coming in had JavaScript disabled. If this was the case then the JavaScript analytics software would not detect the incoming traffic and therefore would not be able to log the result at all. Did you read their post? To quote: > Here's what we found: on about 80% of the clicks Facebook was charging us for, JavaScript wasn't on. And if the person clicking the ad doesn't have JavaScript,…
Most Javascript analytics packages also wrap an image call in a noscript tag to capture hits for browsers which do not have JS enabled. So yes, you can log the result with JS turned off.
So this article is claiming that 80% of people clicking on Facebook ads have chosen to use https? Seems way too high to me.
Facebook has been strongly recommending people switch this on (a one-step process, prompted in your news feed) for over a year now. http://www.insidefacebook.com/2011/06/02/https-secure-browsi... I'd be surprised if the number was as low as 80%.
> we're displaying this prompt when a user who has not enabled secure browsing (through the account settings option) manually changes their browser's address bar to https://, which does not fully protect their Facebook traffic.
I just had to go hunting through privacy and security settings for 5 minutes to figure out how to enable HTTPS.
So no, I would guess fewer than 0.1% of Facebook users have this enabled.
I'll admit I know little to nothing about how prefetching works.
> The first is that the traffic coming in had JavaScript disabled. If this was the case then the JavaScript analytics software would not detect the incoming traffic and therefore would not be able to log the result at all. Did you read their post? To quote: > Here's what we found: on about 80% of the clicks Facebook was charging us for, JavaScript wasn't on. And if the person clicking the ad doesn't have JavaScript,…
If this was the case then the JavaScript analytics software would not detect the incoming traffic and therefore would not be able to log the result at all. Most Javascript analytics packages also wrap an image call in a noscript tag to capture hits for browsers which do not have JS enabled. So yes, you can log the result with JS turned off.
Although the author of the original post said nothing, i assume that's what they did.
I was hoping the article would be a little more informative and definitive according to the title. It is based on assumptions itself with a little theory behind it. As for the statement - "The first is that the traffic coming in had JavaScript disabled. If this was the case then the JavaScript analytics software would not detect the incoming traffic and therefore would not be able to log the result at all." You can t…
I can't believe someone who has 'delivered highly scalable solutions' actually managed to write this line on his blog with a straight face. How were you not able to deduce that the devs likely detected disabled javascript without the use of javascript? His whole post is devoid of content and nothing but statements without any real substance or evidence.
edit: never mind; an img in a noscript tag.
> The first is that the traffic coming in had JavaScript disabled. If this was the case then the JavaScript analytics software would not detect the incoming traffic and therefore would not be able to log the result at all. Did you read their post? To quote: > Here's what we found: on about 80% of the clicks Facebook was charging us for, JavaScript wasn't on. And if the person clicking the ad doesn't have JavaScript,…
If this was the case then the JavaScript analytics software would not detect the incoming traffic and therefore would not be able to log the result at all. Most Javascript analytics packages also wrap an image call in a noscript tag to capture hits for browsers which do not have JS enabled. So yes, you can log the result with JS turned off.
I was hoping the article would be a little more informative and definitive according to the title. It is based on assumptions itself with a little theory behind it. As for the statement - "The first is that the traffic coming in had JavaScript disabled. If this was the case then the JavaScript analytics software would not detect the incoming traffic and therefore would not be able to log the result at all." You can t…
I can't believe someone who has 'delivered highly scalable solutions' actually managed to write this line on his blog with a straight face. How were you not able to deduce that the devs likely detected disabled javascript without the use of javascript? His whole post is devoid of content and nothing but statements without any real substance or evidence.
Earlier quoted context omitted.
Facebook has been strongly recommending people switch this on (a one-step process, prompted in your news feed) for over a year now. http://www.insidefacebook.com/2011/06/02/https-secure-browsi... I'd be surprised if the number was as low as 80%.
I've never received that prompt. If you read further down in that misleading article you linked to, you would see that they don't show the prompt to all their users: > we're displaying this prompt when a user who has not enabled secure browsing (through the account settings option) manually changes their browser's address bar to https:// , which does not fully protect their Facebook traffic. I just had to go hunting…
So this article is claiming that 80% of people clicking on Facebook ads have chosen to use https? Seems way too high to me.
Facebook has been strongly recommending people switch this on (a one-step process, prompted in your news feed) for over a year now. http://www.insidefacebook.com/2011/06/02/https-secure-browsi... I'd be surprised if the number was as low as 80%.
I thought the same thing as parent. It seems the poster is suggesting that tons of people are using https, and I can almost certainly say that just about everyone I know does not use that feature.
I believe the poster of that facebook post (Limited Run) said they would post their analytics details or something like that. I'd kind of like to see them, myself.