Google Campaign Manager 360 is an ad management platform that helps advertisers and agencies manage digital campaigns across websites and mobile. It's part of Google Marketing Platform, providing tools for ad serving, targeting, verification, and reporting for digital advertising campaigns.
Why this server?
Listed as a supported data source for integration, allowing access to Google Campaign Manager 360 data.
Why this server?
Provides read-only access to Google Campaign Manager 360 data by exposing tables as relational SQL models, allowing retrieval of live data through simple MCP queries.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Enables querying Google Campaign Manager 360 data sources by exposing them as relational SQL models that can be accessed through natural language queries.
Why this server?
Allows SQL-based access to Google Campaign Manager 360 advertising data.
Why this server?
Enables SQL-based access to Google Campaign Manager 360 advertising data.
Why this server?
Provides read-only SQL access to Google Campaign Manager 360 campaign data, creatives, and performance metrics.
Why this server?
Provides SQL access to Google Campaign Manager 360 advertising data, including campaigns, creatives, and performance metrics.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver framework.
Why this server?
Provides read-only access to Google Campaign Manager 360 data through SQL models, allowing queries of Campaign Manager 360 data through natural language requests.
Why this server?
Allows SQL-based querying of Google Campaign Manager 360 advertising data through the CData JDBC driver.
Why this server?
Allows access to Google Campaign Manager 360 advertising data through SQL interfaces.
Why this server?
Listed as a supported data source for integration, enabling access to Google Campaign Manager 360 advertising data through the CData JDBC Driver.
Why this server?
Listed as a supported data source that can be queried through the MCP server.
Why this server?
Provides SQL-based access to Google Campaign Manager 360 data, enabling retrieval of digital campaign information.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for retrieving data.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for querying Google Campaign Manager 360 data.
Why this server?
Allows SQL-based access to Google Campaign Manager 360 advertising data.
Why this server?
Provides access to Google Campaign Manager 360 advertising data through relational SQL models.
Why this server?
Allows querying Google Campaign Manager 360 advertising data via SQL models.
Why this server?
Provides SQL-based access to Google Campaign Manager 360 data, enabling queries against advertising campaigns and performance metrics.
Why this server?
Provides SQL query capabilities for Google Campaign Manager 360 data, including campaigns, ads, and performance metrics.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver integration.
Why this server?
Enables querying of SAS Data Sets containing Google Campaign Manager 360 data using SQL.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to Google Campaign Manager 360 data.
Why this server?
Provides read-only access to Google Campaign Manager 360 advertising data.
Why this server?
Enables SQL queries against Google Campaign Manager 360 advertising data.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Provides SQL access to Google Campaign Manager 360 campaigns and reporting data.
Why this server?
Provides access to Google Campaign Manager 360 advertising data and reporting.
Why this server?
Provides querying capabilities for Google Campaign Manager 360 advertising data.
Why this server?
Provides access to Google Campaign Manager 360 advertising data through SQL.
Why this server?
Provides access to Google Campaign Manager 360 data through relational SQL models, supporting table discovery, column information retrieval, and SQL query execution.
Why this server?
Allows accessing Google Campaign Manager 360 advertising data through SQL queries.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for data access.
Why this server?
Enables querying Google Campaign Manager 360 advertising data through SQL
Why this server?
Provides access to Google Campaign Manager 360 advertising data through SQL-based tools for listing tables, retrieving column information, and executing SELECT queries.
Why this server?
Listed as a supported data source for querying Google Campaign Manager 360 advertising data.
Why this server?
Allows querying Campaign Manager 360 advertising data through SQL.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver, enabling data querying capabilities.
Why this server?
Listed as a supported data source for integration, allowing access to Google Campaign Manager 360 data through the MCP server.
Why this server?
Allows querying of Google Campaign Manager 360 data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver, allowing for data retrieval from Google Campaign Manager 360.
Why this server?
Allows querying of Google Campaign Manager 360 advertising data through SQL interfaces.
Why this server?
Provides SQL-based access to Google Campaign Manager 360 advertising data through the MCP server.
Why this server?
Allows querying Campaign Manager 360 campaigns and reporting data through SQL interfaces.
Why this server?
Provides read access to Google Campaign Manager 360 advertising data through SQL interfaces, enabling natural language querying of digital marketing campaigns.
Why this server?
Provides access to Google Campaign Manager 360 advertising data.
Why this server?
Allows querying of Google Campaign Manager 360 advertising data by exposing it as relational SQL models through the CData JDBC driver.
Why this server?
Provides SQL-based access to Google Campaign Manager 360 digital marketing campaign data.
Why this server?
Provides SQL-based access to Google Campaign Manager 360 advertising data.
Why this server?
Listed as a supported data source that can be accessed through the MCP server.
Why this server?
Listed as a supported data source that can be accessed through the MCP server interface, allowing retrieval of Google Campaign Manager 360 data through SQL queries.
Why this server?
Provides access to Google Campaign Manager 360 data through a SQL interface, allowing for querying campaign data, advertising information, and performance metrics from Campaign Manager 360 accounts.
Why this server?
Provides SQL-based access to Google Campaign Manager 360 advertising data, supporting querying of campaigns and performance metrics.
Why this server?
Provides access to Google Campaign Manager 360 advertising data, including campaigns, creatives, and reporting metrics.
Why this server?
Provides access to Google Campaign Manager 360 advertising data, campaigns, placements, and performance metrics through SQL queries.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Enables access to Google Campaign Manager 360 campaigns, creatives, and reports.
Why this server?
Enables querying Google Campaign Manager 360 advertising data through SQL.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to Google Campaign Manager 360 data.
Why this server?
Provides SQL-based access to Google Campaign Manager 360 advertising data, enabling queries for campaign performance and reporting.
Why this server?
Allows read-only access to Google Campaign Manager 360 advertising data.
Why this server?
Enables access to Google Campaign Manager 360 advertising data through SQL queries.
Why this server?
Listed as a supported data source that can be accessed through CData JDBC Driver and exposed via the MCP server.
Why this server?
Provides access to Google Campaign Manager 360 data through natural language queries.
Why this server?
Allows access to advertising campaign data from Google Campaign Manager 360.
Why this server?
Included in the list of supported sources for data retrieval through the MCP server.
Why this server?
Enables querying of Campaign Manager 360 advertising data, providing access to campaign performance metrics through natural language questions.
Why this server?
Enables querying Google Campaign Manager 360 advertising data through SQL-like interface.
Why this server?
Enables querying advertising campaign data from Google Campaign Manager 360.
Why this server?
Allows querying Google Campaign Manager 360 advertising data through SQL interfaces.
Why this server?
Allows read-only access to Google Campaign Manager 360 data, enabling queries for digital marketing campaigns and performance metrics.