Upholding Graph API contingent (limit) when using only the app ID - facebook

Facebook tells me that the the contingent for API calls for a certain App ID is raised when a user logs into facebook using my app.
It says that the algorithm for detecting the current limit per time is like
users (logged in?) the day before x new logins today x n
My question is: Does this only take into account new logins so that logins that occured 2 days before day x would not longer uphold my API call limit on day x+2? Or does it consider all users that ever logged in using my app?
My app only uses a facebook login once (at the beginning for law protocolling reasons) but then no more and I had to change that if user logins are counted on a 2-day basis.

Related

Facebook pixel + server "matching"

I want to do something that I thought would be very simple, but Facebook's docs are beyond confusing to me.
A user (that is known to our servers) visits my site, and our Facebook pixel fires a simple page view event. Lets say the user has a UID of 1234 on our server
Sometime later we use the facebook marketing api to send this information to Facebook: "User 1234 has made 9 purchases, totaling $1,500. Their most recent purchase was on January 12th, 2018"
My question is, can we somehow add this UID to the pixel event so that it can be used later in our api call?

Facebook Rate Limit, what counts as an active user?

I have a website that makes a call to Facebook to see how many times certain links have been shared but i'm wondering about the Rate Limit. I'm trying to estimate the rate limit my site has, according to the official documentation the rate limit is calculated like this:
The number of users for your app is calculated as the average number
of daily active users plus today's new logins as an estimated value.
Apps with a larger number of users may have more accurate rate
limiting than apps with a smaller number of users. Apps with a very
small number of users may have rate limit issues.
But what counts as an active user? everyone that makes a call to the API through my site/app? everyone that visits the site/app and is logged in to Facebook?
Active Users are users who are interacting with your APP (what means that they are making some kind of API calls) It doesn't matter if they are logged into FB when they are using an active access token.

How does Facebook API Rate Limit work for App Access Token?

I'm working on a project where an app displays events in the near surrounding based on the personal preferences of the user. We plan on getting the events from the Facebook Graph API using this approach. Due to Facebook's API changes it is much more complicated to search for events in a particular city. Therefore it requires much more API calls than before and i'm worried about FB rate limit.
We want to get the information about events by calling the Graph API with our app access token from our server and then store the data temporarily in our own database. So every time a user searches for events in our app, the client gets the information from our database. Moreover the user can (but don't has to) log-in with his Facebook account in order to provide us more information about him. We want to use the user's access token to call the API in order to get the user's likes.
I've read the FB documentation about the rate limits and some posts here on the site. Apparently FB calculates the number of calls based on the active users (200 calls per user every hour). It says that
"These limits apply to calls made using any access token other than a
page access token"
ergo they also apply to the app access token. Additionally in the FB policy it says something about 100M calls per day.
So my questions are:
How does the rate limit work on a per user basis if I am using my App Access Token?
To what token does the "100M" number belong? Is it an overall number for all tokens used by the app?
A similiar question has been posted here some time ago but didn't receive any answers. I hope maybe someone got new information since then. An answer to these questions is crucial to our project, so bear with me if you've read that question before.
Thanks in advance!
Please check this
Facebook Rate Limits

Facebook graph limit

I have been reading through the Facebook Doc's about limits of requests to their graph api (https://developers.facebook.com/docs/graph-api/advanced/rate-limiting). It states there are 200 calls allowed per user per hour ( e.g If app has 10 users Facebook allows 10x200 = 2000 calls to the api per hour).
Facebook states:
Rate limiting is done on your Facebook AppId. If your app reaches a
rate limit, all calls made for that app will be limited not just on a
per-user basis.
So I have a concern that one malicious user can use up all 2000 calls in an hour and my app would be down since users can't make calls anymore. Is there a way to stop a user from making so many calls?
How would one user who can only do 200 API calls in an hour concern you? Because as you can read in the docs, it is 200 API calls per user. That does not mean that one user can use 2000 calls just because there are 10 users in the App. And i am sure that Facebook will not punish any App just because one single user gets to the limit all the time. That would allow a competitor to just stop your App from working instantly, all the time.

Get Facebook User Profile ID instead of App-Scoped user id in Facebook Graph API

I have 6 different applications on FB which have one database with users. All of them was created long time ago, on V1.0 and I have several hundred thousands registered users. People are buying daily tickets for those games, and tickets are valid for any of games. And that works just fine.
But since V2.0 for each application I'm getting different app_scoped user ID which are different to original ID in database, so I'm getting all of them as a new users every time they change the game so purchased ticket (which is app for registering) will not be available for user in any of app caused by totally different ID's... Note that many of them don't want to leave email, so email cannot be used as parameter for user identification.
I have read about finding original user ID with API V2.x calls, but still I'm unsuccessful. Any idea of getting real user ID with V2.x API calls?
Thanks in advance!
You canĀ“t get the real IDs in new Apps anymore, it would make the whole concept of App Scoped IDs void. But you can map the IDs of different Apps with the Business Mapping API: https://developers.facebook.com/docs/apps/for-business