When data is delivered to a data lake, the folder structure is as follows:
- google-mmm-ads
- google-mmm-ads-metadata
- google-mmm-dv360
- google-mmm-dv360-metadata
- google-mmm-ads-reach
- google-mmm-ads-reach-metadata
- google-mmm-ads-gqv
- google-mmm-ads-gqv-metadata
Metadata files
For each project delivery, MMM Data Platform creates a JSON metadata file in the metadata folder for each requested report type (ads/dv360/reach/gqv). This file contains a list of data files delivered for the given report type.
{
"googleProjectId": "1-1234567891234",
"projectName": "Test Project 2",
"dateRange": "2024/01/01-2024/09/25",
"dataGeoGranularity": "LOWEST_LEVEL",
"dataTimeGranularity": "WEEKLY_SUNDAY",
"brands": [
"Brand 1"
],
"deliveryValidationStats": {
"recordCount": "951700",
"fileNames": [
"google_mmm_dv360_1-1234567891234_DV360TestProject200000of00003.csv",
"google_mmm_dv360_1-1234567891234_DV360TestProject200001of00003.csv",
"google_mmm_dv360_1-1234567891234_DV360TestProject200002of00003.csv"
]
},
"countryCode": "US"
}
Metadata files follow the naming convention:
<data_type>_metadata-<CASE_ID>.json. For example:
google_mmm_dv360_metadata_1-1234567891234.json.