News for hackers. Stuff that matters.
Re:Ask HN: Conversion rate increase with a Facebook sign-on? by fookyong on Tuesday August 10, 2010 @08:07PM (#1593332)
if signups are your metric, then I would guess you'd see an increase.

however, as others have mentioned on HN, by reducing friction you increase the amount of "tyre-kickers" - people who just want to check things out and leave.

that's not such a bad thing if your cost-per-user is negligible, or you have some kind of post-signup campaign in place (e.g. an email after inactivity that tries to "reactivate" the user).

in those situations, the more people you can expose your company to, the better. I'd wager that many startups don't implement Facebook signin because of the engineering overhead that could be spent on sexy new features.

Re:Ask HN: Conversion rate increase with a Facebook sign-on? by ebun on Wednesday August 11, 2010 @12:16AM (#1593805)
"I'd wager that many startups don't implement Facebook signin because of the engineering overhead that could be spent on sexy new features."

How much time is really spent integrating FB Connect?

Re:Ask HN: Conversion rate increase with a Facebook sign-on? by fookyong on Wednesday August 11, 2010 @08:43AM (#1594501)
The fact that it requires learning a new API makes it a non-trivial feature, engineering-wise IMO.
Re:Ask HN: Conversion rate increase with a Facebook sign-on? by ebun on Wednesday August 11, 2010 @01:17PM (#1595310)
I wouldn't have deemed it trivial, but the part I quoted made it sound like the associated workload was pretty heavy.

I haven't looked into the API or what it takes to integrate it, but I assumed (bad habit, I know) it wouldn't necessarily be rocket science. Aren't most API's relatively simple to use compared to the actually building of an app?

Plus, if it causes a huge increase in users and tire-kickers, it seems an app would get more chances to show off their sexy features anyway.

Re:Ask HN: Conversion rate increase with a Facebook sign-on? by msencenb on Wednesday August 11, 2010 @02:13PM (#1595495)
After looking at the docs it doesn't appear to be incredibly hard.

I think the most non-trivial thing would be integrating with the current site sign-on. Issues such as an existing users that decide to sign on with facebook (which is linked to a different e-mail address) could become a problem on the backend.

Re:Ask HN: Conversion rate increase with a Facebook sign-on? by Charuru on Tuesday August 10, 2010 @10:20PM (#1593605)
Do you have any basis? I mean we all know the theory why it might, but I'm not convinced?
Re:Ask HN: Conversion rate increase with a Facebook sign-on? by Reedge on Tuesday August 10, 2010 @11:58PM (#1593773)
We tested this with http://www.reedge.com for a client that integrated the facebook login on the checkout page of a Magento shop. I remember that Around 8% more finished the checkout compared to when we did not show the facebook login option.

The problem was we did not test the actual login, just having the option. The client did not give us details on revenue/turnover or hoe many people actually used login of facebook.

It was a health product on the US market.

Re:Ask HN: Conversion rate increase with a Facebook sign-on? by fookyong on Tuesday August 10, 2010 @10:52PM (#1593660)
wellll ok, the real answer is:

It depends on your execution.

In general, reducing friction will increase signups. That's hard to argue against. The only situation where reducing friction will reduce signups is where you seemingly reduce perceived value by doing it, but again, that all depends on execution.

Facebook connect sign in could be executed in a couple of ways:

1) Click a Facebook button. Click approve. Boom, you're registered in your app.

2) Click a Facebook button. Click approve. Get redirected to another signup form and have to fill in more data. Click "Send". Oops, there was an error with your form input, please enter a valid email address. Fill in data. Click "Send".

I can say with confidence that (1) will increase signups, but (2) will hardly move the needle.

It depends on your execution.