How to verify if post is shared on facebook - facebook

I have an URL and it has many features. I want to disable one feature and enable it only if the app is shared on facebook. I have implemented share button, only problem is i will not know if the app is really shared on facebook or not. Users can click on share button and in the popup cancel it and the feature gets enabled as of now.
Kindly let me know if detection is possible via facebook javascript code.

Only incentivize a person to log into your app, enter a promotion on your app’s Page, or check-in at a place. Don’t incentivize other actions.
Source: https://developers.facebook.com/policy/
Share Gating is not allowed, users MUST share/like/comment something only because they really want to, you are not allowed to reward them in any way or gate content behind those actions.
Afaik the only way to implement this is to authorize the user with publish_actions, in that case you will get the post id in the callback. But you will never get publish_actions approved for something that is not allowed, obviously.

Related

How Do I Share to Facebook With Custom Text

I have a task to add links to a web page to enable the user to post a short message to Facebook. There may be multiple messages on the page, each with its own link. The intent is to launch a Facebook share dialog pre-populated with the text of the message which the user can then modify, accept and/or reject.
I'm pretty new to programming anything for Facebook. I'm fairly confused and am not sure what to ask first, so I'll go with a very basic question: what's the simplest way to do this? I gather from Facebook's documentation that I probably have to use the Javascript SDK and/or the Open Graph technology. Is this correct, or is there another option I'm missing? Is there a really clear example of this kind of solution anywhere?
Thanks!
You have to create a facebook app first so you have your app_id and app_secret.
After that you need to request permissions to the user to publish_actions. If the user accepts, you'll receive a token (you need to store it in db). If you need to publish actions in a user page instead of his own page, you also need the manage_pages permission.
You need to read the facebook graph api documentation to understand how all this works.
The access token you receive expires after certain time. So, when you receive it, you can ask for a long lived token. The page tokens doesn't expire.
Facebook evaluates your app before approving it to be in production. They ask a couple of questions about how you'll use the user's token and data. You might have to put pictures of the flow too.
As far as I know, Facebook won't allow you to send pre populated messages to the user's wall. They user has to write it.
Hope it helped a bit!

How to verify whether content is shared on Facebook or not?

I was given a requirement where the user of a site shares content on Facebook and gets a coupon in return. This doesn't seem technically possible at the moment as content is shared through the share button. Is there a way I could detect if some content has been shared on Facebook or at least whether someone has clicked on it?
The user will design the interior of room and the designed image will be shared on Facebook and in return he'll get the coupon code sent to his email.
Is it possible?
https://developers.facebook.com/docs/sharing/reference/share-dialog
This one will only return an object id if the user is authorized with publish_actions, else you don´t know if something is shared. The Share Button plugin can´t be used for that either.
The major problem is that it is not allowed though. You can´t incentivize likes and shares - meaning, you are not allowed to reward a user with a coupon for sharing something. You may want to check out the platform policy: https://developers.facebook.com/policy/
Remember, users need to like something because they really "like" it, and share something because they really WANT to share it.

If Facebook Feed dialog is deprecated, how are you to share posts on Facebook?

I have been working on a Facebook app for some time, and we are having trouble getting the app approved. I feel like Facebook's app approval process is a constantly moving target and their explanations are provide the least amount of detail possible, leaving the door open for further rejections.
We are using a Facebook app to provide sharing functionality for products that are behind a paywall. All of our share buttons are custom, so they fit in our designs (we don't want to use the out of the box buttons). We first built the app attempting to use the recommended share dialog with open graph actions and stories. The problem here is that you can only use the share dialog with a shared link. Facebook reads any open graph tags on the page to provide sharing information, but because there are many different "products" on a given page, we can't use open graph tags. Because of our environment, we couldn't use the actions or stories. Furthermore, we'd like to customize that share information, so using share dialog is not an option.
Unfortunately, we had left our open graph stories and actions in our app when we first attempted approval. In our first denial, Facebook told us that we had implemented our open graph actions and stories incorrectly. We were not using the share dialog, but the 'feed' method, which is deprecated in 2.0 but still works. Thinking that Facebook looked at our app and noticed we were not using those actions correctly, we figured if we removed those stories and actions from the app, Facebook would see our share method worked and approve us. Wrong.
We had built the share using the publish_actions permission, along with FB.login() and FB.ui(). Facebook denied us because our app did not need publish_actions. They recommended we use the share dialog which did not need login or permissions.
We removed the publish_actions permission and FB.login(). When we tested this, you could still login to Facebook and perform the share WITHOUT fb.login(). So we thought it was good to go. It was not; Facebook told us we needed to implement login(), even thought the docs say you don't need it.
Now we have reimplemented login() and are going to try to get it approved again, but I have a feeling it's going to get rejected due to the 'feed' method being deprecated.
So my questions are:
A) If you have a website providing a paid service, how do you allow your users to post to their feeds, using the newer share method, with data you'd like? Eg: "I just completed the Get Moving III workout at teamexos.com!" The post would contain no pics or links. If it had to, a link to teamexos.com would be ok.
B) How do paid sites provide open graph actions and stories? Do they have public links to their products? Do those products have their own individual pages, with their own open graph tags?
First of all, the feed dialog is not deprecated, at least not anymore. You do not need to get anything approved for it, and you certainly don´t need login: https://developers.facebook.com/docs/sharing/reference/feed-dialog/
But: Your example looks like an Open Graph story, you should consider taking a look at those: https://developers.facebook.com/docs/sharing/opengraph

Facebook App Policy : incentivizes users to use Facebook social channels

This may be a controversial topic.
I have an app that just banned by Facebook, which is reported that the app violates Facebook App Policy (VI. 1)
Your app gates content behind or incentivizes users to use Facebook
social channels. (FPP IV.1)
Here is the Facebook App Flow:
Click "Page Tab App" icon
Enter the landing page, check whether the user installs the App or not; If not installed, install the App
Enter the checking page, check whether the user likes a Fans page, share to wall & send friend requests; If not, the user will not allow to go to next step.
Next page is a questionnaire; user has to complete the questionnaire to go to next step
Last page is a Thank You page
The whole idea is, the user has to complete the flow to enter a lucky draw (prize will be given to winners).
My question is, how to avoid violating the rule?
It's pretty straight forward...
You are telling the user that he must like a page, share to his wall and invite his friends, all of those are social channels which you "force" the user to go through in order to use your app.
You can ask your users to like your page, you can ask them to invite their friends (or better yet offer them a better experience when their friends join), but you can not (and that's the policy violation) incentivize them to do so by saying "do that or don't use the app"

Problem with like it button and public permissions

I'm a web developer and i'm having problems using the "like it" button
I put the buttom on my site as a counter of votes of a special contest. People can only click the like buttom if they are fan of my Facebook page.
The problem is that people can't vote if they haven't public permissions on his facebook, cause i can't know if they are or not fans of my page.
Is there a solution?
if you rely on information that you are not certain that you can obtain then sadly there is no solution.
Since what you are doing is beyond a simple like button What you may want to try is open a facebook application and request from your users the user_likes permission. You can read more about it here. I have photo albums on the "highest privacy setting" - only me. Yet when I request a list of my photo albums through one of my applications (with the required permissions of course) I get back ALL of my albums.. This might have been a temporary issue that was solved - but in any case - I saw this behavior and I thought it might be relevant to this post :)
Additionally you should look at the Promotions Guidelines specifically this point :
You must not use Facebook features or functionality as a promotion’s registration or entry mechanism. For example, the act of liking a Page or checking in to a Place cannot automatically register or enter a promotion participant.
I had some problems with facebook on this issue - you are not allowed to require someone to "like" a page in order to participate in an activity that is not directly connected to that page.
From what I understand you are requireing people to like your page on facebook beofore voting on your site... If this IS the case then facebook might very well start taking action and closing your page/app.