[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-18。"],[[["\u003cp\u003eCampaign Manager 360 (CM360) data can be integrated into the Cortex Framework Data Foundation, allowing advertisers and agencies to analyze and optimize digital advertising campaigns across multiple channels.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003econfig.json\u003c/code\u003e file manages the necessary settings for connecting to CM360, including parameters for deploying CDC scripts, data transfer buckets, and dataset configurations.\u003c/p\u003e\n"],["\u003cp\u003eCM360 data is made available through Data Transfer Version 2 (DTv2) files, which contain campaign performance data and require a designated Cloud Storage bucket for storage.\u003c/p\u003e\n"],["\u003cp\u003eCloud Composer connections and service account permissions need to be configured for data pipelines that transfer data from DTv2 files to BigQuery datasets, and configuration for the ingestion settings through \u003ccode\u003eingestion_settings.yaml\u003c/code\u003e manage the \u003ccode\u003eSource to Raw\u003c/code\u003e and \u003ccode\u003eRaw to CDC\u003c/code\u003e data pipelines.\u003c/p\u003e\n"],["\u003cp\u003eReporting views, defined as green objects in the ERD, contain aggregated metrics and can be customized via the \u003ccode\u003ereporting_settings.yaml\u003c/code\u003e file, as well as by customising table partioning and clustering.\u003c/p\u003e\n"]]],[],null,["# Integration with Campaign Manager 360\n=====================================\n\nThis page describes the required configurations to bring data from\nCampaign Manager 360 as a data source of the marketing workload of\nCortex Framework Data Foundation.\n\nCampaign Manager 360 (CM360) is a web-based advertising management platform\noffered by Google specifically designed for advertisers and agencies. It\nfunctions as a central hub to manage and optimize all your digital advertising\ncampaigns across various channels. Cortex Framework provides the tools\nand platform to analyze CM360 data, combine it with data from other marketing\nchannels, and use AI to gain deeper insights and optimize your overall\nmarketing strategy.\n\nThe following diagram describes how CM360 data is\navailable through the marketing workload of Cortex Framework Data Foundation:\n\n**Figure 1**. CM360 data source. **Note:** For accessing configuration files, analytical views and models for the CM360 data source, see the [data source directory](https://github.com/GoogleCloudPlatform/cortex-data-foundation/tree/main/src/marketing/src/CM360).\n\nConfiguration file\n------------------\n\nThe [`config.json`](https://github.com/GoogleCloudPlatform/cortex-data-foundation/blob/main/config/config.json)\nfile configures the settings required to connect to data sources for transferring\ndata from various workloads. This file contains the following parameters for CM360: \n\n \"marketing\": {\n \"deployCM360\": true,\n }\n\n \"CM360\": {\n \"deployCDC\": true,\n \"dataTransferBucket\": \"\",\n \"datasets\": {\n \"cdc\": \"\",\n \"raw\": \"\",\n \"reporting\": \"REPORTING_CM360\"\n }\n }\n\nThe following table describes the value for each marketing parameter:\n\nData Model\n----------\n\nThis section describes the CM360 Data Model using the Entity\nRelationship Diagram (ERD).\n\n[](/static/cortex/docs/images/erd_cm360.png)\n**Figure 2**. CM360: Entity Relationship Diagram.\n\n### Base views\n\nThese are the blue objects in the ERD and are views on CDC tables with\nno transforms other than some column name aliases. See scripts in\n[`src/marketing/src/CM360/src/reporting/ddls`](https://github.com/GoogleCloudPlatform/cortex-data-foundation/tree/main/src/marketing/src/CM360/src/reporting/ddls).\n\n### Reporting views\n\nThese are the green objects in the ERD and are reporting views that contain\naggregate metrics. See scripts in\n[`src/marketing/src/CM360/src/reporting/ddls`](https://github.com/GoogleCloudPlatform/cortex-data-foundation/tree/main/src/marketing/src/CM360/src/reporting/ddls).\n\nDTv2 Files storage\n------------------\n\nDTv2 (Data Transfer Version 2) files are a specific format used by CM360 to\ndeliver campaign performance data. Set up the data transfer process by\nfollowing the [Data Transfer V2.0](https://developers.google.com/doubleclick-advertisers/dtv2/overview)\ndocumentation in order to use CM360 with Cortex Framework.\n\nCreate or add a Cloud Storage bucket for storing your DTv2 files from CM360.\nEnsure the files under the bucket are readable by the service account running\nDAGs in Cloud Composer. For more information,\nsee [Create storage buckets](/storage/docs/creating-buckets).\n\nData Freshness and Delay\n------------------------\n\nAs a general rule, data freshness for Cortex Framework data\nsources is limited by what upstream connection allows for, as well as the\nfrequency of your DAG execution. Adjust your DAG execution frequency to align\nwith upstream frequency, resource constraints, and your business needs.\n\nWith CM360 [Data Transfer v2](#dtv2_files_storage),\nImpressions and Clicks data are delivered 24 times a day (hourly).\nProcess time can vary by file, so files may appear out of order. Activity\nfiles are delivered daily.\n\nCloud Composer connections\n--------------------------\n\nCreate the following connections in Cloud Composer. For more details,\nsee the [Manage Airflow connections documentation](/composer/docs/how-to/managing/connections).\n\nCloud Composer service account permissions\n------------------------------------------\n\nGrant Dataflow permissions to the service account used in\nCloud Composer (as configured in the `cm360_raw_dataflow` connection).\nSee instructions in [Dataflow documentation](/dataflow/docs/concepts/security-and-permissions#df-service-account).\n\nIngestion settings\n------------------\n\nControl `Source to Raw` and `Raw to CDC` data pipelines through the settings in\nthe file [src/CM360/config/ingestion_settings.yaml](https://github.com/GoogleCloudPlatform/cortex-data-foundation/tree/main/src/marketing/src/CM360/config/ingestion_settings.yaml). This section describes the parameters of each data pipeline.\n\n### Source to raw tables\n\nThis section describes how entries that control which files from DTv2 are\nprocessed. Each entry corresponds with files associated with one entity.\nBased on this configuration, Cortex Framework creates Airflow DAGs\nthat run Dataflow pipelines to process data from the DTv2 files.\n\nThe following parameters control the settings for `Source to Raw`\nfor each entry:\n\n### Raw to CDC tables\n\nThis section has entries that control how data is moved from raw tables to\nCDC tables. Each entry corresponds with a raw table (which in\nturn corresponds with the DTv2 entity as mentioned above.)\n\nThe following parameters control the settings for `Raw to CDC` for each entry:\n\n##### Reporting settings\n\nYou can configure and control how Cortex Framework generates data\nfor the CM360 final reporting layer using the reporting settings file ([src/CM360/config/reporting_settings.yaml](https://github.com/GoogleCloudPlatform/cortex-data-foundation/tree/main/src/marketing/src/CM360/config/reporting_settings.yaml)).\nThis file controls how reporting layer BigQuery objects\n(tables, views, functions or stored procedures) are generated.\n\nFor more information, see [Customizing reporting settings file](/cortex/docs/deployment-step-five#customizing_reporting_settings_file).\n\nWhat's next?\n------------\n\n- For more information about other data sources and workloads, see [Data sources and workloads](/cortex/docs/data-sources-and-workloads).\n- For more information about the steps for deployment in production environments, see [Cortex Framework Data Foundation deployment prerequisites](/cortex/docs/deployment-prerequisites)."]]