Last verified: October 19, 2026
What You Can Now Do
Context Memo now lets you view traffic metrics broken down by individual pages inside your landing page builder, with region-based consent handling for GA4 data. Before this deploy, the analytics section answered one question: how much traffic the brand's published pages pulled in total. Now every page reports its own numbers, so you can see which memos and landing pages are actually earning visits and which ones are sitting quiet. The task this changes is prioritization. Instead of refreshing your whole library on instinct, you pick the two or three pages worth the next editing pass.
Where It Is in Context Memo
It's in the landing page builder, in the analytics section. The section now renders site traffic per page rather than a single rolled-up figure, served by a new traffic endpoint that reads GA4 and splits results by hostname per brand. If your brand publishes across more than one host, each host's pages are reported against that host instead of pooled into one bucket.
How to Use It
- Open the landing page builder for the brand you want to review and go to the analytics section. The traffic view loads with one row per page instead of a brand-level total.
- Check that the hostname you publish on is the one connected to your GA4 property. Pages served from a host that isn't mapped to the brand will return no traffic data, and an empty row is a mapping problem, not a traffic problem.
- Read the per-page numbers against your publish dates. A page that has been live for weeks with flat traffic is a content problem. A page published days ago with flat traffic is usually still an indexing question.
- Cross-reference your highest-traffic pages with citation tracking for the same URLs. Pages that draw traffic and citations are the templates worth repeating. Pages that draw citations but little traffic tell you the model is using the page while human search is not finding it.
- Update or expand the pages that are underperforming, republish, and come back to the same view after your next crawl cycle to confirm the change moved anything.
Why We Built It
Customers kept asking a version of the same question: which of our pages is driving traffic? The analytics section could only answer it in aggregate, which meant a brand with dozens of published memos knew the total and nothing about the distribution. That cost teams real editing hours. They rewrote pages that were already working, left dead pages in place, and had no page-level evidence when someone senior asked what the publishing program was returning. Page-level traffic replaces that guesswork with a list you can act on in order.
What It Does Not Do Yet
A few limits worth knowing before you read the numbers:
- GA4 is the source, so GA4 is the ceiling. If the property isn't connected, or the page's hostname isn't mapped to the brand, the page reports nothing. There's no independent traffic counter behind this view.
- Consent handling suppresses some sessions by design. Region-based consent rules mean visitor traffic from regions where consent wasn't granted won't appear in the page's totals. Treat per-page numbers as a floor for compliance-sensitive geographies, not a full census, and use directional comparison between pages rather than absolute volume.
- It reports human site traffic, not AI bot crawl activity. Crawl tracking and citation data remain separate signals in the platform. Reading both together is the point of step 4 above; this view alone won't tell you which model touched the page.
- It is not a replacement for your analytics suite. The page-level view is scoped to pages you publish through Context Memo so you can make a publishing decision in the same place you make the edit. Deeper segmentation, funnel analysis, and cross-site attribution still belong in GA4 itself.
Changelog
October 19, 2026
Disconnect Google Analytics and Search Console Integrations. You can now disconnect your Google Analytics and Google Search Console integrations from the dashboard. When you disconnect, brand data from those sources is hidden across analytics sections, performance dashboards, and traffic reports, and a source badge now indicates which data comes from which integration.
October 15, 2026
Stackable Exclusions Across Traffic Dimensions. You can now stack exclusions across any dimension—region, source, device, or page—in the Performance Dashboard traffic explorer to isolate the traffic patterns that matter most to your analysis.
