Google Analytics 4 data reference
Lucen syncs your Google Analytics 4 data (Analytics) to your warehouse and models it into the tables below. You connect Google Analytics 4 with one OAuth sign-in. By default your data refreshes every day at 07:00 Buenos Aires time (UTC-3). Your plan sets how many times a day it can sync, and you can choose the times, see pricing.
Your plan sets how much history the first sync loads, see pricing.
Send Google Analytics 4 data to
Tables
gold_google_analytics_event_catalog_current
- Grain
- Current event catalog
gold_google_analytics_first_user_channel_daily
- Grain
- First-user channel
gold_google_analytics_first_user_channel_events_daily
One row per property_id, date, first_user_default_channel_group, event_name, is_key_event. Use for original user acquisition by GA4's default channel classification. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_first_user_channel_key_event_pivot_daily
One row per property_id, date, first_user_default_channel_group. Use for original user acquisition by GA4's default channel classification. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_first_user_manual_source_daily
- Grain
- Manual first-user source
gold_google_analytics_first_user_manual_source_events_daily
One row per property_id, date, first_user_manual_source, event_name, is_key_event. Use for original user acquisition by manual UTM attribution. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_first_user_manual_source_key_event_pivot_daily
One row per property_id, date, first_user_manual_source. Use for original user acquisition by manual UTM attribution. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_first_user_manual_source_medium_content_daily
- Grain
- Manual first-user source / medium / content
gold_google_analytics_first_user_manual_source_medium_content_events_daily
One row per property_id, date, first_user_manual_source, first_user_manual_medium, first_user_manual_ad_content, event_name, is_key_event. Use for original user acquisition by manual UTM attribution. Content is the manual utm_content dimension. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_first_user_manual_source_medium_content_key_event_pivot_daily
One row per property_id, date, first_user_manual_source, first_user_manual_medium, first_user_manual_ad_content. Use for original user acquisition by manual UTM attribution. Content is the manual utm_content dimension. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_first_user_manual_source_medium_daily
- Grain
- Manual first-user source / medium
gold_google_analytics_first_user_manual_source_medium_events_daily
One row per property_id, date, first_user_manual_source, first_user_manual_medium, event_name, is_key_event. Use for original user acquisition by manual UTM attribution. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_first_user_manual_source_medium_key_event_pivot_daily
One row per property_id, date, first_user_manual_source, first_user_manual_medium. Use for original user acquisition by manual UTM attribution. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_first_user_source_daily
- Grain
- First-user source
gold_google_analytics_first_user_source_events_daily
One row per property_id, date, first_user_source, event_name, is_key_event. Use for original user acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Independent event-count query, with historical is_key_event in the grain. Sum both status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_first_user_source_key_event_pivot_daily
One row per property_id, date, first_user_source. Use for original user acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_first_user_source_medium_content_daily
- Grain
- First-user source / medium / content
gold_google_analytics_first_user_source_medium_content_events_daily
One row per property_id, date, first_user_source, first_user_medium, first_user_manual_ad_content, event_name, is_key_event. Use for original user acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Content is the manual utm_content dimension. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_first_user_source_medium_content_key_event_pivot_daily
One row per property_id, date, first_user_source, first_user_medium, first_user_manual_ad_content. Use for original user acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Content is the manual utm_content dimension. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_first_user_source_medium_daily
- Grain
- First-user source / medium
gold_google_analytics_first_user_source_medium_events_daily
One row per property_id, date, first_user_source, first_user_medium, event_name, is_key_event. Use for original user acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_first_user_source_medium_key_event_pivot_daily
One row per property_id, date, first_user_source, first_user_medium. Use for original user acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_geography_daily
- Grain
- Country / region / city
gold_google_analytics_geography_events_daily
One row per property_id, date, country, region, city, event_name, is_key_event. Use for GA4-attributed geography at the complete country/region/city grain. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_geography_key_event_pivot_daily
One row per property_id, date, country, region, city. Use for GA4-attributed geography at the complete country/region/city grain. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_landing_page_daily
- Grain
- Session entry page
gold_google_analytics_landing_page_events_daily
One row per property_id, date, landing_page, event_name, is_key_event. Use for session entry-page reporting. Independent event-count query, with historical is_key_event in the grain. Sum both status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_landing_page_key_event_pivot_daily
One row per property_id, date, landing_page. Use for session entry-page reporting. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_page_daily
- Grain
- Page path
gold_google_analytics_page_events_daily
One row per property_id, date, page_path, event_name, is_key_event. Use for activity by visited page, not session entry-page reporting. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_page_key_event_pivot_daily
One row per property_id, date, page_path. Use for activity by visited page, not session entry-page reporting. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_property_current
- Grain
- Current property metadata
gold_google_analytics_property_daily
- Grain
- Property totals (use this for headlines)
gold_google_analytics_property_events_daily
One row per property_id, date, event_name, is_key_event. Use for property-day totals; do not reconstruct them by summing breakdown reports. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_property_key_event_pivot_daily
One row per property_id, date. Use for property-day totals; do not reconstruct them by summing breakdown reports. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_session_channel_daily
- Grain
- Session default channel
gold_google_analytics_session_channel_events_daily
One row per property_id, date, session_default_channel_group, event_name, is_key_event. Use for session acquisition by GA4's default channel classification. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_session_channel_key_event_pivot_daily
One row per property_id, date, session_default_channel_group. Use for session acquisition by GA4's default channel classification. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_session_manual_source_daily
- Grain
- Manual session source
gold_google_analytics_session_manual_source_events_daily
One row per property_id, date, session_manual_source, event_name, is_key_event. Use for session acquisition by manual UTM attribution. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_session_manual_source_key_event_pivot_daily
One row per property_id, date, session_manual_source. Use for session acquisition by manual UTM attribution. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_session_manual_source_medium_content_daily
- Grain
- Manual session source / medium / content
gold_google_analytics_session_manual_source_medium_content_events_daily
One row per property_id, date, session_manual_source, session_manual_medium, session_manual_ad_content, event_name, is_key_event. Use for session acquisition by manual UTM attribution. Content is the manual utm_content dimension. Independent event-count query, with historical is_key_event in the grain. Sum both status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_session_manual_source_medium_content_key_event_pivot_daily
One row per property_id, date, session_manual_source, session_manual_medium, session_manual_ad_content. Use for session acquisition by manual UTM attribution. Content is the manual utm_content dimension. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_session_manual_source_medium_daily
- Grain
- Manual session source / medium
gold_google_analytics_session_manual_source_medium_events_daily
One row per property_id, date, session_manual_source, session_manual_medium, event_name, is_key_event. Use for session acquisition by manual UTM attribution. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_session_manual_source_medium_key_event_pivot_daily
One row per property_id, date, session_manual_source, session_manual_medium. Use for session acquisition by manual UTM attribution. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_session_source_daily
- Grain
- Session source
gold_google_analytics_session_source_events_daily
One row per property_id, date, session_source, event_name, is_key_event. Use for session acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Independent event-count query, with historical is_key_event in the grain. Sum both status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_session_source_key_event_pivot_daily
One row per property_id, date, session_source. Use for session acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_session_source_medium_content_daily
- Grain
- Session source / medium / content
gold_google_analytics_session_source_medium_content_events_daily
One row per property_id, date, session_source, session_medium, session_manual_ad_content, event_name, is_key_event. Use for session acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Content is the manual utm_content dimension. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_session_source_medium_content_key_event_pivot_daily
One row per property_id, date, session_source, session_medium, session_manual_ad_content. Use for session acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Content is the manual utm_content dimension. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
gold_google_analytics_session_source_medium_daily
- Grain
- Session source / medium
gold_google_analytics_session_source_medium_events_daily
One row per property_id, date, session_source, session_medium, event_name, is_key_event. Use for session acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Independent event-count query, with historical is_key_event in the grain. Sum all status rows for all occurrences of a name; filter true for historically key occurrences. Use the matching performance model for users and sessions; aggregate event rows to its full key before joining.
gold_google_analytics_session_source_medium_key_event_pivot_daily
One row per property_id, date, session_source, session_medium. Use for session acquisition by GA4-resolved attribution. Resolved includes eligible auto-tagged traffic; it is not auto-tag-only. Pilot view combining independent performance with occurrence columns for currently configured key-event names across properties; columns change on rebuild. Counts include both historical key statuses; zero means complete coverage with no matching occurrences, NULL means missing coverage or an event not currently key for that property. Event-only keys retain NULL performance. Use the property report for totals and never sum distinct-user metrics.
Columns
Column names match your warehouse exactly. Descriptions come from dbt.
gold_google_analytics_event_catalog_current columns
gold_google_analytics_first_user_channel_daily columns
19
gold_google_analytics_first_user_channel_events_daily columns
gold_google_analytics_first_user_channel_key_event_pivot_daily columns
18
gold_google_analytics_first_user_manual_source_daily columns
19
gold_google_analytics_first_user_manual_source_events_daily columns
gold_google_analytics_first_user_manual_source_key_event_pivot_daily columns
18
gold_google_analytics_first_user_manual_source_medium_content_daily columns
21
gold_google_analytics_first_user_manual_source_medium_content_events_daily columns
gold_google_analytics_first_user_manual_source_medium_content_key_event_pivot_daily columns
20
gold_google_analytics_first_user_manual_source_medium_daily columns
20
gold_google_analytics_first_user_manual_source_medium_events_daily columns
gold_google_analytics_first_user_manual_source_medium_key_event_pivot_daily columns
19
gold_google_analytics_first_user_source_daily columns
19
gold_google_analytics_first_user_source_events_daily columns
gold_google_analytics_first_user_source_key_event_pivot_daily columns
18
gold_google_analytics_first_user_source_medium_content_daily columns
21
gold_google_analytics_first_user_source_medium_content_events_daily columns
gold_google_analytics_first_user_source_medium_content_key_event_pivot_daily columns
20
gold_google_analytics_first_user_source_medium_daily columns
20
gold_google_analytics_first_user_source_medium_events_daily columns
gold_google_analytics_first_user_source_medium_key_event_pivot_daily columns
19
gold_google_analytics_geography_daily columns
21
gold_google_analytics_geography_events_daily columns
gold_google_analytics_geography_key_event_pivot_daily columns
20
gold_google_analytics_landing_page_daily columns
19
gold_google_analytics_landing_page_events_daily columns
gold_google_analytics_landing_page_key_event_pivot_daily columns
18
gold_google_analytics_page_daily columns
19
gold_google_analytics_page_events_daily columns
gold_google_analytics_page_key_event_pivot_daily columns
18
gold_google_analytics_property_current columns
gold_google_analytics_property_daily columns
18
gold_google_analytics_property_events_daily columns
gold_google_analytics_property_key_event_pivot_daily columns
17
gold_google_analytics_session_channel_daily columns
19
gold_google_analytics_session_channel_events_daily columns
gold_google_analytics_session_channel_key_event_pivot_daily columns
18
gold_google_analytics_session_manual_source_daily columns
19
gold_google_analytics_session_manual_source_events_daily columns
gold_google_analytics_session_manual_source_key_event_pivot_daily columns
18
gold_google_analytics_session_manual_source_medium_content_daily columns
21
gold_google_analytics_session_manual_source_medium_content_events_daily columns
gold_google_analytics_session_manual_source_medium_content_key_event_pivot_daily columns
20
gold_google_analytics_session_manual_source_medium_daily columns
20
gold_google_analytics_session_manual_source_medium_events_daily columns
gold_google_analytics_session_manual_source_medium_key_event_pivot_daily columns
19
gold_google_analytics_session_source_daily columns
19
gold_google_analytics_session_source_events_daily columns
gold_google_analytics_session_source_key_event_pivot_daily columns
18
gold_google_analytics_session_source_medium_content_daily columns
21
gold_google_analytics_session_source_medium_content_events_daily columns
gold_google_analytics_session_source_medium_content_key_event_pivot_daily columns
20
gold_google_analytics_session_source_medium_daily columns
20
gold_google_analytics_session_source_medium_events_daily columns
gold_google_analytics_session_source_medium_key_event_pivot_daily columns
19
Typical questions
Users / sessions this month
gold_google_analytics_property_dailydo not SUM users across days as unique
Landing pages
gold_google_analytics_landing_page_daily
Channel mix
gold_google_analytics_session_channel_daily
Starter queries
SELECT date, property_id, total_users, active_users, new_users
FROM `your-project.your_org_gold.gold_google_analytics_property_daily`
WHERE date >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
ORDER BY date DESC
LIMIT 100;SELECT date, property_id, landing_page, total_users, active_users
FROM `your-project.your_org_gold.gold_google_analytics_landing_page_daily`
WHERE date >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
ORDER BY date DESC
LIMIT 100;SELECT date, property_id, page_path, total_users, active_users
FROM `your-project.your_org_gold.gold_google_analytics_page_daily`
WHERE date >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
ORDER BY date DESC
LIMIT 100;SELECT date, property_id, country, region, city
FROM `your-project.your_org_gold.gold_google_analytics_geography_daily`
WHERE date >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
ORDER BY date DESC
LIMIT 100;