Intro
Google Search Ads 360, formerly DoubleClick Search (DS), is a search management platform that helps agencies and marketers efficiently manage some of the largest search marketing campaigns in the world, across multiple engines and media channels. To learn more about the Search Ads 360 Reporting API, visit their page (https://developers.google.com/search-ads/reporting/overview ). You can connect to your Google Search Ads account in the Data Center. This topic discusses the fields and menus that are specific to the Google Search Ads 360 (SA360) connector user interface. To add DataSets, set update schedules, and edit DataSet information, see Adding a DataSet Using a Data Connector.Prerequisites
To connect to your Search Ads 360 account and create a DataSet, you must have the following:- A Search Ads 360 client ID
- A Search Ads 360 client secret
https://your_instance/<appstore>/com.domo.connector.doubleclicksearch), then you may already have a Search Ads 360 client ID and secret. You can reuse these credentials if you want, however, you need to make sure that you enable the new Search Ads 360 Reporting API in the project used to generate the client ID and secret, and you need to reauthenticate before trying the new Search Ads 360 connector. Follow the below instructions to enable the new Reporting API.
Creating a Client ID and Secret
You can create a client ID and secret in the Google API Console. To do this, follow the below steps:- Go to Google API Console at https://console.developers.google.com.
- Click Credentials on the left column.
- From the Create Credentials menu, select OAuth Client ID.
- (Conditional) If OAuth Consent is not set up previously, continue to the Consent screen, or, navigate to Step 5.
- Add an App Name, User Support Email, and the Authorized Domain as domo.com, everything else can be blank.
- Select Save and Continue.
- There is no scope required, Save and Continue.
- There are no test users required, Save and Continue.
- Click Credentials in the left column.
- In the Create Credentials menu, select OAuth Client ID.
- Select Web application as the Application Type.
- Enter the desired name for the client (such as ” Search Ads 360 Client”).
- For the Authorized Redirect URL, enter https://oauth.domo.com/api/data/v1/oauth/providers/doubleclick-search/exchange.
- Click Create. A box pops up showing the client ID and secret. Copy the client ID and secret to be used in the connector.
Enabling the Search Ads 360 Reporting API
You need to make sure the Search Ads 360 Reporting API is enabled in the project that houses your client ID and secret. To do this, follow these steps:- Click Library in the left column.
- Search for the “Search Ads 360 Reporting API”. Note: If you search for “Search Ads 360” or “DoubleClick”, you may be presented with two options: “Search Ads 360 API” and “Search Ads 360 Reporting API”. Select the “ Search Ads 360 Reporting API ” option.
- Click the Enable button on the top of the screen. (If the button reads Disable, the API is already enabled.)
Connecting to Your Google Search Ads 360 Account
This section enumerates the options in the Credentials and Details panes on the Google Search Ads 360 Connector page. The components of the other panes on this page, Scheduling, and Name & Describe Your DataSet, are universal across most connector types and are discussed in greater length in Adding a DataSet Using a Data Connector.Credentials Pane
This pane contains fields for entering credentials to connect to your Google Search Ads 360 account. The following table describes what is needed for each field:Field | Description |
|---|---|
Client ID | Enter your Google API Client ID. |
Client Secret | Enter your Google API Client Secret. |
Details Pane
This pane contains a primary Reports menu, along with various other menus which may or may not appear depending on the report type you select.Menu | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Report | Select the Google Search Ads 360 report you want to run. The following reports are available:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Enter the id of the top level manager account, the authenticated user has access to. |
Other Panes
For information about the remaining sections of the Connector interface, including how to configure scheduling, retry, and update options, see Adding a DataSet Using a Data Connector.FAQs
I am using the legacy SA360 Connector. Can I use the same credentials or do I need to create a new Account?
I am using the legacy SA360 Connector. Can I use the same credentials or do I need to create a new Account?
If you have powered up the legacy SA360 Connector, you can use the same Account to power up the new SA360 Connector, but you must ensure the following additional steps first:
- Ensure that the client id and secret you are using have access to the Search Ads 360 Reporting API. See above for more information on enabling the API.
- Once you have updated the client id and secret, reauthenticate the connector Account.
How do I know which connector is using the new SA360 API and which connector is using the legacy SA360 API?
How do I know which connector is using the new SA360 API and which connector is using the legacy SA360 API?
The new SA360 connector can be found on your instance at https://your_instance.domo.com/appstore/connectors/com.domo.connector.doubleclicksearchnew. It has the following icons:
Can I run my legacy SA360 connector datasets in parallel with datasets I build on the new SA360 connector?
Can I run my legacy SA360 connector datasets in parallel with datasets I build on the new SA360 connector?
Yes, you can run your legacy SA360 datasets in parallel with datasets created on the new SA360 connector. The two connectors are separate, however, we do not recommend using the old connector to validate data in the new connector. We recommend using the new SA360 UI to validate the data.Is there any way for me to upgrade my legacy SA360 datasets instead of having to build out new ones? I have a lot of assets built on those datasets.Unfortunately, there isn’t a way to upgrade legacy SA360 datasets to use the new SA360 connector. The new version of the API that the connector uses is significantly different from the legacy API.
The connector is asking for a Google Manager Account ID. Where do I find that?
The connector is asking for a Google Manager Account ID. Where do I find that?
Your Google Manager Account ID is a 9-10 digit numeric that can be found next to your profile picture in the new SA 360 UI. You can enter this numeric value with or without the dashes.
How do I know which report to use? How do I map my old reports in the legacy connector to the new one?
How do I know which report to use? How do I map my old reports in the legacy connector to the new one?
The new SA360 Reporting API is significantly different from the legacy API. Below is a list of commonly used reports in the legacy connector to the new connector.The full mapping of reports from the legacy API to the new API can be found here: https://developers.google.com/search-ads/reporting/migrate/mappings/report-mappings.
Legacy connector report name | New connector report name |
Account | Customer |
Ad | Ad |
Ad Group | Ad Group |
Ad Group Dynamic Search Ads Target, Ad Group Remarketing List Target, Ad Group Target | Use Ad Group Target for target information. For metrics, use Ad Group Audience View, Age Range View, Gender View, and Web Page View. |
Advertiser | Customer |
Campaign | Campaign |
Campaign Location Target, Campaign Target | Use Campaign Criterion to get the list of criterions. To get a segmented list of metrics use the Location View and the Campaign Audience View reports. |
Conversion | Use the Conversion report to get event-level conversion data. To get Flood Light Activity, use the Conversion Action report. |
Feed Item | Asset |
Keyword | Use the Ad Group Criterion report to get the list of ad group criterions. To get a segmented list of metrics use the Keyword View report. |
Paid And Organic | This is not currently available in the new SA360 API. |
Product Group | Product Group View |
Product Target | Campaign Criterion |
How do I map the fields and metrics I was using the fields and metrics in the new reports.
How do I map the fields and metrics I was using the fields and metrics in the new reports.
The names of many fields have changed as Google has renamed many of the objects or resources that the fields reside on. For the full list of changes, visit https://developers.google.com/search-ads/reporting/migrate/mappings/field-mappings.Here are some guidelines for reading the field mappings:
- Search for the legacy API report name. On the right-hand side of the page, you will see a list of reports available in the legacy API, as shown below.
- You should now see a mapping of the field names in the old API to mappings of field names in the new API. The new field names generally have one of the following three formats:
segments.<segment_name> e.g., the deviceSegment field in the Account report now maps to segments.deviceresourceName.<attribute> e.g, the account field in the Account report now maps to customer.descriptive_nameAny field in the form of metrics.<metric_name> should be available in the corresponding report in the new SA360 connector in the “Metrics” selection box. Similarly, any field in the form of segments.<segment_name> can be found in the “Segments” selection box of the corresponding report.A resource is an entity in the new SA360 such as, but not limited to campaign, ad group, and ad. There is a report in the new connector for each resource. Any attribute in the form of resourceName.<attribute> can be found in one of two places:- If the resource is attributable to a particular object, then the resource can be selected in the report for that object. For example, the account name in the old Ad report is now mapped to the customer.descriptive_name field. In the new Ad report, the customer resource is an attributed resource, so you can select attributes from the customer resource, such as descriptive_name, in an Ad report dataset.
- Each resource has its report in the connector. You can select the report corresponding to the resource.
I have looked through the mapping of the reports and field names, but I still can’t find the field I was using before.
I have looked through the mapping of the reports and field names, but I still can’t find the field I was using before.
Google has retired some fields and has changed the behavior of several others. See https://developers.google.com/search-ads/reporting/migrate/mappings/behavior_change_fields for a full list of retired fields and behavior changes.
The data in the new connector does not match with the data in the old connector.
The data in the new connector does not match with the data in the old connector.
This is expected. If you are validating data in the new connector, use the SA360 UI as opposed to any datasets on the old connector.
The available segments and metrics in the new connector do not match those in the legacy connector.
The available segments and metrics in the new connector do not match those in the legacy connector.
This is expected. Google has changed the available fields, metrics, and segments in many of its reports. Domo’s connector does a dynamic lookup to determine which fields, metrics, and segments are available in any particular report.
I am getting an error message saying that the metrics I have selected cannot be used in the report I want to use.
I am getting an error message saying that the metrics I have selected cannot be used in the report I want to use.
In some cases, Google makes certain fields and metrics available but will throw an error if certain combinations of fields and metrics are selected. Unfortunately, there is not a way for the connector to predetermine the invalid combinations and prevent these combinations from being selected.
The data in the new connector does not match what is in the old UI.
The data in the new connector does not match what is in the old UI.
This is expected. Compare the data in the new connector to the data in the new SA360 UI, and do not compare the data in the new connector to the data in the old connector, as they will not match.
The ID numbers for customers, etc do not match with the old connector.
The ID numbers for customers, etc do not match with the old connector.
This is expected. With the new version of SA360, Google has changed the ID numbers associated with customers, ads, etc. The new ID numbers cannot be derived from the ID numbers in the old version of SA360.
I am comparing my data in the new connector to the new SA360 UI and the data is not matching.
I am comparing my data in the new connector to the new SA360 UI and the data is not matching.
If the data in the new connector does not match the data in the new SA360 UI, contact Domo Support.Datasets built on the legacy SA360 connector can continue to run successfully until the legacy API is retired in June 2024. After that date, the connector will no longer be able to bring in data from SA360.
What version of the Google Search Ads 360 (Doubleclick Search) API does this connector use?
What version of the Google Search Ads 360 (Doubleclick Search) API does this connector use?
This connector uses version 0 of the Google Search Ads 360 (Doubleclick Search) API (https://searchAds360.googleapis.com/v0)“https://searchAds360.googleapis.com/v0)”).
Are there any API limits that I need to be aware of?
Are there any API limits that I need to be aware of?
No