Skip to content

Using Data Marts from OWOX Extension

You already use the OWOX Reports Google Sheets Extension. You have Data Marts defined with SQL queries — running within your BigQuery project and sending data to Google Sheets. While this is a powerful way to handle ad-hoc reporting, you can do more with OWOX Data Marts while keeping your current setups fully functional:

  • get reusable Insights defined by SQL with AI assistance
  • unlock new delivery destinations like Looker Studio, Email, Slack, MS Teams or Google Chat for your data
  • simplify access and scheduling management at the organizational level—all
  • gain full visibility into run history.

💡 OWOX Data Marts detects your existing Extension Data Marts and automatically creates a system storage named after your GCP project ID. The storage type is “Google BigQuery (used in OWOX extension)”. This system storage cannot be added, edited, or deleted manually.

Take your Data Marts to the next level by completing these quick steps 👇

Follow the steps below to complete the setup:

  1. Select a storage
  2. Grant access to Google BigQuery
  3. Publish your Data Marts

In OWOX Data Marts, go to Storages. Find the entry labeled Google BigQuery (used in OWOX extension) — it appears automatically, named after your GCP project ID.

☝️ The Title and Project ID of this storage are locked. Each GCP project gets exactly one system storage to maintain stable integration with the Extension.

OWOX Data Marts Storages list showing four entries. Arrows highlight the Storages navigation item and the "Google BigQuery (used in OWOX extension)" type label.

Click on the storage entry to open its settings. Then:

  1. Under Authentication Method, choose Service Account JSON or Connect with Google.
  2. If using Service Account JSON, paste your Service Account JSON key into the Service Account field.
  3. Leave Auto-detect location selected unless you experience region-specific query errors.
  4. Click Save.

Configure Storage Provider dialog with Location set to "Auto-detect location" and Authentication Method toggled to "Service Account JSON". The Service Account field shows a pasted JSON key with type, project_id, and private_key fields. An arrow points to the JSON key field. A Save button appears at the bottom.

After completing the storage setup, your extension Data Marts appear with Draft status. This means OWOX has imported their definitions but has not yet verified access. To make them operational, publish them.

To publish multiple Data Marts at once, open the three-dot menu on the storage row and select Publish drafts.

OWOX Data Marts Storages list with a three-dot context menu open on the "smwyc-test-3" row (Google BigQuery used in OWOX extension). The menu shows three options: View details, Edit, and Publish drafts. An arrow points to the "Publish drafts" option.

Once published, each Data Mart is live: its output schema is visible and it can be connected to destinations.

☝️ Extension and web Data Marts are bidirectionally linked. Deleting a Data Mart in the web app also removes it from the extension. New Data Marts created in the web app do not sync back to the extension.

OWOX can analyze the output schema and run history of a Data Mart to surface anomalies, trends, or suggestions — using your existing data, with no additional pipeline required.

Demo Google Sheets Report Data Mart detail page on the Insights tab. The tab is circled in red. The content area shows an empty state with "Create your first Insight" message, a "Generate Insight with AI" button, and a "+ Blank Insight" button.

  1. Add an Email destination.
  2. Open a published Data Mart and go to the Destinations tab.
  3. Configure recipients and set a Report Trigger (daily, weekly, monthly, or on an interval).

At the scheduled time, OWOX queries BigQuery using your stored credentials, formats the result, and sends it by email.

  1. Add a Looker Studio destination.
  2. Open a published Data Mart and go to the Destinations tab.
  3. Enable the Available in Looker Studio toggle for that destination.
  4. In Looker Studio, connect using the OWOX Data Marts connector and the JSON Config token generated by the web app.

Facebook Data Mart detail page on the Destinations tab. Two destination rows are listed under "Marketing Team": an email destination and a Looker Studio destination. The Looker Studio row is expanded showing an enabled "Available in Looker Studio" toggle with the status "Waiting for Looker Studio to fetch data". An arrow points to the toggle.

☝️ Google Sheets uses push mode — OWOX sends data to a sheet on a schedule, so data is static between runs. Looker Studio uses pull mode — data is fetched live from BigQuery each time you open the report, subject to the cache lifetime you configured.

Your existing extension Data Marts query data already in BigQuery. Connector-based Data Marts go one step further: they pull raw data from ad platforms directly into BigQuery, which you can then query with your existing SQL Data Marts.

Supported sources: Facebook Ads, TikTok Ads, LinkedIn Ads, X Ads, Microsoft Ads, Reddit Ads, Criteo Ads, and others.