Data is exported to a separate table each day. Tables are saved with name in format 'CostData_YYYYMMDD'.
Table schema
| Google BigQuery field name | Google BigQuery data type | Description / Google Analytics dimension or metric |
|---|---|---|
source |
STRING | Source |
medium |
STRING | Medium |
campaign |
STRING | Campaign |
keyword |
STRING | Keyword |
adContent |
STRING | Ad Content |
date |
STRING | Date |
sessions |
INTEGER | Sessions |
adCost |
FLOAT | Cost |
impressions |
INTEGER | Impressions |
adClicks |
INTEGER | Clicks |
adAccount |
STRING | Contains info about the source ad account: 1) from the adGroup field: if the data is uploaded via the Google Analytics API;2) from the AdAccount field: if the data is uploaded via an OWOX BI pipeline |
dataSource |
STRING | From what source the cost data was imported to the CostData_ table. Possible values: - AdExport: the cost data is from an OWOX BI pipeline that collects raw data from ad services to BigQuery- ROI: the cost data is from an OWOX BI pipeline that collects cost, click, impression, and UTM data from ad services to BigQuery- GA: the cost data is from Google Analytics API- Custom_Table: the cost data is from your custom BigQuery table |
campaignType |
STRING | The type of ad campaign the costs were spent on. Thanks to this field, OWOX BI can filter out mobile ad traffic while attributing session cost. Possible values: - APP: mobile app ad costs- WEB: website traffic ad costs- null: couldn't identify the type of campaignThe campaign type is identified only if the cost data was imported from another Google BigQuery table to which it was collected via an OWOX BI campaign or via Data Transfer. The APP-type cost data will not be attributed to sessions in the session data table. |
0 Comments