Is wall sharing (performed through the FB JS API) in any form related to the Site URL setting for a given application? Users don't actually log in to our website using the tool - they just share the URLs on their walls via an application we've setup.
We are looking for expert confirmation on the subject as we'd like to change the Site URL in support of a new login provider wrapper (Janrain).
No, you can share urls even if the Site Url is not supplied. But the domain should be listed in the "App Domains" box. This shouldn't be a problem since it supports multiple domains. An example would be both myapps.mydomain.com and myapps.myotherdomain.com are listed there. I think this is ok in your case.
Related
I've made a website, which relies on Facebook OAuth in order for the user to participate in a competition.
The canvas URL within Facebook differentiates between https://www.mycompetition.com/ and https://mycompetition.com
Our server is set up to receive both entries, but if I enter the site using www, Facebook complains that the URL doesn't match when authorizing.
Do you know how to make Facebook accept both entries?
Solved, by the way. The webserver now contains two websites. The first contains the website, the second one just redirects to the first one, using JS. Easy :)
Just got this message from the FB debugging tool : is not allowed for the specified application id. I'm trying to post a story using Open Graph on Facebook. Right now I'm using the Graph API Explorer, but will eventually use the Facebook SDK.
I AM using a different domain from the domain I'm using to host the meta tag URL. My understanding was that Open Graph needed a publicly accessible page from which to read meta tags. I was under the impression that this page DID NOT have to live at the same domain as my app. Is that wrong? So, does this mean that the page with all the meta tags has to live on the same domain as my web site?
To be clear: the FB app is configured to use domain X, but I'm hosting the OG page on domain Y. Is that a problem?
Update:
Okay, I'm still getting the error this AM. It seems like I'm getting contradictory info. Given that this is Facebook support, is there some way I can escalate?
I still don't know what the issue is, but I was able to get this working by changing my local dev URL to an address that shared the same domain as the URL that was hosting the OG object I needed.
So, locally I've set my environment up to be: mylocal.sample.com, and the OG is hosted at public.sample.com.
I have developed a Wordpress site that is hosted on the client's server. The client does not want to enable SSL on the server, but wants to be able to auto post from WP to an existing FB page. Is this possible? I know there are a couple of awesome plugins but they all require a FB App to be created. The client does not want to do this, they want to use their existing FB page. Me thinks I might be in for some extra coding.
There are a number of APIs available to work with pages:
https://developers.facebook.com/docs/reference/api/page/
I'm not sure exactly what you're looking to do from WP, but there might be a way to do that through the Page API. Note that working with pages requires you to have a page access_token, which you will need to set up.
You can set their facebook page up with this plugin: https://www.facebook.com/networkedblogs. It will allow for blog posts to be automatically posted on a facebook page.
In my Google Analytics reports I get "facebook.com / referral" as the source. Is it possible to get the exact URL?
I don't think it's possible. as #yahelc pointed on a previous comment most traffic from facebook goes through a facebook controlled redirect on page facebook.com/l.php .So if you want to have campaigns on facebook you can use urls with campaign query parameters to keep track of it.
eg: link to
http://www.example.com/?utm_campaign=Facebook&utm_medium=social&utm_source=facebook.com
Now they will show up in GA as a separate campaign and you can tell how many visitors come from that specific link. You probably want to minify that link using bit.ly or goo.gl.
Create multiple campaigns on facebook and change the utm_campaign parameter as much as you want. You can also create different utm_content parameter to separate your marketing efforts on facebook. Keep the utm_medium and utm_source as static as on the example above.
This is how social marketing analytics measures marketing efforts on social networks. Anything that comes from facebook is not tagged you know comes from people posting links to your site other than you.
At the same time it really makes no sense to have the referral url at all. If you think about it most of the times it will be from private posts that you don't even have access to see, even if you had a url for it. That's just not the way facebook works. It doesn't have pages, it has streams and posts.
More about url tagging:
http://support.google.com/analytics/bin/answer.py?hl=en&answer=1033863
The answer is yes and no. You can drill down to referral path for facebook source in the report Traffic Sources -> Sources -> Refferals by simply pressing facebook.com at the Source coloumn, just like for all other visits from the referring site.
But that would be not much of a use, because for facebook you'll always see /l.php. And that's how facebook works, it doesn't allow visitors to visit the link immedeately, instead it redirects user to the page with url facebook.com/l.php?u=<link-to-your-site.com> with a redirect or maybe with some text like "if you're sure you want to leave", so technically, the referring page would be this /l.php that GA shows.
So if you need to track the efficency of your Facebook activities - use utm tags, like #Eduardo Cereto mentioned. Here's a very nice video tutorial on link tagging for GA: http://services.google.com/analytics/breeze/en/v5/campaigntracking_adwordsintegration-v23_ia5/ (starts from p. 17, you can skip all that goes before).
Hope it helps!
i just know this settings here:
http://www.sebastienpage.com/2009/05/06/google-analytics-trick-see-the-full-referring-url/
I'm building an app using Backbone.js and a private API that serves assets and JSON.
Most content in the app is accessed through the root '/' and the Backbone router serves up views based on the hash (ie /#about or /#view).
The problem is that when a page is shared to Facebook, it scrapes the main page and seems to disregard anything past the hash mark.
Are there any good rules of thumb for url paths or content that is not highly dynamic to make the app more presentable to Facebook, Google, etc?
Google has some good info on making AJAX apps crawlable.
https://developers.google.com/webmasters/ajax-crawling/
You could create a dummy page on your site with a full URL that is only accessible to the bots that Facebook and Google use. I'm not sure what Google's user agent is, but Facebook's is listed here:
https://developers.facebook.com/docs/reference/plugins/like/#scraperinfo
So you could have a blank page on /item/itemid1/ that is only accessible to the bots, point your og:url tags to that blank page and have the correct metadata on it for the Facebook scraper. Whenever a regular user tries to access it, redirect them back to the correct hash-based URL.