Skip to main content

Google Search Ads 360 Data Source

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that ingests data from a Google Search Ads 360 location.
gsa360_api.png

Google Search Ads 360

Follow the instructions below to create a new data flow that ingests data from a Google Search Ads 360 source in Nexla.

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Google Search Ads 360 connector tile from the list of available connectors. 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.

  3. In Nexla, Google Search Ads 360 data sources can be created using pre-built endpoint templates, which expedite source setup for common Google Search Ads 360 endpoints. Each template is designed specifically for the corresponding Google Search Ads 360 endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Google Search Ads 360 sources can also be configured manually, allowing you to ingest data from Google Search Ads 360 endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Google Search Ads 360 endpoints. Each template is designed specifically for the corresponding Google Search Ads 360 endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    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.

Configure Manually​

Google Search Ads 360 data sources can be manually configured to ingest data from any valid Google Search Ads 360 API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Google Search Ads 360 sources, such as sources that use custom query parameters, different HTTP methods, or custom data transformations.

Content Format​

  1. Select the format in which the data from the Google Search Ads 360 API will be received from the Content Format pulldown menu. Nexla will automatically parse the data in the selected format. The Google Search Ads 360 API typically returns data in JSON format for API responses and CSV format for report files.

API Endpoint URL​

  1. Enter the URL of the Google Search Ads 360 API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Google Search Ads 360 API endpoints typically follow the pattern https://www.googleapis.com/doubleclicksearch/v2/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about Google Search Ads 360 API endpoints and available APIs, see the Google Ads API documentation.