Facebook Connect login preventing traffic source conversion data. Any solutions?

[Startupfactory]

We're buying traffic to the website via Adwords,   and when they hit the website and go to sign up for an application (enter into our conversion funnel),   the session concludes as a bounced session, a new session starts and that session now has a referral from Facebook rather than the original referring source. This means we can't monitor adwords conversions properly (or any other traffic source conversions) this seems to be quite a common problem with Facebook/Google account logins,  in the case of Google, people block account.google.com but we can't afford to block Facebook outright as we're wanting to see other Facebook referrals.

Has anyone come across this problem? Any suggestions of how to fix this?

[RyanPurkey]

There's a take on this at Quora here: http://www.quora.com/How-do-you-track-Facebook-Connect-signup-goals-in-Google-Analytics where the attribute is getting applied via a query string. In his example "redirect_to root_url(:new_facebook_user => resource.new_facebook_user)" 'resource' would be replaced with 'adwords' or whichever attribute you'd like. Cheers!

[Startupfactory]

Cool, thanks for the quick response! I will see if that is going to work for us.

[JasmineA]

Hey, how did this work? Did you get it to track appropriately?