The fastest AdsWizz to Looker Studio connection is a third-party community connector, such as Catchr, which pulls AdsWizz reporting data into a Looker Studio data source. Google's native connector catalogue includes Google Ads, Google Ad Manager, BigQuery, Google Sheets and CSV uploads, but it does not list AdsWizz as a built-in connector.
For full technical control, use the AdsWizz Domain API, load the results into BigQuery or Google Sheets, and connect that destination to Looker Studio.
You have 4 practical connection routes:
| Method | Best for | Refresh | Main limitation |
|---|---|---|---|
| Third-party AdsWizz connector | Fast, no-code dashboards | Automatic, depending on provider | Provider fees and field availability |
| AdsWizz API to BigQuery | Scalable reporting and multiple clients | Automated with your own workflow | Requires development and data modelling |
| AdsWizz API to Google Sheets | Small reporting workflows | Automated with scripting or an integration tool | Sheets has performance and row-size limitations |
| CSV upload | One-off reports | Manual | No automatic updates |
A community connector is the simplest choice when you want an AdsWizz dashboard without building an API pipeline. Catchr's AdsWizz connector supports exporting campaign data to Looker Studio and lets you select AdsWizz accounts, dimensions and metrics before sending the data to a reporting destination.
AdsWizz reporting can include several environments, including AudioServe, AudioMax and AudioMatic. Confirm that the connector is using the correct AdsWizz environment before comparing metrics across reports.
A basic AdsWizz performance dashboard usually needs the following fields.
Dimensions
Metrics
Start with one reporting grain, such as Campaign plus Date. Add geographic or device dimensions only when the report needs them. More dimensions create more rows and can change how totals are calculated.
The API route is the better choice when you need custom authentication, central data storage, historical reporting or dashboards across several AdsWizz accounts.
The AdsWizz Domain API uses an API key and supports custom reports built from selected dimensions, metrics, filters and reporting intervals. AdsWizz requires an API key for access, and API requests use an agency identifier and environment where applicable.
AdsWizz
↓
AdsWizz Domain API
↓
BigQuery or Google Sheets
↓
Looker Studio
Google provides native connectors for both BigQuery and Google Sheets. Looker Studio also supports reusable data sources, calculated fields, data credentials and data freshness settings.
Use BigQuery instead of Google Sheets when you need:
Google Sheets is suitable for a smaller workflow where the extracted AdsWizz dataset is compact and the reporting logic is simple.
For a one-off report, export a CSV from AdsWizz and use the Upload CSV files connector in Looker Studio.
This approach is simple but does not suit recurring client reporting. Google states that uploaded CSV data sources cannot update automatically, so you must import a new file whenever the underlying AdsWizz data changes.
Use manual CSV uploads when:
The right method depends on whether you value setup speed or control over the reporting pipeline.
Choose a third-party connector when you need a working dashboard quickly and its available fields meet your reporting requirements.
Choose AdsWizz API to BigQuery when the report is business-critical, needs historical storage, combines multiple platforms or will be used by several clients.
Choose AdsWizz API to Google Sheets when the workflow is small and your team already manages reporting in spreadsheets.
Choose CSV upload for temporary or one-time reporting.
A report grouped by Campaign plus Date produces different totals from a report grouped by Campaign, Date, Country and Device Type. The extra dimensions split campaign performance into smaller rows.
Define the grain before creating calculated fields. For example:
One row = one campaign, one reporting date, one country
This reduces the risk of double counting when you blend the data with another source.
Use:
A common CTR calculation is:
SUM(Clicks) / SUM(Impressions)
Format the result as a percentage in Looker Studio.
AdsWizz campaign metadata and delivery performance are different types of data. Campaign names, advertiser names and campaign statuses describe entities. Impressions, clicks and conversions describe performance.
Keep these relationships clear when joining or blending data:
Advertiser -> Campaign -> Ad -> Performance
Joining two performance tables at different grains can multiply rows and inflate totals.
AdsWizz is not listed among Google's built-in connectors. Search the Looker Studio Connector Gallery for a third-party AdsWizz connector, or use the API route through BigQuery or Google Sheets.
This is expected for an API-based AdsWizz connection. AdsWizz requires an authentication key, and the key must have access to the relevant agency or reporting environment.
Check the following:
A Google Workspace administrator can restrict third-party connectors. Apps Script must also be enabled for community connectors to fetch data in Looker Studio. If a connector is unavailable or charts return an Apps Script error, contact the Google Workspace administrator.
For most teams, start with a third-party AdsWizz connector if its fields and refresh options cover the dashboard requirements.
Use AdsWizz API to BigQuery to Looker Studio when you need long-term historical reporting, multiple accounts, cross-channel joins or tighter access controls. Keep the Google Sheets route for smaller workflows, and use CSV uploads for one-time analysis.