OpseerOpseer
Docs
Dashboard

Remote Config

View and manage Firebase Remote Config parameters from the Opseer dashboard.

Last updated: 2026-05-18

Remote Config lets you view and update your Firebase Remote Config parameters directly from Opseer. Change feature flags, A/B test values, and app behavior without deploying a new app version.

Prerequisites

  • Firebase integration connected (service account key)
  • Your app must implement the Firebase Remote Config SDK

Viewing parameters

Navigate to Firebase > Remote Config in the sidebar. You will see a list of all Remote Config parameters with their current default values, descriptions, and value types.

Editing parameters

1

Select a parameter

Click on any parameter to open the edit view.

2

Modify the value

Change the default value. The value type is preserved (string, number, boolean, JSON).

3

Publish

Click "Publish" to see a confirmation dialog showing the diff. Confirm to push the updated template to Firebase; your app clients receive the new values on their next fetch. Before publishing, you can revert your edits with "Discard".

Conflict detection (ETag)

Opseer uses Firebase's ETag mechanism to prevent conflicting updates. When you load the Remote Config template, Opseer stores the current ETag. When you publish changes:

  1. Opseer sends the stored ETag with the publish request
  2. If the template was modified elsewhere (Firebase Console, another team member) since you loaded it, the ETag will not match
  3. Firebase rejects the update with a conflict error
  4. Opseer notifies you of the conflict — reload the page to fetch the latest template before trying again

ETag conflict detection ensures that you never accidentally overwrite changes made by someone else. Always review the latest values after a conflict before publishing again.

Permissions

Remote Config access is controlled by two permissions:

  • remote_config:read — View parameters (granted by default to Member and above when Firebase is connected)
  • remote_config:write — Edit and publish parameters (Owner and Admin only by default)

Best practices

  • Use descriptive parameter names that match your app code
  • Add descriptions to parameters so team members understand their purpose
  • Test changes on a staging Firebase project before publishing to production
  • Use conditional values in Firebase Console for A/B tests, then verify results in Opseer