The mystery of xd_receiver.htm
I came up to my technical ceiling a few weeks ago when I was analysing some google analytics data for cookandkitchen.com.au
The top exit page was one called xd_receiver.htm. I was puzzled. The page did not exist on my site and yet the data was telling me that this was where most people left from. My mantra about helping clients with Google Analytics is “getting actionable insights”. What on earth was actionable about this? What conclusion was I supposed to draw from this and how could I keep people from running away?
What do you know! I got a reply from Facebook and a “call from Google” or a “Call from God” as cookandkitchen founder James Wright likes to call it. God is gonna give me buzz back but Facebook also had a good explanation as to why this page appears in the first place.
So, for techies this might mean something:
I understand this is part of the old mechanism for Facebook Connect. We clearly need to upgrade to “login with Facebook”. That is actionable. My mantra. But I am still puzzled why this page comes up as an exit page, but “God” is gonna sort that one out.
- A Solution To The Facebook fb_xd_fragment Problem (searchengineland.com)
- A Call from God (Eatwright.net)