google_analytics.page_traffic
Daily traffic for the CanadaLogin GA4 property, broken down by page.
Each row represents one day of traffic to a single page, identified by its title, its path, and the data stream that reported it.
Keywords: Google Analytics, GA4, page views, traffic, page title, page path, data stream
Provenance
Pulled daily from the GA4 Data API (runReport) for the CanadaLogin property, via the same Lambda and pipeline as property_traffic.
- Updated: Daily, at 07:00 ET
- Retention: 7 years
- Steward: EDCP Data and Research Team
- Contact: Colin Douglas
- Location:
s3://<transformed-bucket>/google_analytics/page_traffic/
Fields
One row per date per streamname per pagetitle per pagepath.
| Field Name | Type | Description |
|---|---|---|
| date | string | The reporting day, as a partition key (for example, “2026-07-23”) |
| streamid | string | Numeric ID of the GA4 data stream that reported the page |
| streamname | string | Display name of the GA4 data stream |
| pagetitle | string | The page’s <title> at the time of the visit |
| pagepath | string | The page’s URL path |
| sessions | bigint | Number of sessions that included this page on this day |
| activeusers | bigint | Number of distinct active users who viewed this page on this day |
| screenpageviews | bigint | Number of times this page was viewed on this day |
Notes
Keep both pagetitle and pagepath in mind when joining or filtering. Title alone is an unstable key: a page retitled in a release starts a fresh row with no link to its history (this has happened repeatedly to CanadaLogin’s sign-in and sign-up pages - see the task success rate metric for the concrete impact). Path alone is unreadable in a report. Prefer pagepath for anything that needs to survive a copy or title change.
activeusers does not sum across pages. GA4 de-duplicates active users within a row’s dimension combination, so a user who visited three pages in a day appears in all three rows. Summing activeusers across pages, or across this table and property_traffic, overcounts. sessions and screenpageviews are safe to sum; see the property_traffic integrity-check note.
screenpageviews exposes per-step retries on a form page (views greater than 1 on a single page in a day is a friction signal invisible in a funnel’s pass/fail step counts).