I've been setting up the Instagram business api access and have for the past few days been setting up the webhook for story insights. When I went to go run a test today the section is no longer in my webhook dropdown. The only thing that has changed since yesterday is that we added the Marketing Api.
After doing a bit more research it looks like this is a known issue though it isn't included in the depreciation changelogs. Facebook says they are looking into it https://developers.facebook.com/bugs/553848658320920/.
Related
I'm trying to create a Facebook App Install campaign. When I create the ad itself, it wont let me specify my Branch link as the deep link. I've used Branch links in other App Install campaigns, so not sure why it's failing now.
Not Working: http://fight.offtherecord.com/YUQk/RATIxDZQZw
Working: http://fight.offtherecord.com/YUQk/Frqjtf6gww
Alex from Branch.io here: this is a known issue with Branch links in Facebook ads that comes up sometimes, and we're not even quite sure why or when. There are several workarounds you can try, detailed on this page.
To summarize, rescraping sometimes fixes the issue. This may also indicate that your Branch configuration is missing some required data. As a last resort, you can feed the Branch deep link ID directly into your ad to make sure deep linked behavior still works.
We'd like to use the Facebook Continued Flow Lead Ads API. Integrating it into our website was quite easy. The Continued Flow Test Tool was helpful.
The last step missing is how to integrate our endpoint - the Follow Up URL - in campaigns.
In the Facebook Continued Flow Lead Ads API, the documentation says that
This feature is available by whitelist only.
Since Facebook's support doesn't provide this information, maybe someone over here can help me?
How does one get whitelisted?
As far as I know you have to go through an internal process with a FB account manager or one of the technical managers of the Lead Ads project to get your ad account whitelisted for continued flow use. I checked if this might be exposed on the FB App Review process but it's not yet, so I recommend contacting your account manager if you have one or otherwise trying to go through FB support.
in order to be whitelisted you need to have:
Managed account
$50K+ monthly spent
You can apply through this link which is available publicly - https://www.facebook.com/business/standardadsapi
For the last three days, 3 different submissions, I have not been able to pass Facebooks review process. The only feedback I am given is:
I clicked around to see if I could find more details, but there aren't any; as far as I can tell, that's it. At this point I have submitted a support ticket, but thought I'd check in here on SO to see if any others have experienced this vague response.
UPDATE - 2015-05-251
After waiting over the weekend to see if fb would answer my direct support ticket (which I submitted thursday or friday of last week) I came to find that this ticket has just vanished; as if I never submitted it. I know it was there, I was watching it over the weekend. I tried to check it around noon (PST) today and it was gone.
Without any further indication from fb what we're doing wrong, I tried again to submit a review request. I made a few changes to screenshot instructions, added some new information about contacting us if something is wrong (i.e., phone number), and added a few more pieces of information about the publish process. Hoping to hear back from them tomorrow (Tuesday) if not sooner.
UPDATE - 2015-05-25[2]
I got a response from one of the support members on the FB dev page pointing out that there is a good chance that I was not viewing 'all' tickets on my fb dev support page. He was right. I found the support ticket there with someone from fb offering to help me get things straightened out tomorrow (Tuesday). Will update here once I get more information.
Jimmy (I answered your post on the Developer's group). I found this:
"My app was rejected for 'General Issues'. What does this mean?
The App Review process involves loading your app on each supported platform, logging in with Facebook, and using every Facebook integration that you're requesting in review. This often results in what we call 'general issues.' These are errors or bugs relating to loading your app, logging into your app or the general functionality of your app. This means we weren't able to test the permissions you request in your submission.
Since these are issues that prevent us from reviewing your Facebook functionality, we can't comment in detail about how your app uses the Facebook functionality you've submitted for review. Because of this, we reject with 'General Issues' and provide feedback about this on each platform.
If you receive a 'General Issues' rejection, please carefully read all of the feedback. Each platform will receive individual feedback that should explain what issues were experienced in review."
https://developers.facebook.com/docs/facebook-login/review/faqs#scores_achievements
After my final update above (posted on 5/25/2015) I was later informed by the individual assigned to my support ticket that Facebook had a bug in their system that was preventing my submission from being approved. After waiting it out (about 2 days) they got the bug fixed on their end and this morning my submission was fully approved.
The best solution I can think of is: If you've triple-checked and tested your code and you are still failing the review process and getting no explanation as to why - check in with Facebook support either by submitting a ticket (if you have that option) or by reaching out on their Facebook Dev page. It's a closed group but they don't seem strict in any sense about who they approve to join. FB devs moderate the group, so posting your situation along with your App ID seems very helpful.
Thanks to everyone who chimed in on this one, here and on the fb dev page.
Here is the notification I just received:
App, is currently using the following deprecated features:
Non-threaded comments. Please see the developer roadmap for more details about this change.
I looked all over the API and the developer roadmap and the settings but found no way to fix this issue. How do I fix this?
My hunch would be that they send out alerts based on the permissions your app uses - my app doesn't interact with any "comments" connections in the graph, but it does have the "publish_stream" and "manage_pages" permissions.
If someone knows otherwise please advise...
I have received the same notification for one of my apps. My app definitely does not read or create comments on Facebook posts or objects (Facebook rolled out the threaded comments Feature in April). Thus Facebook's message is not relevant to every app they send it to.
The change should only affect apps which read or publish comments.
Here is the link to the API documentation about comments:
http://developers.facebook.com/docs/reference/api/Comment/
Look at the settings page, in the "Migrations" section. Enable "July 2013 Breaking Changes" and your notification should have a green sign notifying: Your app, appname, is now compliant with the July 2013 Breaking Changes migration. No further action is required.
Be sure to read the complete roadmap at https://developers.facebook.com/roadmap/.
I have got the following message too:
MyApp, is currently using the following deprecated features:
The 'page_id' field in the checkin FQL table. Please use 'target_id' instead.
The 'version' field in the group FQL Table and on the Graph API.
Non-threaded comments. Please see the developer roadmap for more details about this change.
I am sure that in my case the warning derives from my Graph API Explorer and
my Django test code.
That means that Facebook logs every request sent by your App and send you a warning even if you used deprecated features only once.
Check it out
I have created a Facebook application that I don't want to use anymore. I deleted it from my developer account and from the related Facebook page more than a week ago but it still appears in the Facebook search engine.
I know similar questions have been posted, but I have no longer access to the admin of this application, meaning I can't change the user accessibility of the app.
How can I avoid this?
Sounds like a bug by Facebook. You might want to post a bug report here. A solution which might help next time: Switch on the sandbox mode, then delete the app.