Reject Open Graph Action Review with explicitly shared - facebook

we have submitted for approval three actions (2 custom and 1 common, watch) on Facebook Open Graph, this is the text that we have write in the review instruction:
The action Add and Watch are published only if user has activated the automatic
sharing inside his profile settings. Those actions use explicitly sharing only
and if only if the corresponded switch is on.
In order to use Share action, user have to touch the rounded Facebook button
at the bottom of the episode page or the series page, then he can write a comment
and only by touching send the action is published. The control is inside user's
hands, and it is obvious that the sharing is explicit.
we have also insert this image along with other images, that show that a user have to enable explicitly the options to make a explicitly share:
and one action need that the user touch a sharing button to be shared.
But Facebook have reject all the action, and have answered this:
we doesn't know how make it, and we need that this actions are explicitly because the user ask it to us. Anyone can help?

It's the explicit option in your settings that's causing Facebook to reject your story. Explicit shares have to be explicitly shared by the user each time (hence the name), so by having an automatic explicit share option that shares the story without the user choosing to share it each time, you're breaking the rules. That's a really complicated sentence... Basically, the user has to choose to share a post every single time for it to be explicit. If it posts automatically without any interaction from the user, then it's implicit.
So your "share" instructions, with the user hitting a share button, is the correct usage. Add and Watch are not.

Related

Custom Dynamic Links in Firebase that goes to user profile

Im pretty new to Firebase, so please bear with me on this one. This problem has been stuck in my head for the past days.
I have seen some videos on Dynamic Links, but i havent seen some clear answers to what im hoping to achieve. I want to create a Dynamic Link, that allow users to share their account with their friends (through a link).
So my question is how can i manually construct a dynamic link (with User A´s uid), so when User B clicks on that link (and has the app) it will go straight into the profile of User A?
Should i create a link when a user signs up and store it under their profile in the database?
Looking forward to hearing how you guys would go about solving this problem im having.
You essentially want to create link where the link parameter (what's called the "Deep link URL" in the Firebase console) looks something like https://www.example.com/userProfile?uid=314159. (The full deep link will look different than this.)
When your app opens up this dynamic link, it will convert the incoming URL to a Dynamic Link object, and that object will have a url property that equals this link parameter. Your app will have to do the work to analyze this url and say, "Oh, this appears to be a request to view a user's profile, so I'm going to redirect to that part of my app". It won't happen automatically.
Whether you create it when the user first signs up, or when they decide to share their profile is kinda up to you. I'm generally not a fan of pre-generating deep links ahead of time, because you might realize later you want to change an aspect of these links, and that's easier to do if you don't have thousands of pre-generated DLs. Keep in mind that either way, there is a network call required to convert these longer URls into a prettier short URL.

Mention tagging gets mistaken for action tagging

While trying to submit an OpenGraph action to Facebook, the feedback we receive states that we should use mention tagging instead of action tagging:
The Action Tagging additional property can only be used when the tagged user is also performing the real action. Otherwise use the Mention Tagging additional property to include another user in the story.
But in our instructions on how to reproduce the action, we clearly state we implement "mention tagging", and as far as I can tell, the app complies with the requirements as listed in the documentation.
What could cause FB to believe we use action tagging instead of mention tagging?
Is there a way to receive more specific information on the failed submission?
I had the same problem and it was a pain in the backside for weeks as I kept resubmitting my open graph action for approval and it was continually rejected. My solution was to:
a) update the description to ensure that I made it clear that the app was using mention tagging rather than action tagging.
b) I used a timeline screenshot that clearly showed the words "FB friend" was mentioned in your profile (where "FB friend" is the name of the friend you have chosen for the mention tag).
As Facebook doesn't actually review and approve the iOS app, its reviewers can only go on the description and screenshots you provide. So, if it's not getting through, you need to make it absolutely clear in idiot-proof steps, exactly what your app does. If you continue to get rejections, ask the reviewers for help within the submission text - sometimes that gets a better response that will help direct you!

Rejected Facebook Built-in Like Action

I'm trying to submitting built-in like action.
First time, I used a button on my site labeled with 'like' and without any logo and linked it to the action, but I've got the following feedback:
Your Like or Recommend button branding conflicts with Section 5.6 of
the Facebook Terms and Section I.8 of the Platform Policy
(https://developers.facebook.com/docs/guides/policy/examples_and_explanations/branding/).
Please resubmit with a different graphic that reflects your own
branding and the ux of your site.
Then I change the button text to 'Useful?', but I've go the following feedback:
Your action conflicts with section IV.3 of the Platform Policies
(https://developers.facebook.com/policy/). You must make it clear to
the user that you will be publishing a story to facebook and get their
permission before actually publishing the story. Additionally, your
action must not be confusing or misleading and should accurately
represent the action the user took within your app.
This confusing, I'm not sure what the problem is, please help :)
Thank you in advance.
It's all explained near the bottom of the the Facebook branding page. On your first attempt you used 'like' and that is not allowed on your custom button. The second time you used 'Useful?' and that is not clear enough and is confusing.
I suggest you read the branding policy examples and the other material.
Section 5.6 of the Facebook Terms
You will not use our copyrights or trademarks (including Facebook, the Facebook and F Logos, FB, Face, Poke, Book and Wall), or any confusingly similar marks, except as expressly permitted by our Brand Usage Guidelines or with our prior written permission.
Section I.8 of the Platform Policy
You must not use or make derivative use of Facebook icons, or use terms for Facebook features and functionality, if such use could confuse users into thinking that the reference is to Facebook features or functionality.
Section IV.3
If a user grants you a publishing permission, actions you take on the user's behalf must be expected by the user and consistent with the user's actions within your app.

How to share in Google+ without opening share dialog

I am going to develop an extention to share a selected part of page just by clicking on a share image that shown in page..How can I share a text or image in google plus without opening share dialog?
Is there any way?
The only way to share on Google+ is through the share dialog.
Google has stated that they want shares to be deliberate actions - they don't want to allow web pages or other systems to be able to post anything "on your behalf" without the user taking a specific affirmative action.
In short, they don't want Facebook's "frictionless sharing".
They are beginning to roll out the ability for websites to automatically post "moments" into a history vault, but users will still need to take a specific action for these moments to be posted to their stream. See https://developers.google.com/+/history/ for more information and the developer preview.

It is possible to define a large amount of specific open graph actions?

it is possible and/or useful du define a big amount of specific Actions in a Facebook Application?
e.g.
First way, generic action: do
User A does "cooking italien spaghetti" on my App
User A does "baking a cookie" on my App
So I define the specific part over my object-title.
Second way, specific actions:
User A is cooking "italien spaghetti" on my App
User A is baking "cookies" on my App
All Actions has to be approved by Facebook.
The user could have a more interesting interaction with the graph.
The maintenance-level would be higher.
Any opinion or experience?
Thanks :)
Always do option 2. We will never approve actions that have objects embedded in them.

Categories