Skip to main content

Google Campaign Manager 360 Data Source

The Google Campaign Manager 360 connector enables you to retrieve campaign data, reports, and advertising metrics from Google Campaign Manager 360. This connector is particularly useful for applications that need to extract campaign performance data, analyze advertising metrics, or integrate campaign data into analytics systems. Follow the instructions below to create a new data flow that ingests data from a Google Campaign Manager 360 source in Nexla.
cm360_api.png

Google Campaign Manager 360

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 Campaign Manager 360 connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Google Campaign Manager 360 instance, and click Next; or, create a new Google Campaign Manager 360 credential for use in this flow.

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

    Google Campaign Manager 360 sources can also be configured manually, allowing you to ingest data from Google Campaign Manager 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 Campaign Manager 360 endpoints. Each template is designed specifically for the corresponding Google Campaign Manager 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.

    Discovery Endpoints

    This endpoint inspects Google Campaign Manager 360 API's discovery document to get a full list of services, information about their URLs, and request and response formats. Use this endpoint when you need to explore available API resources and understand the API structure.

    • This endpoint automatically retrieves the discovery document for the Campaign Manager 360 API. No additional configuration is required beyond selecting this endpoint template.
    • The discovery document contains metadata about all available API resources, endpoints, and their schemas.

    The discovery document is useful for understanding the full API structure and available resources. Use this endpoint to explore API capabilities before configuring specific resource endpoints.

    User Profiles

    This endpoint retrieves user profile information for the authenticated user. Use this endpoint when you need to access user profile details and verify profile access.

    • This endpoint retrieves the user profile specified in your credential configuration. The profile ID from your credential is used to fetch the profile information.
    • The endpoint returns profile details including profile ID, account name, and other profile metadata.

    This endpoint is useful for verifying that your credential has access to the correct user profile and for retrieving profile metadata.

    Campaigns

    This endpoint retrieves a list of campaigns in your Campaign Manager 360 account. Use this endpoint when you need to access campaign data, including campaign names, IDs, status, and other campaign details.

    • This endpoint automatically retrieves all campaigns accessible to your user profile. The endpoint supports pagination to handle large datasets efficiently, automatically fetching additional pages when there are more campaigns than can be returned in a single request. Campaigns are filtered based on your user profile's permissions, so you'll only see campaigns you have access to in Campaign Manager 360.
    • Campaign data includes campaign names, IDs, advertiser information, start and end dates, campaign status (active, paused, archived), budget information, targeting settings, and performance metrics. This comprehensive data allows you to analyze campaign performance, track campaign lifecycle, and integrate campaign data into your analytics and reporting systems.

    This endpoint is useful for building campaign lookups, analyzing campaign performance, or syncing campaign data to other systems. The endpoint supports filtering and pagination for large campaign lists. You can filter campaigns by advertiser, status, date range, and other criteria using query parameters. For accounts with many campaigns, consider using filters to limit the results and improve performance.

    Advertisers

    This endpoint retrieves a list of advertisers in your Campaign Manager 360 account. Use this endpoint when you need to access advertiser information, including advertiser names, IDs, and account details.

    • This endpoint automatically retrieves all advertisers accessible to your user profile. The endpoint supports pagination to handle large datasets efficiently.
    • Advertiser data includes advertiser names, IDs, account information, and other advertiser metadata.

    This endpoint is useful for building advertiser lookups, organizing campaigns by advertiser, or analyzing advertiser-level data. The endpoint supports filtering and pagination for large advertiser lists.

    Placements

    This endpoint retrieves a list of placements in your Campaign Manager 360 account. Use this endpoint when you need to access placement data, including placement names, IDs, and configuration details.

    • This endpoint automatically retrieves all placements accessible to your user profile. The endpoint supports pagination to handle large datasets efficiently.
    • Placement data includes placement names, IDs, campaign associations, size information, and other placement metadata.

    This endpoint is useful for analyzing placement performance, building placement inventories, or syncing placement data to other systems. The endpoint supports filtering and pagination for large placement lists.

    Reports

    This endpoint retrieves a list of reports in your Campaign Manager 360 account. Use this endpoint when you need to access report metadata, including report names, IDs, and configuration details.

    • This endpoint automatically retrieves all reports accessible to your user profile.
    • Report data includes report names, IDs, report types, schedule information, and other report metadata.

    This endpoint is useful for discovering available reports, monitoring report schedules, or managing report configurations. Note that this endpoint returns report metadata; to retrieve actual report data, you may need to use additional endpoints or manual configuration.

Google Campaign Manager 360 API provides many additional endpoints for accessing various resources such as ads, creatives, sites, floodlight activities, and more. The templates above represent commonly used endpoints, but you can use manual configuration to access any available CM360 API endpoint.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Google Campaign Manager 360 data sources can be manually configured to ingest data from any valid Google Campaign Manager 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 Campaign Manager 360 sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Google Campaign Manager 360 API from the Method pulldown menu. The most common methods are:

    • GET: For retrieving data from the API
    • POST: For sending data to the API or triggering actions
    • PUT: For updating existing data
    • PATCH: For partial updates to existing data
    • DELETE: For removing data

API Endpoint URL​

  1. Enter the URL of the Google Campaign Manager 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 Campaign Manager 360 API endpoints typically follow the pattern https://dfareporting.googleapis.com/dfareporting/{version}/userprofiles/{profileId}/{resource}.

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 URL should include your API version (v4 or v5) and your user profile ID.

Path to Data​

Optional

If only a subset of the data that will be returned by API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain metadata, pagination information, or other data that you don't need for your analysis.

For example, when a request call is used to fetch a list of items, the API will typically return an array of records, along with metadata, in the response. By entering the path to the relevant data, you can configure Nexla to treat each element of the returned array as a record.

Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.items[*] to access an array of items).

    • For responses in XML format, enter the XPath that points to the object/array containing relevant data. XPath uses slash notation (e.g., /response/items/item to access item elements).

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include any headers already present in the credentials. Common headers like Authorization, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Google Campaign Manager 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.