# Migrating Google Adwords Integrations

Complete the following steps to migrate from the Google Adwords data connector to the new Google Ads V2 connector. The old one uses Google Adwords API to import data, while the new version uses Google Ads API to ingest data.

# Characteristics of Ingested Data

When migrating data from one place or version, it is worth being aware of how that data might be transformed. The following sections outline some important characteristics to be aware of.

## Ad Performance Report

There are some deprecated metrics:

- ClickAssistedConversions
- ClickAssistedConversionsOverLastClickConversions
- ClickAssistedConversionValue
- AverageFrequencyImpressionAssistedConversions
- ImpressionAssistedConversionsOverLastClickConversions
- ImpressionAssistedConversionValue


## Adgroup Performance Report

There are some unsupported predefined metrics:

- 
```
AbsoluteTopImpressionPercentage (metrics.absolute_top_impression_percentage)
```
- 
```
TopImpressionPercentage (metrics.top_impression_percentage)
```


There are some deprecated metrics:

- ClickAssistedConversions
- ClickAssistedConversionsOverLastClickConversions
- ClickAssistedConversionValue
- ImpressionAssistedConversions
- ImpressionAssistedConversionsOverLastClickConversions
- ImpressionAssistedConversionValue


## Campaign Performance Report

There are some deprecated metrics:

- AverageFrequency
- ClickAssistedConversions
- ClickAssistedConversionsOverLastClickConversions
- ClickAssistedConversionValue
- ImpressionReach
- ImpressionAssistedConversions
- ImpressionAssistedConversionsOverLastClickConversions
- ImpressionAssistedConversionValue


## Keywords Performance Report

There are some deprecated metrics:

- ClickAssistedConversions
- ClickAssistedConversionsOverLastClickConversions
- ClickAssistedConversionValue
- ImpressionAssistedConversions
- ImpressionAssistedConversionsOverLastClickConversions
- ImpressionAssistedConversionValue


## Audience Performance Report (Not support)


```
The AUDIENCE_PERFORMANCE_REPORT returned data for both campaign-level and ad group-level audience criteria, while the Google Ads API provides this information in two separate resources: campaign_audience_view and ad_group_audience_view.
```

## Date Range:

- `LAST_WEEK`  option is unsupported.
- `segments.date` is required for Date range except `ALL_TIME`


# Create a New Google Ads V2 Connector

Go to Treasure Data Catalog, then search and select Google Ads v2.

![](/assets/screen-shot-2022-03-24-at-15.03.08.ef4aee4a3dd150a8d4ef9cc032f36545724a546c73d2075afbfc384169ced3b1.eb5176de.png)

In the dialog box, enter the values that you enter in your legacy Google Ads connector.

Using OAuth to authenticate the connector

![](/assets/screen_shot_2022-03-27_at_15_45_43.8fd3d68cd2e949f59bba7c3c3a3d220b79110f94bc3dffee12c83a85d3cc2884.eb5176de.png)

# Save Settings and Run the Legacy Google Adwords Data Connector One Last Time

You can save your legacy setting from TD Console or from the CLI.

- [Ad Performance Report](/int/migrating-google-adwords-integrations#ad-performance-report1)
- [Adgroup Performance Report](/int/migrating-google-adwords-integrations#adgroup-performance-report)
- [Campaign Performance Report](/int/migrating-google-adwords-integrations#campaign-performance-report)
- [Keywords Performance Report](/int/migrating-google-adwords-integrations#keywords-performance-report)
- [Audience Performance Report (Not support)](/int/migrating-google-adwords-integrations#audience-performance-report-not-support)
- [Date Range:](/int/migrating-google-adwords-integrations#date-range)
- [Using TD Console](/int/migrating-google-adwords-integrations#using-td-console)
- [Using CLI and Workflow](/int/migrating-google-adwords-integrations#using-cli-and-workflow)
- [Migration Guide](/int/migrating-google-adwords-integrations#migration-guide)
- [Query Migration Tool](/int/migrating-google-adwords-integrations#query-migration-tool)
- [Query Validator](/int/migrating-google-adwords-integrations#query-validator)
- [Query Builder](/int/migrating-google-adwords-integrations#query-builder)


## Using TD Console

### Save the Settings of Your Scheduled Legacy Google Adwords Connector and Run a Final Import

Go to Integration Hub > Sources. Search for your scheduled Google Adwords source, select the source and select **Edit**.

![](/assets/screen_shot_2022-03-27_at_15_50_27.727668481171d8a0fb2eff7d73a6cc6124ecfb52e0dc2fcb9f3c0b8dccf57e72.eb5176de.png)

In the dialog box, copy the settings to use later:

![](/assets/screen_shot_2022-03-29_at_16_08_23.9f0d78d1eb9303528b8dd510a13aa0f5d58f0946b28f4054eb8cdf3d8d859415.eb5176de.png)

Also copy any advanced settings:

![](/assets/screen-shot-2022-03-27-at-15.55.24.59c029cc2dedfcbc00a5c0aeeb3efd55e12a8e9649106f695d1423fefa220557.eb5176de.png)

Next, you configure one final run with the legacy data connector to create a temporary table against which you can run a config-diff. You use the diff to identify and confirm the latest data imported into Treasure Data.

![](/assets/image-20190920-223452.4bf2fa218a9517425dacb967c12df40769e981e8c13a7c1f2ae45db5ba8decb8.eb5176de.png)

Before running the final import with the legacy connector, make sure that you change the schedule to one run only:

![](/assets/image-20190920-223521.97b218bd0b67056dd5358973c55e88e9b4c4c667b32526fa94565b7750d59a96.eb5176de.png)

After the job is complete, look at and copy **config_diff** in the job query information somewhere to use later.

![](/assets/image-20190920-223541.b56a9ac85b1cd27d402643428847df0a61045b7641ee3f81a8284d27a18b0493.eb5176de.png)

### **Create New Google Adwords V2 Source**

Go to Integration Hub > Authentication. Search for the new Google Ads V2 connection that you created:

![](/assets/screen_shot_2022-03-27_at_15_57_58.70ef63abf8bbc55eb9d799a362755699f9b47e7cbef382ce6251b4402b5c52c5.eb5176de.png)

Select the New Source. Fill in all basic settings and advanced settings that you copied in the preceding steps.

![](/assets/screen_shot_2022-03-27_at_16_04_01.16939beaedf3c0179f693c6722158be090148d357251758e57f1f227f7b181dc.eb5176de.png)

After completing the settings, choose the database and table job to populate data into, then schedule the job and provide a name for your new data connector. Select **Save** and then run the new data connector.

## Using CLI and Workflow

Update in: type in your yml configuration from google_adwords to google_adwords_v2.

For example, your existing workflow configuration might look something like this:


```
in:
  type: google_adwords
  client_id: ${client_id}
  client_secret: ${client_secret}   
  refresh_token: ${refresh_token}   
  client_customer_id: ${client_customer_id}
  target: KEYWORDS_PERFORMANCE_REPORT
  include_predefined_metrics: true
  developer_token: ${developer_token}
  date_range: "TODAY"
out: {}
exec: {}
filters: []
```

Your new workflow configuration would look like this:


```
in:
  type: google_adwords_v2
  client_id: ${client_id}
  client_secret: ${client_secret}   
  refresh_token: ${refresh_token}   
  client_customer_id: ${client_customer_id}
  target: KEYWORDS_PERFORMANCE_REPORT
  include_predefined_metrics: true
  developer_token: ${developer_token}
  enable_multiple_page: false
  date_range: "TODAY"
out: {}
exec: {}
filters: []
```

# Appendix

## Migration Guide

[https://developers.google.com/google-ads/api/docs/migration](https://developers.google.com/google-ads/api/docs/migration)

## Query Migration Tool

[https://developers.google.com/google-ads/api/docs/migration/query-migration-tool](https://developers.google.com/google-ads/api/docs/migration/query-migration-tool)

## Query Validator

[https://developers.google.com/google-ads/api/fields/v10/query_validator](https://developers.google.com/google-ads/api/fields/v10/query_validator)

## Query Builder

[https://developers.google.com/google-ads/api/fields/v10/ad_group_audience_view_query_builder](https://developers.google.com/google-ads/api/fields/v10/ad_group_audience_view_query_builder)