Unable to Configure a Custom Report
Issue
It's not possible to set up a custom report because the report name isn't available or the fields I want to include aren't available.
Environment
Connector: Google Ads
Resolution
The report name isn't available
While setting up a custom report, you must select the Report Name of the report you want to sync. We source the names from the list of resources with metrics available in Google Ads' API documentation. However, we don't sync all reports and resource types. If you can't find the report you want in the Report Name dropdown, we don't sync it as a custom report.
If you can't configure the custom report you want, check our Google Ads Entity Relationship Diagram (ERD) to see if we sync the required fields in one of our prebuilt reports or metadata tables. For example, label data is available through the ad_group_ad_label
resource, which we don't sync. However, we offer a LABEL
table and several LABEL_HISTORY
tables.
NOTE: If you can't find the data you want in the ERD, consider submitting a feature request.
The field I want to include isn't available
To determine which fields are available for each report, locate the report in Google Ads' API documentation. Each report contains three types of fields: resource fields, segments, and metrics.
Some fields are incompatible with chosen segments. As a result, when you select a segment, some fields may be unavailable. See Google's segments documentation to determine which fields you can combine with each segment.
To understand why you can't include a certain field, attempt to build the query using the Google Ads Query Builder or do the following:
- Confirm that the field is included in the selected report by locating it in Google's list of resources.
- If you have included a segment, locate it in Google's segments documentation to determine which fields you can combine with the segment.
- Attempt to create a brand new report that includes the applicable field. If you can include the field in a new report, this confirms that you can't include it in your existing report due to incompatibility with other fields.