There are readme files that should help explain what is all happening and the different features. Let me know if anything is confusing or hard to decipher.

To stay within free usage, we are going to save data to Cloud Storage and load those files into BigQuery instead of streaming data directly into BigQuery. Because of this, there are 2 different Cloud Functions that will be utilized.

As an overview, these are the steps that will be taken:

Cloud Function (HTTP): Receive JSON data from plugin. Save as JSON line-delimited file in Cloud Storage.
Cloud Storage: Bucket will temporarily hold generated data file.
Cloud Function (Storage trigger): Function is triggered when a new file is uploaded to storage bucket. Meta data will be read to know what table to load the data into, and the file will be loaded into BigQuery.
BigQuery: Holds data ready for reporting. Easy to connect to various visualization tools

Let me know if that's helpful. I could share the javascript code that I use for the functions, but I would have to remove some proprietary logic that I added to mine to support some other specific business needs.

The plugin breaks out the data into tables for contacts, contact activity, groups, and group activity.

If you have a different data storage behind your Power BI that's not GCP, you can either do a similar cloud function approach (the plugin has built-in support for sending data to a webhook URL for you to process however you need) or we could look at another data provider integration.

We have 2 metrics related plugins.
https://disciple.tools/plugins/metrics-export/
and https://disciple.tools/plugins/data-reporting/

I think https://disciple.tools/plugins/data-reporting/ is the one we'll want. I've forwarded your question and waiting to hear back with confirmation.