This article will help you learn about how Daasity replicates data from Google Analytics Multi-Channel Funnels Reporting, limitations to the data we can extract and where the data is stored in the Google Analytics MCF V2 schema
KEY TOPICS
Click on the links below to take you to the section where you can learn more about this Integration
- API Endpoints
- Entity Relationship Diagram
- Google Analytics Multi-Channel Funnels Reporting Schema
- Related Resources
INTEGRATION AVAILABILITY
This integration is available for:
- Growth
- Pro V2
NOTE: You are considered V2 if...
- You are a Growth customer
- Your account says Pro V2 in the Daasity App
Not sure? Reach out to Support@Daasity.com
INTEGRATION OVERVIEW
Google Analytics Multi-Channel Funnels Reporting API enables you to request Multi-Channel Funnels data which is derived from conversion path data and shows user interactions with various traffic sources over multiple sessions prior to converting. This allows the merchant to analyze how multiple marketing channels influence conversions over time.
The Daasity V2 Google Analytics MCF extractor pulls a standard set of data via the Multi-Channel Funnels Reporting API. The Multi-Channel Funnels Reporting API is a report generation API and requires parameters to be passed into the API.
NOTE: The API has limitations on the level of granularity that can be returned:
- Dimensions are limited to 7 per report
- Metrics are limited to 10 per report
Daasity queries each report for each day which thus removes the need to include the ga:Date as a parameter and thus allowing the full 7 dimensions to be used.
API Endpoints
The Daasity V2 Google Analytics MCF extractor is built based on this Google Analytics Multi-Channel Funnels Reporting API Documentation. The following endpoints are used by Daasity to replicate data from Google Analytics MCF V2:
Entity Relationship Diagram (ERD)
The embedded diagram houses the ERD for the Daasity Google Analytics Multi-Channel Funnels integration illustrating the different tables and keys to join across tables. Hover over the embedded diagram to reveal controls to zoom and scroll.
Google Analytics Multi-Channel Funnel Reporting Schema
The Daasity Google Analytics MCF extractor creates these tables using the endpoints and replication methods listed. The data is mapped from source API endpoint to the table based on the mapping logic outlined in each table.
Base Multi-Channel
- Endpoint: MCF
- Update Methdod: UPSERT
- Table Name: ga.base_multi_channel
JSON Element | Database Column |
MD5(all the dimensions) | id |
View ID selected for the integration | view_id |
mcf:transactionId | transaction_id |
mcf:conversionDate | created_on |
mcf:sourcePath | source_path |
Daasity: 1st node of mcf:sourcePath | source_path_first_node |
Daasity: Last node of mcf:sourcePath | source_path_last_node |
mcf:mediumPath | medium_path |
Daasity: 1st node of mcf:mediumPath | medium_path_first_node |
Daasity: Last node of mcf:mediumPath | medium_path_last_node |
mcf:campaignPath | campaign_path |
Daasity: 1st node of mcf:campaignPath | campaign_path_first_node |
Daasity: Last node of mcf:campaignPath | campaign_path_last_node |
mcf:basicChannelGrouping | basic_channel_grouping_path |
Daasity: 1st node of mcf:basicChannelGrouping | basic_channel_grouping_path_first_node |
Daasity: Last node of mcf:basicChannelGrouping | basic_channel_grouping_path_last_node |
mcf:keywordPath | keyword_path |
Daasity: 1st node of mcf:keywordPath | keyword_path_first_node |
Daasity: Last node of mcf:keywordPath | keyword_path_last_node |
mcf:sourceMediumPath | source_medium_path |
Daasity: 1st node of mcf:sourceMediumPath | source_medium_path_first_node |
Daasity: Last node of mcf:sourceMediumPath | source_medium_path_last_node |
mcf:timeLagInDaysHistogram | time_lag_in_days_histogram |
Daasity: from Channel Mapping Google Sheet | channel_first_click |
Daasity: from Channel Mapping Google Sheet | vendor_first_click |
Daasity: from Channel Mapping Google Sheet | sub_channel_first_click |
Daasity: from Channel Mapping Google Sheet | media_type_first_click |
Daasity: from Channel Mapping Google Sheet | channel_last_click |
Daasity: from Channel Mapping Google Sheet | vendor_last_click |
Daasity: from Channel Mapping Google Sheet | sub_channel_last_click |
Daasity: from Channel Mapping Google Sheet | media_type_last_click |
Daasity: from Channel Mapping Google Sheet | attribution_channel |
NOTE: There are two extractions being made for this report, due to dimension limits within an extraction. The primary table will contain the full set of columns while their stage tables will have a subset of metrics. Stage tables are stitched together to complete the primary table, updating rows with matching sync keys.
Base Multi-Channel Funnel
- Endpoint: MCF
- Update Method: UPSERT
- Table Name: ga.base_multi_channel_funnel
JSON Element | Database Column |
MD5(all the dimensions) | id |
View ID selected for the integration | view_id |
mcf:transactionId | transaction_id |
mcf:conversionDate | created_on |
mcf:sourcePath | source_path |
mcf:basicChannelGrouping | basic_channel_path |
mcf:sourceMediumPath | source_medium_path |
mcf:mediumPath | medium_path |
mcf:campaignPath | campaign_path |
mcf:keywordPath | keyword_path |
Daasity: node number | sequence |
Daasity: from Channel Mapping Google Sheet | channel |
Daasity: from Channel Mapping Google Sheet | vendor |
Daasity: from Channel Mapping Google Sheet | sub_channel |
Daasity: from Channel Mapping Google Sheet | media_type |
Daasity: from Channel Mapping Google Sheet | attribution_channel |
NOTE: There are two extractions being made for this report, due to dimension limits within an extraction. The primary table will contain the full set of columns while their stage tables will have a subset of metrics. Stage tables are stitched together to complete the primary table, updating rows with matching sync keys.
Related Resources
Although the GA Multi-Channel Funnel Reporting data extract is API based the best way to sample data is using tools that GA supplies:
- MCF Sample Data: https://developers.google.com/analytics/devguides/reporting/mcf/v3/reference
- Use the Try this API section on the right side of the page