Skip to main content

Google Search Ads 360

Google Search Ads 360 is an enterprise-level search marketing platform that provides advanced campaign management, bidding optimization, and cross-channel analytics for large-scale advertising operations, enabling businesses to maximize their search marketing ROI with sophisticated automation and insights.

Google Search Ads 360 icon

Power end-to-end data operations for your Google Search Ads 360 API with Nexla. Our bi-directional Google Search Ads 360 connector is purpose-built for Google Search Ads 360, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Google Search Ads 360 or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Google Search Ads 360 workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Before creating a Google Search Ads 360 credential, you need a Google account with access to Google Search Ads 360. Nexla authenticates to the Google Search Ads 360 API (also known as the DoubleClick Search API) using OAuth2 through a Nexla-managed application, so you do not need to register your own Google Cloud project or OAuth client — you'll sign in with your Google account and grant Nexla access during credential creation. The required access scopes are https://www.googleapis.com/auth/doubleclicksearch and https://www.googleapis.com/auth/userinfo.email, which provide access to your Search Ads 360 data and user email information. For detailed information about the Google Search Ads 360 API, refer to the Google Ads API documentation.

Authenticate​

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Google Search Ads 360

GSA360Cred.png

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  2. Click the Authorize button to begin the OAuth2 authorization flow. This will redirect you to Google's authorization page where you will be asked to sign in with your Google account and grant permissions to Nexla to access your Google Search Ads 360 data.

    During the OAuth2 authorization flow, you will be redirected to Google's authorization page. You must sign in with a Google account that has access to the Google Search Ads 360 account you want to connect. After signing in, you will be asked to grant permissions to Nexla to access your Google Search Ads 360 data. The required scopes are https://www.googleapis.com/auth/doubleclicksearch and https://www.googleapis.com/auth/userinfo.email, which provide access to your Search Ads 360 data and user email information. Once you grant permissions, you will be redirected back to Nexla, and the authorization will be completed automatically.

  3. After completing the OAuth2 authorization flow, Nexla will automatically obtain and store the access token and refresh token needed to authenticate API requests. The access token is used to authenticate each API request, and the refresh token is used to obtain new access tokens when the current access token expires.

    OAuth2 access tokens expire after a certain period for security reasons. Nexla automatically refreshes expired access tokens using the refresh token, so you typically do not need to re-authorize unless you revoke access or the refresh token expires. The access token is sent in the Authorization header with the Bearer prefix for all API requests to the Google Search Ads 360 API. For detailed information about OAuth2 authentication and token management, see the Google Ads API documentation.

  4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Google Search Ads 360 connector tile, then select the credential that will be used to connect to the Google Search Ads 360 account, and click Next; or, create a new Google Search Ads 360 credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Google Search Ads 360 endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable box below.

Get Report Data

Configure this ingestor to fetch reports from your Search Ads 360 account. Reports data will be downloaded automatically and extracted as Nexla datasets.

  • Enter the report query in the Report Query field. This should be a valid JSON object that defines the report parameters, including report type, date range, columns, filters, and other report configuration options. The default value is {} if not specified. The report query determines what data will be retrieved from your Search Ads 360 account.
  • The endpoint uses a multi-step process to generate and retrieve reports. First, it sends a POST request to https://www.googleapis.com/doubleclicksearch/v2/reports with the report query in the request body to initiate report generation. The response contains a report ID that is used in subsequent steps.
  • Next, the endpoint polls the report status using GET requests to https://www.googleapis.com/doubleclicksearch/v2/reports/{report_id} until the report is ready. The endpoint uses async polling (iteration.type: async.poll) and checks the isReportReady field in the response. When isReportReady is true, the report is ready for download.
  • Once the report is ready, the endpoint retrieves the report files from the URLs provided in the response. The endpoint extracts file URLs from the files array in the API response ($.files[*]) and downloads each file as CSV data.
  • The endpoint processes the downloaded CSV files and extracts the data as Nexla datasets. Each file is parsed and converted into structured data that can be used in your data flows.

This endpoint uses an asynchronous report generation process. The report query must be a valid JSON object that defines the report parameters according to the Google Search Ads 360 API specification. Common report parameters include reportType, startDate, endDate, columns, filters, and maxRowsPerFile. The endpoint automatically handles the multi-step process of generating the report, polling for completion, and downloading the report files. Reports are downloaded as CSV files and automatically parsed into structured datasets. The endpoint supports pagination through multiple report files if the report data exceeds the maximum rows per file. For detailed information about report query format, available report types, and report parameters, see the Google Search Ads 360 API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Google Search Ads 360 data sources can also be manually configured to ingest data from any valid Google Search Ads 360 API endpoint, including endpoints not covered by the pre-built templates or requiring custom query parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

The Google Search Ads 360 API typically returns data in JSON format for API responses and CSV format for report files. Endpoints generally follow the pattern https://www.googleapis.com/doubleclicksearch/v2/{endpoint_path}, and requests are authenticated automatically using the Authorization: Bearer {token} header from your credential. For detailed information about available endpoints, see the Google Ads API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Google Search Ads 360 data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.