I was wondering if anyone can clarify a Firebase Authentication API limit for me as I am a little confused.
I am developing a website that is storing the user registrations (email/password login details) in the Firebase Authentication so I don't have to store them in my local db.
I can see from their documentation that on the "Spark Plan" (free plan) I can have 49,999 Monthly Active Users and then any extra is charged. This is fine. Registered User Accounts is unlimited. This is fine. I am only using Firebase Authentication and it is purely Email/Password login - no email verifications, no SMS etc just pure Email/Password login.
What I don't understand is the following on their website:
Instrumentless Limit:
Tier 1 Daily Active Users | 3000 per day
What exactly does the above mean/restrict? Can only 3000 users login per day?
Their pricing calculator doesn't mention this, it only asks about Monthly Active Users, to which I enter say 30,000 and it calculates $0.00 monthly charge. But I don't want to go to far to be then restricted that my 30,000 Monthly Users can only allow 3000 of them per day to login.
A little confused. Hoping someone who know this stuff can advise.
Many thanks for your time.
Ro
I think I worked out my confusion if this helps anyone else with the same confusion. I just wasn't reading the docs correctly.
Firebase Authentication now has the Identity Platform (Google).
If you stick with the "Spark Plan" (100% free) then you get a new restriction of 3000 Daily Active User logins.
If you upgrade to the "Blaze Plan" (Pay as You Go) then you get 49,999 free Monthly Active Users (a single user can login in as many times as they want in a month and that is classed as 1 Monthly Active User) and after 49,999 then you pay per user.
So, Identity Platform for the Spark Plan is Daily Active User limits (3000) and Blaze Plan is Monthly Active Users (49,999) - for free.
Hope this helps anyone else.
Related
I want to use firebase for backend as a service for my college project.
Docs are well elaborated but I have doubt in understanding what is the meaning of 10,000 phone auth per month. If one user login multiple times in a month is it considered as 1 auth or the number of times the user login.
Also, what is the limit of email authentications?
If I use sign-in with google or facebook is that is going to be counted in email authentication?
For Firebase Authentication's phone provider it is common that the user only signs in once, and not each time they start the app.
There is no documented limit on email authentication calls, although there is (undocumented) abuse protection.
we are using a iam.gserviceaccount.com Email adresss to connect our tool with the Google Analytics accounts from our clients.
We have reached the maximum connected accounts, but an upgrade is not possible because we can't response to the emails sent by analytics support.
Is there another way to upgrade it? Or is there another possibility to connect our tool with the analytics API?
We already tried to upgrade the account with the analytics support, but it is not working because of the emailadress.
For normal Google analytics accounts there is a limit to 100 accounts that you can have access to. If you upgraded to a premium account if i remember correctly that number jumps to 250.
You are currently using a service account and granting it access to a number of Google analytics accounts. The service account is going to be bound by the normal user limit of 100 and your not going to be able to increase that.
The problem is that you are using service accounts in correctly. Your not supposed to be giving the service account out to your customers and asking them to add it as a user on their Google analytics account. Service accounts are intended to be used by developers and companies that have access to data and want to share that data with others.
You should be using Oauth2 to gain access to the users data and saving the refresh token in your application which will enable you to request data for the user when ever needed.
By using a service account you are going to be hit with a lot of quota limits because they are shared by the user a user can only make so many requests so fast per day. By using Oauth2 you would be using different users and would not have as many issues with the user based quotas.
I'm currently working on a WordPress website,
The Website broker between two users :
The first user wants service and paid for this.
The second user provides this service then takes money.
The Website broker between users and takes a percentage of this
money.
But stopped when I met a problem and can't find a solution,
I can easily deduct from the visa held by first user but do not know how to pay cash for the second user?!
Is there any way to transfer money to the second user, are easy and online because it will be almost daily ??
I am developing an addon for Shopify platform and using the Shopify NET library I have managed to authorize the user shop and gather some data.
Now I need to charge the usage of the Addon with a monthly fee (providing 7 days trial) but I cannot figure out the flow I must follow.
I guess that I have to call Recurring Application Charge API after the user authenticates (at the callback from the authorization URL) and if the user declines the charge then I have to log him out. Is that correct?
Do I have to care for providing 7 days trial by myself or the Shopify RACharge API with manage it by itself?
What do I have to do when the user cancel the subscription or freeze it?
Can anyone point me out a document that analyze the charging flow except the Shopify Billing API which is not that helpful after all?
First question, you're right. You either have to log out the user or you just let him authed without permission to see some views or all of them.
There's a propperty on Recurring Application which allows you to define the days of the trial: "Number of days that the customer is eligible for a free trial.", so Shopify handles this for you.
When user cancels a subscription or his store is put on "frozen" status, you should make sure he doesn't have access to your App functionalities, though if it's frozen, he won't even be able to log into his store.
We're actively developing our PMD ads management tool. We have a number of customers who want to advertise but don't have a Facebook account of any kind. I have a two part question:
(1) Is their an API/programmatic way for us to create a proper user account for our client so the client can in turn log in to their fresh Facebook account and enter ads payment information? For example, I can imagine an open graph call like this:
createFBUserAccount(f_name:"Joe",l_name:"Smith",email:"joesmith#gmail.com",isbusiness:"false");
or for a person
createFBUserAccount(business_entity_name:"ACME Corp",email:"contact#acmecorp.com",isbusiness:"true");
(2) For users who don't want a Facebook account but still want to advertise on Facebook through us, what is the proper way to create their ads? Let's say this is a business interested in buying External Website ads (or Mobile App Install, or any number of other ad units).
we currently don't have a way to create Ad Accounts through API. The user will have to create an account directly through https://www.facebook.com/advertising.
We also have business accounts (doc: https://www.facebook.com/help/131976240210052)
We require either a user account or business account to advertise with us.
Hope this is helpful.