Signing up and linking your Ads credential

To use Cognetik’s Google Ads connector, you first need to sign up and link your credentials within the Cognetik Connector in Tableau.

Reports

There are 13 reports available in the Ads Connector:

  • Account Performance Report
  • Adgroup Performance Report
  • Ad Performance Report
  • Audience Performance Report
  • Bid Goal Performance Report
  • Campaign Performance Report
  • Click Performance Report
  • Display Keyword Performance Report
  • Final Url Performance Report
  • Geo Performance Report
  • Keyword Performance Report
  • Search Query Performance Report
  • URL Performance Report

Account Performance Report

The Account Performance report includes all statistics aggregated by default at the account level, one row per account. If other segment fields are used, you may get more than one row per account.

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Adgroup Performance Report

The Ad Group Performance report includes all statistics aggregated by default at the ad group level, one row per ad group. If other segment fields are used, you may get more than one row per ad group

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Ad Performance Report

The Ad Performance report includes all statistics aggregated at the ad level, one row per ad. If other segment fields are used, you may get more than one row per ad. 

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Audience Performance Report

The Audience Performance report includes performance data from interests and remarketing lists for Display Network and YouTube Network ads, and remarketing lists for search ads (RLSA), aggregated at the audience level—one row per audience. If other segment fields are used, you may get more than one row per topic.

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Bid Goal Performance Report

The Bid Goal Performance report includes statistics for your portfolio bid strategies.

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Campaign Performance Report

The Campaigns Performance report includes all statistics aggregated by default at the campaign level, one row per campaign. If other segment fields are used, you may get more than one row per campaign.

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Click Performance Report

The Click Performance report includes stats aggregated at each click level, and includes both valid and invalid clicks.

Note: This report can be run only for a single day and only for dates up to 90 days before the time of the request.

  • For non-Search campaigns, the Clicks field represents the number of valid and invalid interactions instead of clicks.
  • The ClickType field will reflect each area of the ad that the user clicked for each GclId (Google Click Identifier). This differs from other reports, where the ClickType shows every area of the ad that was shown to the user for each impression.
  • The Date field indicates the time of the impression, not the time of the click.

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Display Keyword Performance Report

The Display Keyword Performance report includes all Display Network and YouTube Network statistics aggregated at the keyword level, one row per keyword. If other segment fields are used, you may get more than one row per keyword. 

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Final URL Performance Report

The Final URL report includes all statistics aggregated at the final URL level, one row per final URL. If other segment fields are used, you may get more than one row per final URL. 

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Geo Performance Report

The Geo Performance report includes all statistics aggregated at the country/territory level, one row per country/territory.

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Keyword Performance Report

The Keywords Performance report includes all statistics aggregated at the keyword level, one row per keyword. If other segment fields are used, you may get more than one row per keyword. 

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Search Query Performance Report

The Search Terms report includes all statistics aggregated at the search terms level, one row per combination of search terms. If other segment fields are used, you may get more than one row per combination of search terms. 

Note: The API only show the first 128 char bytes of a query; so two rows with seemingly identical query strings just indicates that there were some differences past the 128th byte

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

URL Performance Report

The URL Performance report includes all statistics aggregated at the URL and criterion level, one row per combination of:

  • URL where your ads have been displayed (Url)
  • Targeting criterion (CriteriaParameters)

If other segment fields are used, you may get more than one row per combination of URL and placement criterion.

For a list of all the metrics and dimensions supported by this report, and information about these parameters (including incompatibility with other metrics and dimensions), please refer to AdWords’ documentation.

Error Guide

What to do if I run into an error?

If you run into an error message, feel free to contact us on our website through our chat box, in the lower right corner. 

Send us your error message, along with the specifics of your issue (screenshot of the complete query that generated the error) so we can replicate the error and troubleshoot it

Error Troubleshooting

In this section, we’ll describe three broad categories of errors. Keep in mind that these categories don't encompass all possible errors, and some may fit into more than one category, 

1. Authentication and authorization errors.

Authentication refers to whether Cognetik has been given permission by a user to access AdWords acting on their behalf. Authentication is managed through credentials generated by the OAuth2 flow.

Authorization refers to whether Cognetik, authenticated and acting as a user, is allowed to work with the particular AdWords data it is trying to read or write

The most common reason an authentication error arises is when the authenticated user revokes the permission they gave Cognetik to act on their behalf. 

For example, if you manage separate AdWords accounts for independent clients and authenticate separately as each client when managing that client's account, a client could revoke Cognetik's access at any time. Depending on when your access was revoked, the API may directly return an AuthenticationError.OAUTH_TOKEN_REVOKED error 

Another common reason an authorization error arises from factors beyond your control is due to changes in your manager account hierarchy. Apps working with a single manager account hierarchy usually authenticate as an administrator user of their top-level manager account, since this user has the authority to access all of the sub-accounts in the hierarchy. If a user of a sub-account removes the manager link, Cognetik will receive an AuthorizationError.USER_PERMISSION_DENIED error when attempting to access that account. You can use ManagedCustomerService to check whether the sub-account has indeed been removed from the hierarchy.

Another reason an authorization error can arise is when the user Cognetik authenticated as, has their access rights changed. For example, suppose another user with administrator rights on the AdWords account changes your app's authenticated user's rights to read-only. In this case, all mutate requests will fail with an AuthorizationError.USER_HAS_READONLY_PERMISSION error.

2. Retryable errors

Some errors can indicate a temporary problem that may be resolved by retrying the request after a short pause. These include CONCURRENT_MODIFICATION, UNEXPECTED_INTERNAL_API_ERROR, and RATE_EXCEEDED.

When you retry requests, use an exponential backoff policy. For example, if you first pause 5 seconds before the first retry, you could pause 10 seconds after the second and 20 seconds after the third retry. Exponential backoff helps ensure you are not calling the API too aggressively.

For RATE_EXCEEDED errors, the amount of time your app pauses before attempting to retry should be at least longer than the retryAfterSeconds field in the error. See the Rate Limits guide for more details. Other retryable errors can be retried sooner but should still follow an exponential backoff policy.

3. Validation errors

Validation errors indicate that an input to an operation was not acceptable. Some examples include PolicyViolationError, DateError, DateRangeError, StringLengthError, UrlError, and many others.

Validation errors occur most commonly in user-initiated requests, where a user has entered invalid input. 

For a list of common errors, please refer to Google Ads’ API documentation.

For a list of various API limits, please refer to Google’s Ads API documentation.

Did this answer your question?