Clarification Required: Do internal Firebase Performance Monitoring fetches impact the new Remote Config billing quotas?

[lklong1551019]

I am writing to ask for a clarification regarding the new usage-based pricing for Firebase Remote Config that went into effect on September 1, 2026 (https://firebase.google.com/docs/remote-config/pricing).

My mobile application handles a large user base (approximately 80 million users), making quota management critical for our budget.

We currently use Firebase Performance Monitoring. I understand that the Performance Monitoring SDK automatically makes background network calls (such as evaluating the perf_disable flag or fetching dynamic trace sampling rates) using the underlying Remote Config infrastructure. Could you please clarify the following:

1. Do the internal automated fetch requests triggered by the Firebase Performance Monitoring SDK count toward our project's daily 100,000 free Remote Config fetch request quota?
2. Will our project incur Blaze/Spark plan charges ($0.06 per 10k requests) for these internal system fetches if our total volume exceeds 100,000 requests per day solely due to Performance Monitoring traffic?
3. Does the usage-based pricing strictly apply to custom Remote Config fetches initiated explicitly by our own client application code?

Having a clear statement on whether internal SDK layers bypass developer-facing Remote Config billing quotas will help us properly manage our implementation.

Thanks for your time and help,

Best regards,
Long

[siddhantjn-cmd]

Hi @lklong1551019 - Thank you for reaching out!

I can confirm that FirePerf driven fetches will not be counted towards daily free fetch quota and billed fetches for Remote Config pricing. These will be exempt for the purposes of Remote Config pricing calculation. We have updated the public pricing documentation page with this clarification:
https://firebase.google.com/docs/remote-config/pricing

Please let me know if this doesn't resolve your concern or if you have any other feedback for us!