Documentation

While configuring your Google Search Ads 360 connection, you may encounter several issues. Understanding these common errors can help streamline the setup process and facilitate quick resolutions.

Permissions issue

‍If you only have access to the client account and do not have permissions for the manager or sub-manager accounts, labels, and other management data will not be extracted until the appropriate permissions are granted. You can learn more about this here.

Custom columns

How to enable custom columns for your report

Custom columns for Google Search Ads 360 are configured using two specific options in the “Extraction Template Settings”:

• Load Dynamic Metrics
• Google Search Ads 360 Custom Column ID

First, to enable custom columns in the extract, set “Load Dynamic Metrics” to “Yes”. Then, to get the data from the custom columns, enter the required custom column IDs in the “Google Search Ads 360 Custom Column ID” field. Improvado will query the name of this column and you will see your custom column name in data table.

{%docs-informer info%}

• If the Load Dynamic Metrics = ```Yes``` and Google Search Ads 360 Custom Column ID is empty only standard fields will be requested within the extraction.
• To avoid data discrepancies, make sure there are no duplicates in the names of the custom columns you need.

{%docs-informer-end%}

Data discrepancy in custom columns with the same naming

If you encounter missing data when importing columns that share identical names but have different IDs, this behavior is expected and reflects system design principles. To ensure data integrity, Improvado intentionally preserves platform-specific structures and does not merge or transform metrics during extraction. Identically named columns (even with different IDs) are treated as duplicates to mirror how platforms like Google Search Ads 360 handle reporting.

Solution

Set different names for different columns.

Custom columns issues

If you're getting the following error during the extraction process: ```The Custom Column ID selected in the Google Search Ads 360 custom settings does not comply with the API requirements...```, It may appear in a few different cases:

Case 1. The custom columns specified in the ```referencedSystemColumns``` parameter may include segments or metrics that are not permitted for the report-type resource you are trying to extract data from.

If this occurs, the API will return an error message containing ```PROHIBITED_METRIC_IN_SELECT_OR_WHERE_CLAUSE```, along with a list of custom columns that should be removed from the "Google Search Ads 360 Custom Column ID" setting.

Example of custom column:

{
  "resourceName": "customers/111111111/customColumns/12345",
  "id": "12345",
  "name": "Improvado - Imps (Lost to Budget)",
  "valueType": "DOUBLE",
  "referencesMetrics": true,
  "queryable": true,
  "referencedSystemColumns": [
    "metrics.impressions",
    "metrics.search_budget_lost_impression_share"
  ],
  "renderType": "NUMBER"
}

API error:

...
"errorCode": {
  "queryError": "PROHIBITED_METRIC_IN_SELECT_OR_WHERE_CLAUSE"
},
"message": "Cannot select or filter on the following metrics: 'custom_columns.id[12345]'(could not support requested resources: 'AD_GROUP_AD'), since metric is incompatible with the resource in the FROM clause or other selected segmenting resources."
...

Case 2. The custom columns failed due to an unknown API issue, the error message will look like this:

...
"errorCode": {
  "internalError": "INTERNAL_ERROR"
},
"message": "An internal error has occurred."
...

In such cases, please contact Improvado Support through the Improvado Service Desk for further assistance.

‍

mrt_ Transformations Discontinued

Effective December 4, 2024, mrt_ enriched views structure will no longer be updated. To ensure data consistency and reporting accuracy, take the following actions:

1. Use Bulk Edit: Update your extraction orders to include necessary properties. This preserves consistency with the mrt_ view in your dashboards while maintaining performance reporting on Improvado.

2. Switch BI Tool Sources: Replace mrt_ views with the general table with updated property fields in your BI tools, as new fields will no longer flow to mrt_ views.

3. Adopt the Custom Configuration Flow: Use this feature to choose the property fields that best meet your reporting needs.

‍