Firebase Remote Config (google/firebaseremoteconfig
)
operated by: Google LLC
(get company information on datarequests.org)The Firebase Remote Config service lets developers remotely change the functionality and appearance of their apps without having to publish an app update.
Developers can use user segmentation and return different configuration to different users based on app version, language, Google Analytics audience, and imported segment. They can also “[use] machine learning to continuously tailor individual user experience to optimize for goals like user engagement, ad clicks, and revenue—or any custom event [they] can measure with Google Analytics”. Finally, they can use A/B testing.
Endpoint URLs
These are URLs or regexes of endpoints the tracker sends data to. We use these to determine which adapter to apply to a request. Some trackers use the same endpoint for several formats. In this case we use additional logic to match the adapter to the request, refer to the code for more information./^https:\/\/firebaseremoteconfig\.googleapis\.com\/v1\/projects\/.+\/namespaces\/firebase:fetch$/
Decoding steps
Every tracking library has its own way of transmitting tracking data, often even several. They are regularly pretty convoluted, nested encoding schemes. Because of that, the adapter needs to decode the request information into a consistent format. We try to keep keys and paths intact, but the structure results from our decoding. All steps used in the decoding for this adapter are documented here.- Parse the request body as JSON. Store that in the result for the request body.
- Get the property at JSONPath
$
in the request headers. Store that in the result for the request headers.
1res.body = parseJson(body)
2res.header = header.$