GA4 BigQuery general availability & Multi-Channel Funnel support - 2023.07.06

Overview

This release does the following:

Why are we releasing this?

Google has not released a Multi-Channel Funnel reporting API for GA4 similar to the one that exists for Universal Analytics. As a result, the GA4BQ extractor is necessary for us to keep providing users with the same data they were getting out of Universal Analytics. This data will allow for users to continue to support Daasity's First Click, Last Ad Click, Last Marketing Click, and Assisted attribution models, which rely on Google Analytics Multi-Channel Funnel data.

Setting up the integration & Multi-Channel Funnel Report

The instructions for setting up this integration can be found here.

To get the Multi-Channel Funnel data, you must keep the Multi-Channel Funnel report toggle set to "On."

If you already have the Google Analytics via BigQuery integration set up, the Multi-Channel Funnel report will be turned on automatically.

New extractor data

The Google Analytics 4 via BigQuery extractor will query your GA4 data from BigQuery and load it into your data warehouse. The newly added MCF report will extract and load data into a new ga4_bq_stg.base_multi_channel_funnel table.

This table will show the previous 30 days of marketing activity (information on page_view events that have a non-null source value) associated with every transaction tracked in Google Analytics 4.

It will not contain data for a transaction if the user making that transaction has no marketing activity information (i.e. all pageview hits had null source values) in the past 30 days.

The extractor is de-duplicating pageviews from the same session if they have the same marketing attribution info so that there are not multiple rows with duplicate information.

ga4_bq_stg.base_multi_channel_funnel specifications

ColumnDescription

id

Unique identifier for this row

ga4_property_id

The ID of the GA4 property associated with the integration

stream_id

The stream ID associated with the pageview & transaction

user_pseudo_id

The automatically generated user cookie value set by GA4

user_id

The user ID passed explicitly in your GA4 hits

transaction_id

The ID of the transaction, as tracked in GA4

transaction_timestamp

The time (in microseconds, UTC) when the purchase event was logged by GA4

session_id

The unique session ID in which the page_view event occurred

event_timestamp

The time (in microseconds, UTC) when the page_view event was logged by GA4

source

Value of the source event parameter from the page_view hit

medium

Value of the medium event parameter from the page_view hit

campaign

Value of the campaign event parameter from the page_view hit

content

Value of the content event parameter from the page_view hit

term

Value of the term event parameter from the page_view hit

page_location

Value of the page_location event parameter from the page_view hit This is the URL on which the page_view hit occurred.

channel_grouping

Channel-mapped Default Channel Grouping value The Default Channel Grouping is not exposed directly in the GA4BQ export, so we set this to NULL when extracted and then update this field post-extraction.

channel

The channel value, based upon the values in other columns and the rules set up in your Channel-Mapping BSD

vendor

The vendor value, based upon the values in other columns and the rules set up in your Channel-Mapping BSD

sub_channel

The sub_channel value, based upon the values in other columns and the rules set up in your Channel-Mapping BSD

media_type

The media_type value, based upon the values in other columns and the rules set up in your Channel-Mapping BSD

attribution_channel

The attribution_channel value, based upon the values in other columns and the rules set up in your Channel-Mapping BSD

__sync_key

Unique identifier for this row

_account_id

Your Daasity account ID

__synced_at

Timestamp of when this row was last synced with the source

Last updated