|
| 1 | +--- |
| 2 | +title: Troubleshoot the Google AdWords connector |
| 3 | +titleSuffix: Azure Data Factory & Azure Synapse |
| 4 | +description: Learn how to troubleshoot issues with the Google AdWords connector in Azure Data Factory and Azure Synapse Analytics. |
| 5 | +author: jianleishen |
| 6 | +ms.service: data-factory |
| 7 | +ms.subservice: data-movement |
| 8 | +ms.topic: troubleshooting |
| 9 | +ms.date: 02/23/2022 |
| 10 | +ms.author: jianleishen |
| 11 | +ms.custom: has-adal-ref, synapse |
| 12 | +--- |
| 13 | + |
| 14 | +# Troubleshoot the Google AdWords connector in Azure Data Factory and Azure Synapse |
| 15 | + |
| 16 | +[!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)] |
| 17 | + |
| 18 | +This article provides suggestions to troubleshoot common problems with the Google AdWords connector in Azure Data Factory and Azure Synapse. |
| 19 | + |
| 20 | +## Error code: |
| 21 | + |
| 22 | +- **Message**: |
| 23 | + |
| 24 | +- **Cause**: |
| 25 | + |
| 26 | + Due to the sunset of Google AdWords API by April 27, 2022, you are recommended to migrate to the new version of Google AdWords API before the starting date April 27, 2022, and connection will start to fail because of the deprecation of Google AdWords API (see this [link](https://ads-developers.googleblog.com/2021/04/upgrade-to-google-ads-api-from-adwords.html)). Migration steps: |
| 27 | + |
| 28 | + 1. Open your Google AdWords connector linked service. |
| 29 | + 2. Edit the linked service and choose the new API version. |
| 30 | + |
| 31 | + :::image type="content" source="media/connector-troubleshoot-guide/update-google-adwords-linked-service.png" alt-text="Screenshot of updating the linked service configuration for Google AdWords."::: |
| 32 | + |
| 33 | + 3. Apply the changes. |
| 34 | + |
| 35 | +- **Known issues and recommendations**: |
| 36 | + |
| 37 | + 1. The new Google AdWords API doesn't provide a migration plan for below reports/tables: |
| 38 | + a. AD_CUSTOMIZERS_FEED_ITEM_REPORT |
| 39 | + b. CAMPAIGN_GROUP_PERFORMANCE_REPORT |
| 40 | + c. CAMPAIGN_NEGATIVE_KEYWORDS_PERFORMANCE_REPORT |
| 41 | + d. CAMPAIGN_NEGATIVE_LOCATIONS_REPORT |
| 42 | + e. CAMPAIGN_NEGATIVE_PLACEMENTS_PERFORMANCE_REPORT |
| 43 | + f. CREATIVE_CONVERSION_REPORT |
| 44 | + g. CRITERIA_PERFORMANCE_REPORT |
| 45 | + h. FINAL_URL_REPORT |
| 46 | + i. KEYWORDLESS_CATEGORY_REPORT |
| 47 | + j. MARKETPLACE_PERFORMANCE_REPORT |
| 48 | + k. TOP_CONTENT_PERFORMANCE_REPORT |
| 49 | + |
| 50 | + 2. The syntax for Google AdWords query language is similar to AWQL from the AdWords API, but not identical. You can refer this [document](https://developers.google.com/google-ads/api/docs/migration/querying) for more details. |
| 51 | + |
| 52 | + |
| 53 | +## Next steps |
| 54 | + |
| 55 | +For more troubleshooting help, try these resources: |
| 56 | + |
| 57 | +- [Connector troubleshooting guide](connector-troubleshoot-guide.md) |
| 58 | +- [Data Factory blog](https://azure.microsoft.com/blog/tag/azure-data-factory/) |
| 59 | +- [Data Factory feature requests](/answers/topics/azure-data-factory.html) |
| 60 | +- [Azure videos](https://azure.microsoft.com/resources/videos/index/?sort=newest&services=data-factory) |
| 61 | +- [Microsoft Q&A page](/answers/topics/azure-data-factory.html) |
| 62 | +- [Stack Overflow forum for Data Factory](https://stackoverflow.com/questions/tagged/azure-data-factory) |
| 63 | +- [Twitter information about Data Factory](https://twitter.com/hashtag/DataFactory) |
0 commit comments