Google Campaign Manager 360 Integration for Nodus
1. Introduction to the Google Campaign Manager 360 Integration
What Is This Integration?
The Google Campaign Manager 360 (CM360) integration connects your Campaign Manager ad server platform data with Nodus, allowing you to extract, analyze, and transform campaign performance metrics, creative insights, and conversion data. This integration functions as a source connector, bringing your CM360 data into the Nodus ecosystem for advanced analytics and business intelligence.
Prerequisites:
- An active Google Campaign Manager 360 account
- CM360 Profile ID (User profile)
- CM360 Account ID
- Optional: Advertiser ID for specific advertiser data
- Authorization via Google Single Sign-On (SSO)
- Google account with access to your CM360 account
Connection Overview:
The integration uses Google's Campaign Manager 360 Reporting API to extract advertising data and performance metrics. Authentication is handled through OAuth 2.0 with Google, and the connector extracts data based on predefined templates that specify which reports to retrieve.
2. Platform Setup Documentation (Setup Form for CM360)
Purpose & Scope
This section covers how to set up the initial connection between Nodus and Google Campaign Manager 360 by providing the necessary authentication credentials and account identifiers.
Field-by-Field Breakdown:
Integration Name
- Field Name & Label: Integration Name
- Description & Purpose: A descriptive name to identify this CM360 integration within your Nodus account.
- Validation Rules & Format: Text string, required field.
- Examples: "CM360 - Main Account", "Client A Campaign Manager"
- Troubleshooting Tips: Use a descriptive name that clearly identifies the specific CM360 account or purpose.
CM360 Account ID
- Field Name & Label: CM360 Account ID
- Description & Purpose: The unique identifier for your CM360 account, used to access reporting data.
- Validation Rules & Format: Numeric string, required field.
- Examples: "123456789"
- Troubleshooting Tips: You can find your Account ID in CM360 UI under Account Settings.
CM360 Profile ID
- Field Name & Label: CM360 Profile ID
- Description & Purpose: The User Profile ID with the permissions to access reporting.
- Validation Rules & Format: Numeric string, required field.
- Examples: "12345678"
- Troubleshooting Tips: Found in CM360 UI under User Profile settings. This is the profile that will be used for API access.
CM360 Advertiser ID (Optional)
- Field Name & Label: CM360 Advertiser ID
- Description & Purpose: The specific Advertiser ID to limit reporting scope (optional).
- Validation Rules & Format: Numeric string, optional field.
- Examples: "54321678"
- Troubleshooting Tips: If provided, data will be limited to this specific advertiser. Leave blank to access all authorized advertisers.
External Link
- Link Label: "CM360 API Documentation"
- URL: https://developers.google.com/doubleclick-advertisers/reporting
- Purpose: Provides access to official Google CM360 API documentation for additional help.
Step-by-Step Guide:
- Log in to your Campaign Manager 360 account
- Navigate to Account Settings to locate your Account ID
- Find your Profile ID under User Profile
- Optionally, identify the Advertiser ID if you want to limit data to a specific advertiser
- Enter these values along with a meaningful Integration Name in the Nodus setup form
- Click Authorize to launch the Google OAuth authorization flow
- Grant permissions when prompted by Google
- Verify connection and save the configuration
Reference Links:
3. Extraction/Query Configuration (Extraction Form for CM360)
Purpose & Overview
This section explains how to configure data extraction from Google Campaign Manager 360. The platform offers various templates for extracting different types of advertising data and performance reports.
Template & Field Documentation:
Template Selection
- Field Name & Label: Select a template
- Description & Purpose: Defines which type of CM360 data to extract
- Validation Rules & Format: Dropdown selection, required field
- Available Options:
- Campaign Performance - Performance metrics aggregated at the campaign level
- Creative Performance - Performance data for individual creatives including completion rates
- Geographic Performance - Performance metrics broken down by geographic regions
- Floodlight Conversions - Conversion data from floodlight tags
- Attribution Analysis - Path to conversion data for attribution modeling
Lookback Range
- Field Name & Label: Lookback Range
- Description & Purpose: Specifies how many days back to extract data
- Validation Rules & Format: Dropdown selection, required field
- Available Options:
- 7-day Range
- 14-day Range
- 30-day Range (recommended)
- 90-day Range
- 180-day Range
- Troubleshooting Tips: Larger date ranges will result in more data being extracted but may take longer to process.
Historic Date Selection
- Field Name & Label: Historic Date
- Description & Purpose: For historical data extraction, specifies a custom date range
- Validation Rules & Format: Date picker, required field
- Troubleshooting Tips: CM360 typically maintains historical data for extended periods, but very old data may have limitations.
Workflow & Examples:
- Select the appropriate template (e.g., "Campaign Performance" for campaign-level metrics)
- Choose a lookback period or specific historic date range
- Preview the query to confirm configuration
- Execute extraction
Example Use Cases:
Campaign Performance Analysis:
- Template: Campaign Performance
- Metrics: Impressions, clicks, spend, conversions, viewability
- Lookback: 30-day Range
Creative Performance Optimization:
- Template: Creative Performance
- Metrics: Creative engagement, video completion rates, click-through rates
- Lookback: 90-day Range
Geographic Targeting Analysis:
- Template: Geographic Performance
- Metrics: Performance metrics by country, region, and city
- Historic Date: Custom range for specific campaign periods
Conversion Analysis:
- Template: Floodlight Conversions
- Metrics: Conversion counts, conversion values, attribution
- Lookback: 30-day Range
4. Data Mapping & Underlying Models for CM360
Data Model Overview
The CM360 integration extracts data using the Campaign Manager Reporting API based on the selected template. Each template corresponds to specific report types and data structures.
Schema & Field Mapping
Campaign Performance Schema
| Field | Description |
|---|---|
| date | The date for the metrics |
| campaign_id | The unique identifier of the campaign |
| campaign | The name of the campaign |
| advertiser_id | The advertiser identifier |
| advertiser | The name of the advertiser |
| site_id | Site identifier |
| site | Name of the site |
| platform_type | Type of platform |
| browser | Browser used |
| impressions | Number of impressions |
| clicks | Number of clicks |
| click_rate | Click-through rate (CTR) |
| total_conversions | Total number of conversions |
| revenue_per_click | Revenue generated per click |
| active_view_viewable_impressions | Number of viewable impressions |
| active_view_measurable_impressions | Number of measurable impressions |
| active_view_viewable_rate | Viewable rate percentage |
| extracted_at | Timestamp of extraction |
Creative Performance Schema
| Field | Description |
|---|---|
| date | The date for the metrics |
| creative_id | The unique identifier of the creative |
| creative | The name of the creative |
| creative_type | Type of creative |
| ad_type | Type of ad |
| placement_id | Placement identifier |
| placement | Name of placement |
| advertiser_id | The advertiser identifier |
| advertiser | The name of the advertiser |
| impressions | Number of impressions |
| clicks | Number of clicks |
| active_view_viewable_impressions | Number of viewable impressions |
| video_completion_rate | Rate of video completions |
| video_first_quartile_completions | Number of videos viewed to 25% |
| video_midpoint_completions | Number of videos viewed to 50% |
| video_third_quartile_completions | Number of videos viewed to 75% |
| video_completions | Number of complete video views |
| extracted_at | Timestamp of extraction |
Geographic Performance Schema
| Field | Description |
|---|---|
| date | The date for the metrics |
| country_id | Country identifier |
| country | Country name |
| region_id | Region identifier |
| region | Region name |
| city_id | City identifier |
| city | City name |
| campaign_id | The campaign identifier |
| campaign | The campaign name |
| advertiser_id | The advertiser identifier |
| advertiser | The advertiser name |
| impressions | Number of impressions |
| clicks | Number of clicks |
| click_rate | Click-through rate |
| total_conversions | Total number of conversions |
| active_view_viewable_impressions | Number of viewable impressions |
| active_view_measurable_impressions | Number of measurable impressions |
| active_view_viewable_rate | Viewable rate percentage |
| extracted_at | Timestamp of extraction |
Floodlight Conversions Schema
| Field | Description |
|---|---|
| date | The date for the metrics |
| floodlight_configuration_id | Floodlight configuration identifier |
| advertiser_id | The advertiser identifier |
| advertiser | The advertiser name |
| activity_id | Activity identifier |
| activity | Activity name |
| activity_group_id | Activity group identifier |
| activity_group | Activity group name |
| campaign_id | Campaign identifier |
| campaign | Campaign name |
| total_conversions | Total number of conversions |
| click_through_conversions | Number of click-through conversions |
| view_through_conversions | Number of view-through conversions |
| revenue | Revenue amount |
| total_revenue | Total revenue |
| extracted_at | Timestamp of extraction |
Attribution Analysis Schema
| Field | Description |
|---|---|
| conversion_id | Unique conversion identifier |
| activity_id | Activity identifier |
| activity | Activity name |
| activity_group_id | Activity group identifier |
| activity_group | Activity group name |
| interaction_number | Interaction number in the path |
| interaction_time | Time of the interaction |
| campaign_id | Campaign identifier |
| campaign | Campaign name |
| advertiser_id | The advertiser identifier |
| advertiser | The advertiser name |
| interaction_type | Type of interaction |
| total_conversions | Total number of conversions |
| view_through_conversions | Number of view-through conversions |
| click_through_conversions | Number of click-through conversions |
| revenue | Revenue amount |
| extracted_at | Timestamp of extraction |
5. Troubleshooting & FAQs for CM360
Common Issues & Error Messages
Authentication Failures
- Error: "Authentication failed" or "Invalid OAuth token"
- Solution: Re-authorize the integration through Google OAuth. Google OAuth tokens have limited lifetimes and may need to be refreshed.
Permission Issues
- Error: "Insufficient permissions" or "Access denied"
- Solution: Ensure the Google account used for authentication has appropriate access to the CM360 account. You may need to adjust permissions in CM360 or contact your CM360 administrator.
Profile ID Issues
- Error: "Invalid profile ID" or "Profile not found"
- Solution: Verify that your Profile ID is correct. Make sure the profile has API access permissions in CM360.
Account ID Issues
- Error: "Invalid account ID" or "Account not found"
- Solution: Verify that your Account ID is correct and that your authenticated user has access to this account.
Missing Data
- Common Causes:
- Date range outside of data retention period
- Insufficient account activity to generate data
- Filtering by Advertiser ID limiting results
- Solution: Adjust template filters, check date ranges, verify advertiser settings
Contact & Support Information
- Nodus Support: support@nodus.com
Data Retention & Limitations
- CM360 maintains historical data for extended periods, often multiple years
- Some report types have specific data retention policies
- Daily reporting is the most granular time period available for most report types
- The API has limits on the number of concurrent reports and request frequency