Starter
For freelancers and small teams.
$ 24 /mo
Billed monthly · cancel anytime
Platforms3
Accounts10
Available metrics
Available dimensions
What our customers say about us.
After three years of use, Catchr has become essential for both our teams and our clients. So far, it has been our best solution for compiling and analyzing data from different advertising platforms. It’s easy to set up, and the customer service is responsive and excellent.
With Catchr’s automated API, we can finally collect and centralize all advertising data, connect it with booking information, and calculate the real ROAS for our restaurant clients. It gives them full visibility, more autonomy, and the ability to optimize campaigns to maximize ROI.
The solution is a real game changer, providing optimal time savings for our data reporting. The major strength of the solution is their highly responsive and professional support.
Connect Firebase Realtime Database in Catchr using your database URL and service account JSON credentials. Catchr discovers the first-level nodes in the database; select the node containing the records you want to report on. Then open the Catchr connector in Looker Studio, select that connection, and create your data source. Use a node organized as a collection of records with consistent fields.
No. This connector reads records from Firebase Realtime Database. Cloud Firestore is a separate database, and Firebase Analytics reports app measurement events. Google documents a Firebase Analytics connection through BigQuery. Choose the route that matches where your data is stored; an Analytics export does not automatically include your Realtime Database records.
You need the URL of your Realtime Database instance and a service account JSON key with access to that database. A Firebase web API key alone is not sufficient for this Catchr connection. Ask the person managing your Firebase project to provide the correct service account credentials, and enter them in the Catchr connection form rather than in report text or a shared spreadsheet.
Place comparable records under a first-level node, such as orders with one child record per order. Keep field names and value types consistent across those records. Catchr infers columns from a sample and flattens nested objects containing scalar values; arrays are not expanded into report columns. If each order contains a list of items, prepare a separate item-level collection when you need item-level charts.
Catchr discovers fields from a limited sample of records in the selected node. A field absent from that sample may not appear, and mixed value types can cause a field to be treated as text. Check that the selected node contains populated, similarly structured records and that numeric values use a consistent type. Arrays need to be reshaped into records or scalar fields before reporting.
The Realtime Database name describes how Firebase synchronizes application data. It does not mean the Catchr dashboard keeps a live subscription to every database change. Catchr reads database records when data is requested, while Looker Studio freshness settings and caching affect when charts show new values. Refresh the report when checking a recent change, allowing for the reporting cache.
You can report on historical records that your database still contains. The connector reads the current contents of the selected node; it does not reconstruct deleted records or earlier versions of overwritten values. Store dated events or snapshots when you need trends over time, and use an appropriate date field in your report. A current balance field by itself cannot show what the balance was last month.
Our team is always here to answer any questions you may have about our data connector.
