I have some use-cases related to Facebook social plugins . Basically, these all plugins from Facebook are for web development. But I need these for my flutter apps. Three of the use-cases are -
Use-Case 1: I want to reward some points to my users if they invite others to link my app's Facebook page.
Use-Case 2: I want to reward some points to my users if they like my app's Facebook page.
Use-Case 3: I want to reward some points to my users if they share their score with screenshots taken by the app automatically to their News feeds. (Although I got some plugins for this but they didn't look handy to me as there are no success callbacks to prevent spam that if the user really shared the score with a screenshot. I also observed that these plugins only share captions or screenshots at a time but not togetherly)
I have a fairly unique business model in which I need to use a retail partner to sell my produce because licensing is difficult. They have to collect money and transfer it to supplies on my behalf so my product must be sold on their site.
They have their own acquisition campaigns running through facebook and therefor have a facebook pixel passing data for those ads and it's directly integrated into shopify. Our products end up just being another sku on their site but we would like to also support those with facebook ads so would need to have our pixel as well. Unfortunately shopify only allows one tracking code from facebook.
Would there be any issue is setting our facebook pixel up on Google Tag Manager (we have the container across their site) and expecting it to fire in parallel with the pixel that they have integrated into shopify?
Followup, same scenario for Google Analytics, Google Adwords, etc.
Thanks!
We publish advertisement on facebook and we have a new domain. The problem is that advertisement click rate on facebook panel is 6193 but only 1682 person enter website accordşng to google analytic.
There are about 4500 hit which is lost. AS you know, users are redirected to our website after click on facebook advertisement but they cannot access to our website. we are waiting your kindly response.
our website: testmastersatinal.com
Try using Google's URL builder to properly code the landing page URL in such a way that GA will recognize the traffic as having come from your FB advertising campaign. Here's a blog describing how it is done.
For reasons that I do not yet completely understand - but apparently have to do with the internal FB redirect process for ads, much of my traffic from Facebook shows up in Google Analytics as (direct)/(none). I've found that setting the GA UTM codes on the landing page URL will help by using Google's URL builder helps with this issue.
More generally, in my experience, advertiser reported clicks are often different from what you see in GA. In fact, I'm working on trying to resolve this issue now with another advertising platform (not FB) who is billing us for 2.5x the number of clicks we are seeing in Google Analytics.
There are many possible causes for this, and you can find relevant discussions on
webmasters, moz.
One thing you should try is segmenting the referrals by device (mobile, tablet, desktop) or operating system, etc. See if the percentage of traffic is much lower from your ad on one particular device or operating system. This may indicate that the GA tracking is not working correctly on that device or OS.
I have submitted our facebook app for App center review, but it has been in pending status for 10 days, according to facebook App center guideline http://developers.facebook.com/docs/appcenter/guidelines/ "Once it has enough positive ratings and engagement, we will automatically review your app detail page and contact you if any changes are needed before it appears in a category."
Could anyone please tell me after a facebook app submitted for review, how to get enough positive ratings and engagement? What is exact rating/engagement amount? Where can I see the progress? Any facebook app center contact email?
Any help is appreciated.
Not to disappoint you, but we had our app being reviewed for 4 months and 11 days before our patience ran out. We had 50K users and 400 5* ratings out of 450 total ratings. It is insane how irresponsible FB is regarding reviewing content. We resubmitted the app for review and it took several days before the app was live in App Center.
Positive ratings is when users that installed your app rate it from 1 to 5 stars. Engagement is basically how many users installed your app in total and how many did not remove it within short period of time (the more the better). There is no exact amount, but for example 10K new installs in first week is better than 10K installs in first year, yet the number is the same. Same goes for the progress bar - Facebook has its internal metrics. Good luck with review.
We are unable to submit the application page / details for review in the App Center, because
"Your app does not have high enough ratings and user engagement to be reviewed for the App Center at this time".
I asked some questions about this:
1) How can we improve ratings without being listed in the Facebook App Center?
2) Our user engagement is about the same level as other apps in the same category, which are published in the App Center. What is a critical mass to be eligible for review? Which numbers are relevant?
The response I got from a Facebook developer:
1) We randomly ask users that uses your app to rate it.
2) There are no specific number. Our algorithm takes in as much data as possible and try to figure out if it is a high quality app. But in general if you get bad review you need more active users, And if you have good reviews you need less.
Update:
In our case, we had to disable the web and mobile web implementation in the App details section, because they had too few users (so only Android/iOS was still enabled - our main applications). After that we got approved.
The process for submission app is very tough. We need to strictly follow the guidelines. We need to sure what type of App we are developing and list of permissions are needed. Due to spamming by many Facebook App developers, Facebook app center required exact reason to get approve the required permission.
Here is an example of submission guidelines.
Tags
There may be scenarios where your app's users want to tag a friend. This tagging capability comes in two forms. One scenario is if the user takes an action with the friend (i.e. cooks a pizza with someone), and the other scenario is when the user simply wants to mention a friend (i.e. "Hey John Smith, let's make a pizza next time"). If you choose to choose to support both action and mention tags, clearly distinguish the two different use cases in your submission.
Action tagging appends "- with Friend" to the story.
Mention tagging allows your app's users to tag friends names within their user messages.
App Center Guidelines App Center Guidelines link
Submission process https://developers.facebook.com/docs/opengraph/submission-process
Please go through the submission guidelines as well. I hope this will help anyone.
I could upload two of my apps to App Center but now as though I don't have the correct gaming type option to be able to upload one
I want to develop an online application and I am considering EITHER building a website with community features built in or building ONLY a facebook app. I was wondering if other people have had to make the same decision and what things I will need to consider.
The website I want to build will be an educational portal where people can make and take tests online
I disagree with some of the other answers here. There is a huge difference between a) trying to advertise a new place on the web and b) trying to advertise a new functionality of an existing place. Even if this new website would offer a very tight integration with Facebook and some other social platforms. Keep in mind: facebook users really don't like to leave facebook, no matter what the reason would be. That's why the click-through rate for the advertisements is so embarrassingly poor: http://en.wikipedia.org/wiki/Facebook#Company
That said you can of course always do both: build a website and offer the same functionality through a facebook app. However my opinion here is that if you're application only offers its users a single functionality, you'll be better off just doing the latter.
What exactly is the advantage you expect by creating a Facebook-ONLY-App for that?
If it's only about taking tests you can still build a "normal" portal and include some of the Facebook-functionality through the JavaScript-SDK, like posting to the wall, Single-Sign-On, find your friends and so on. This way the user still has the choice if he wants to connect with Facebook or not. This way you also don't minimize your userbase to Facebook-users
(yeah I know, "everyone" has Facebook these days... ;) Still not everyone wants it to be connected to every single site he's using through Facebook)
Considering this comment:
Well I guess its easier for people to recommend my app if it is a facebook app, is the main reason I want to know if facebook is a good option – Zubair Mar 3 at 14:51
Build a website and then add the Facebook 'like' button. See: http://developers.facebook.com/docs/guides/web/#plugins
You should put a Twitter button as well:
http://twitter.com/about/resources/tweetbutton
In my opinion you have to develop both. First develop you website. Although facebook is having millions of users But in my opinion you cannot implement every thing as freely as you can in your web application than facebook application. You should have a website and a page on facebook. You can integrate other facebook social plugins on your website to interact with facebook.
From monitization point of it is easy for new users on website than application on facebook. Other reason website especially related to educational purposes have a huge click through rate which you cannot find on facebook application advertiser.
What is the goal of the website?
If its to make money dont do a facebook app, you have far more control of your site by designing it entirely yourself.
If you want social networking features there are plenty of APIs you can tie in to which will provide you with functionality and allow you to link into facebook / twitter etc.
A website would look more professional, it would allow you to gather statistics on unique hits, revisits etc, having your own database of users means you can gather information and market your site more specifically ( which users took which tests).
A website also allows you to monetize it by adding advertisement if that is your goal, and you can gain search engine rankings.
If you want to get publicity for your website you can use facebook by creating a group / page for the site and promoting it that way.
Also your own website wont leave you vulnerable to changes in Facebook, what if you put in all this work and in a year the terms change and a portion of your app is now in violation of the terms. What if you want to add X feature and facebook wont allow it?
Basically your site = 100% in your controll, thats a big advantage to you. With facebook you loose that advantage but maybe gain a little in being able to use more of their features. Personally id always go for my own site.
You should go for the website first, then add the social elements in the website.
Like you can enable users to login using there facebook credentials. Like/share Button.
And later on, you can also go for the facebook app, when you want to shoot for much much more traffic. Therefore, whenever you think that you have figured out what exactly you want out of your application then only go for it, otherwise try your options with website. Because once your facebook app is up, you will get hell lot of traffic.
Let me know if you need help in creating facebook application or social elements enabled website. I have built an Facebook Easy API on top of all facebook features, which will enable you to easily access anything on facebook and meanwhile reducing your work effort.
You first build it like web app and use Graph API and FBConnect to use Facebook functionalities. Then you need to create a facebook app version also because getting facebook traffic is also required. People from facebook most like come to facebook app then to another web.
You will not need to convert it to facebook app, it will be just less in width and it would be a facebook iframe app. as I some where read that facebook is depreciating fbml and iframe app is recommended.
So now you can make both things, as I think , test app can have flexible layout so that you don't need to change width for facebook iframe. So you can both things by doing one.
thanks
i'm pretty sure many people will not agre with me, but IMHO you should focus on build a good Web-App that work well also on Mobile-Phones. keep it simple, intuitive, responsive, lightweight, cross-browser and straight to the point.
if your only concern is about "recommend your app to other people" make it SEO and Multi-Language too. google will do the rest.
then if you want make your app bold, slowly and planty of useless stuffs start to add all the facebook widget you want.
PS: i'm also on facebook, twitter,
flickr, google etc etc, i'm also
sharing photos, links and usefull
stuffs, my google rss reader is full
of links with tons of nice things, well i
have never had a minute to look at it, when i need something i just start searching google
I agree with most of the answers here—a native website is the way to go. Personally, I don't trust/like FB apps. Dunno what they do, and given the number of scammers out there and FB's lack of responsibility (IMO), I rarely if ever use an FB app.
Creating the website gives users choice about whether they want to share results/integrate with their FB wall/profile. Users don't like to be forced into something.
And in the spirit of adventure that is typical of SO, it's always more fun to build your own website than to build a template-based (sort of), boring and nearly irrelevant (drowning in a sea of other poorly made apps) FB app. But that's just my 2¢
In your case, I would do a hybrid. First, build your website, but integrate it with Facebook via connect. This way you can concentrate on building your value added services and let Facebook worry about the community.
I would also not ignore the Facebook app. Now, with iframes being fully supported on Facebook, you can adapt your existing site to work within Facebook with minimal effort, as long as you keep this requirement in mind when building your original application.