Skip to content

Commit d9b76e0

Browse files
committed
Update Google AdWords connector and troubleshoot doc
1 parent 2420e50 commit d9b76e0

File tree

3 files changed

+40
-33
lines changed

3 files changed

+40
-33
lines changed

articles/data-factory/connector-google-adwords.md

Lines changed: 30 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: data-factory
88
ms.subservice: data-movement
99
ms.topic: conceptual
1010
ms.custom: synapse
11-
ms.date: 09/09/2021
11+
ms.date: 02/24/2022
1212
---
1313

1414
# Copy data from Google AdWords using Azure Data Factory or Synapse Analytics
@@ -19,7 +19,7 @@ ms.date: 09/09/2021
1919
This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Google AdWords. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
2020

2121
> [!Important]
22-
> Due to the sunset of Google AdWords API by April 27, 2022, the service has upgraded to the new Google Ads API. Please refer this [document](connector-troubleshoot-google-adwords.md) for detailed migration steps and recommendations. Please make sure the migration to be done before April 27,2022.
22+
> Due to the sunset of Google AdWords API by April 27, 2022, the service has upgraded to the new Google Ads API. Please refer this [document](connector-troubleshoot-google-adwords.md) for detailed migration steps and recommendations. Please make sure the migration to be done before **April 27,2022**.
2323
2424
## Supported capabilities
2525

@@ -71,7 +71,10 @@ The following properties are supported for Google AdWords linked service:
7171
| Property | Description | Required |
7272
|:--- |:--- |:--- |
7373
| type | The type property must be set to: **GoogleAdWords** | Yes |
74+
| connectionProperties | A group of properties that defines how to connect to Google AdWords. | Yes |
75+
| ***Under `connectionProperties`:*** | | |
7476
| clientCustomerID | The Client customer ID of the AdWords account that you want to fetch report data for. | Yes |
77+
| loginCustomerID | The customer ID of the Google AdWords manager account through which you want to fetch report data of specific customer.| No |
7578
| developerToken | The developer token associated with the manager account that you use to grant access to the AdWords API. You can choose to mark this field as a SecureString to store it securely, or store password in Azure Key Vault and let the copy activity pull from there when performing data copy - learn more from [Store credentials in Key Vault](store-credentials-in-key-vault.md). | Yes |
7679
| authenticationType | The OAuth 2.0 authentication mechanism used for authentication. ServiceAuthentication can only be used on self-hosted IR. <br/>Allowed values are: **ServiceAuthentication**, **UserAuthentication** | Yes |
7780
| refreshToken | The refresh token obtained from Google for authorizing access to AdWords for UserAuthentication. You can choose to mark this field as a SecureString to store it securely, or store password in Azure Key Vault and let the copy activity pull from there when performing data copy - learn more from [Store credentials in Key Vault](store-credentials-in-key-vault.md). | No |
@@ -90,32 +93,34 @@ The following properties are supported for Google AdWords linked service:
9093
"properties": {
9194
"type": "GoogleAdWords",
9295
"typeProperties": {
93-
"clientCustomerID" : "<clientCustomerID>",
94-
"developerToken": {
95-
"type": "SecureString",
96-
"value": "<developerToken>"
97-
},
98-
"authenticationType" : "ServiceAuthentication",
99-
"refreshToken": {
100-
"type": "SecureString",
101-
"value": "<refreshToken>"
102-
},
103-
"clientId": {
104-
"type": "SecureString",
105-
"value": "<clientId>"
106-
},
107-
"clientSecret": {
108-
"type": "SecureString",
109-
"value": "<clientSecret>"
110-
},
111-
"email" : "<email>",
112-
"keyFilePath" : "<keyFilePath>",
113-
"trustedCertPath" : "<trustedCertPath>",
114-
"useSystemTrustStore" : true,
96+
"connectionProperties": {
97+
"clientCustomerID": "<clientCustomerID>",
98+
"loginCustomerID": "<loginCustomerID>",
99+
"developerToken": {
100+
"type": "SecureString",
101+
"value": "<developerToken>"
102+
},
103+
"authenticationType": "ServiceAuthentication",
104+
"refreshToken": {
105+
"type": "SecureString",
106+
"value": "<refreshToken>"
107+
},
108+
"clientId": {
109+
"type": "SecureString",
110+
"value": "<clientId>"
111+
},
112+
"clientSecret": {
113+
"type": "SecureString",
114+
"value": "<clientSecret>"
115+
},
116+
"email": "<email>",
117+
"keyFilePath": "<keyFilePath>",
118+
"trustedCertPath": "<trustedCertPath>",
119+
"useSystemTrustStore": true,
120+
}
115121
}
116122
}
117123
}
118-
119124
```
120125

121126
## Dataset properties

articles/data-factory/connector-troubleshoot-google-adwords.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,22 +17,24 @@ ms.custom: has-adal-ref, synapse
1717

1818
This article provides suggestions to troubleshoot common problems with the Google AdWords connector in Azure Data Factory and Azure Synapse.
1919

20-
## Error code:
20+
## Migrate to the new version of Google AdWords API
2121

22-
- **Message**:
22+
- **Symptoms**
2323

24-
- **Cause**:
24+
You see a hint on the Google AdWords linked service configuration page. It reminds you to upgrade your linked service to a newer version before the legacy API is deprecated by Google.
2525

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:
26+
- **Cause**
27+
28+
Due to the sunset of Google AdWords API by April 27, 2022, you are recommended to migrate to the new version of Google Ads API before the 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:
2729

28-
1. Open your Google AdWords connector linked service.
29-
2. Edit the linked service and choose the new API version.
30+
1. Open your Google AdWords connector linked service configuration page.
31+
2. Edit the linked service and choose the new API version (select **Google Ads**).
3032

3133
:::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.":::
3234

3335
3. Apply the changes.
3436

35-
- **Known issues and recommendations**:
37+
- **Known issues and recommendations**
3638

3739
1. The new Google AdWords API doesn't provide a migration plan for below reports/tables:
3840
a. AD_CUSTOMIZERS_FEED_ITEM_REPORT
@@ -47,7 +49,7 @@ This article provides suggestions to troubleshoot common problems with the Googl
4749
j. MARKETPLACE_PERFORMANCE_REPORT
4850
k. TOP_CONTENT_PERFORMANCE_REPORT
4951

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.
52+
2. The syntax for Google Ads 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.
5153

5254

5355
## Next steps
4.76 KB
Loading

0 commit comments

Comments
 (0)